I must say I don't like Visual Studio much. Huge, slow, takes forever to start, million functions mostly unneeded. I am not a big fan of C# either. It is a descendant of C, which was made for systems programming. Also it is usually verbose like some stupid Java program although it was improved. I also don't always like that it is compiled code. So you could easily lose the source code and then not modify your program anymore. When I write programs that are entirely irrelevant to NAV, I use Python or Ruby, these dynamic, friendly, succint interpreted languages and lightweight editors.
But it seems if you do .NET programming precisely to interact with NAV, you don't really have a lot of options. You cannot really use IronPython or similar stuff, as they run on the Dynamic Language Runtime and you cannot compile it to classes you can call from NAV. Similarly, if you for example publish a WSDL web service from NAV, and you want to write a program that consumes it, you don't have many options, you need to generate a wrapper code to do that, and only Visual Studio can do that, and only for C#. (Or VB.NET but that is not serious.) If you try to use another editor e.g. SharpDevelop it will probably be unable to do that.
What are your opinions about the options here?
I guess if I really had to I could live with C# because they really improved some of the verbosity problems at least. C# code used to be that stupid, Java-like stuff where you have to say every damn thing three times: SomeBloodyLongNoun someBloodyLongNoun = new SomeBloodyLongNoun(); so they improved it and now it is var someBloodyLongNoun = new SomeBloodyLongNoun(); so you feel less like some parrot now
Although I would still prefer something like the Boo language.
But I would really like to get rid of Visual Studio. It is a too huge tool for the small tasks we tend to have.
What is your opinion and what alternatives you found?