Serialization to accommodate new WCF functionality, but by all and large 3. The 2. New features are either implemented at the compiler level or in the System. Core assembly. He compared the core libraries that shipped with VS and the Beta 2 release of. NET 3. Since the. NET functionality only. Again, the core framework code at the ASP. The Visual Studio release is adding more server side control features for example control extenders , but the core has been publicly available as a preview release for more than 18 months.
Visual Studio adds design time tools and more server controls for richer UIs and better communication between the client-side code and the server. Those features are very helpful and the runtime features have been available in CTPs for a while.
Finally, one more risk mitigation factor to consider is recent announcement that source code with comments and debugging symbols are going to be available with Visual Studio and. In other areas, you get all the fixes for. The remaining risk is the new code in System. Core and in some other places. Even though the quality of Visual Studio has been pretty good, much better than in the 90s when I first looked at Microsoft tools, but new code is always new risk.
The ASP. The new controls that ship with VS are fully supported. With VS you get the stable service pack code for Visual Studio and.
I give that one to Visual Studio VS has been lacking the tool support to take full advantage of the. VS shipped with. The improved Javascript IntelliSense support alone is a great enhancement for somebody like me that delegates mundane tasks like remembering method overloads and signatures to IntelliSense. You now can set breakpoints from the start, debug and inspect javascript variables with property grids, visualizers and an immediate window just like you can in with managed code on the server.
There are many other exciting new features, too many others to list here, but the bottom line is, there are numerous reasons why VS is the better choice for developing AJAX enabled sites. Finally, you could argue that VS actually gives you the best of both worlds because VS lets you target different versions of the. NET Runtime. That's a great combination or productivity and stable code to optimize for low risk. I have been using VS since Beta 2 almost exclusively.
I have found it to be stable and at this point the most productive development environment. Some things are just incredibly easy and the inclusion of LINQ makes the creation of data centric applications all that more "Fun". You must be kidding, VS is "stable and mature"? The IDE and Intellisense is just a nightmare. Microsoft developers love ZBB even if that means closing Connect issues without explanation rather than investigating and fixing them. Developers used to matter to Microsoft, but now that Microsoft is competing with the developers too, not so much.
I'm currently using both. I use for development of my apps I'll release to a public production environment and for prototyping and. I began using in Beta 1, currently use Beta 2, and have been extremely impressed with the stability of both.
I have Beta 2, and am working in it trying to decide whether or not to move from Without spending the bucks to get RTM, is Beta 2 close enough to where I can continue objective evaluation?
Would it be possible to continue using. At least with large solutions e. I'll disagree with the last post a bit. The stability for me has not been greatly increased. I've had 2K8 lock up on me in the middle of a build. But all in all, I like this version namely because of linq.
Now I loved the introduction of generics in , but linq make worth it and then some. Check out this question It is far superb to what VS2K5 had. The code generated by the typed dataset designers is a bit cleaner and neater, especially when working with SQL Compact Edition databases.
Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams?
Collectives on Stack Overflow. Learn more. Visual Studio vs - What are the benefits? Ask Question. Asked 13 years, 3 months ago. Active 12 years ago. Viewed 20k times. What are the benefits of upgrading from Visual Studio to ? Any thoughts on whether it's worth the jump, or is it better to wait for whatever's coming next? Improve this question. Gulzar Nazim 51k 24 24 gold badges silver badges bronze badges.
Joe Schneider Joe Schneider 8, 7 7 gold badges 39 39 silver badges 58 58 bronze badges. Add a comment. Active Oldest Votes. Posting couple of screencasts but you can find more on web: Script intellisense and debugging in Visual Studio Multi-threading Debugging Enhancements in Visual Studio Improve this answer. Gulzar Nazim Gulzar Nazim 51k 24 24 gold badges silver badges bronze badges.
Wyatt Wyatt 1, 9 9 silver badges 14 14 bronze badges. I never knew that and I've been using for a while now. Hope that helps. Jason Down Jason Down Net framework. I can't see a similar option for the WinForms designer -- is there one? No, which is a bummer. Same with WPF. WPF yes, but how much form design for WinForms do you manually do in code?
In Visual Studio, a fair amount :. I find it easier to move around in; the designer requires too much switching back and forth from keyboard and mouse for me. Yeah it is worth the upgrade -- just from a simple stability factor. Jobi Joy Jobi Joy These aren't features of Visual Studio , they are features of. NET 3.
0コメント