Developer licenses are only required if you use the VS.NET IDE. The framework itself is free and can be distributed with your program, so there are no user licenses.
Like Ben says, you can download the framework SDK for free, and you get the C# compiler with it (command-line version). Visual Studio.NET is worth the money, though. It is *so* productive!
There are no runtime license fees for applications you build with either toolset.
Chip H.
If you want to get the best response to a question, please check out FAQ222-2244 first
The Intellisense is a big win. Plus the debugger (I spend a lot of time in it ). Designing forms is one of those things that is possible under the command-line version, but is so painful that no one would want to do it twice.
Chip H.
If you want to get the best response to a question, please check out FAQ222-2244 first
For me, Intellisense is THE biggest benefit to coding in the IDE. The debugging capabilities are nice, but doesn't compare to the "edit and continue" capabilities of VB6.
Designing of forms is nice too, if you like having all that superfluous generated code. I got so used to editing down all that code that I simply design them manually now in the same amount of time.
I agree with theoxyde; IntelliSense all the way. I do miss the edit-and-continue debugger, but the intelligence of IntelliSense (wow, say that repeatedly!) is just wonderful. I don't know how many times I've said something like this: "It's in the framework somewhere, I just don't know what it's called..." then I start typing something like "System." and read all the available items, and work my way down until I find what I need.
Another favorite of mine is the automatic spacing of code (and auto-complete for loops and such). I think it's made the language more readable.
Something else that really helps is using the Color-coding under Tools->Options. I edited the color-coding scheme so that things stand out more... my screen looks a little crazy compared to the typical coder's IDE, but it really has made a difference. (Try a black background with light-blue keywords, yellow string literals, and everything else white... code is much easier for me to manage when it's colored)
I use a white back ground, black for most words, light purple for strings, pink in the back ground of region tags, and a medium blue for key words. I do strongly agree that the coloring of code you can use with the IDE helps a lot, especially using a different color for string literals, it has helped me find many a typo before it gets very far.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.