I've been trying to submit a very simple Skype Extra for a client. For what is such a digitally based business, this submission process is entirely analog and alltogether frustrating.

For the pages of developer documents that they have on their site, I found it overwhelming and really wasn't sure where to start. After building a simple ClickOnce application in C#, I later assumed that this type of application would not work as an extra. After pairing down the application to simple HTML, I submitted, submitted and accidently submitted again.

There are no contact email addresses that I could find anywhere on any of the corporate Skype sites. After resorting to posting on their forums, I have come to find that the extra will be manually reviewed, but that person is currently in Russia and will not be able to review until they return.

With no clear submission policy, no contact email addresses, and no mechanism to understand the status of your submission, I have to say I'm left entirely frustrated by this process and can't really understand how in this day and age, they haven't automated this process.

I understand the need to manually review extras, but if I were on the Skype staff, I wouldn't want to be answering the same question over and over on the boards. I'd put the ability to check the status in the hands of the submitter.

Unfortunately, a very poor characteristic that some developers and programmers have is a compulsion to shout from the mountaintops their love of a platform, language or tool. Threads like this really do nothing for anyone involved except flair tempers and expose childish name-calling tendencies. I think Jeff is above all this and I'm a bit suprised he's jumped into the fray. I do understand why he is upset, but getting sucked in is where you ultimately wind up in the same boat.

You are obviously entirely too close to what you do if you're engaging in this type of discussion. Users don't care what your application is written in. Business suits could care less as well. Its all about making it work, and work well. If you actually think one tool suits all, you have bigger issues to deal with at the moment.

Remaining indifferent can be the only correct answer. That's where I'm at right about now.

I found this little bit of code to help me keep track of moving from older classes and methods to newer ones (in instances where I need to do so over time):

		
[Obsolete("This class is being replaced with Program2.0")]
class Program
{
   [Obsolete("This method is being replaced with Process2.0")]		
   static void Process(string[] args)	
   {
   }
}