Delayed Visual Studio 2010 RC due this week
Trimmer fit
Agentless Backup is Not a Myth
The delayed next edition of Microsoft's Visual Studio is due as a release candidate by the end of this week.
The release of Visual Studio 2010 was announced on the Visual Studio Lab Management team blog here, with the news the Lab Management RC would also be available later this week.
According to the blog: "We have taken a lot of your feedback on Beta2 and incorporated that into RC. Thanks for your feedback!"
Changes follow criticism of the pre-release Visual Studio 2010 code, criticism that saw Microsoft forced to build the RC to provide room for additional testing. Plans for the RC were announced in December 2009, with delivery due in February - that pushed out the initial planned release of Visual Studio 2010 from March to April 12, 2010.
Senior vice president of Microsoft's developer division Soma Somasegar said in December that Microsoft had "significantly improved performance" between the first and second betas but that "based on what we've heard, we clearly needed to do more work."
Somasegar said beta testers had complained of performance problems, especially on virtual memory use, while commenters on his blog talked about crashes when using XAML, Silverlight, and native 64-bit applications.
All-About-Microsoft blogger Mary-Jo Foley, meanwhile, uncovered this blog from a member of Microsoft's Visual Studio QA team who said that between the first and second betas "it became painfully obvious that the new VS had an obesity problem."
Kirill Osenkov complained of memory leaks and the fact that Visual Studio 2010 had to load the Common Language Runtime and Windows Presentation Foundation at application start up.
Visual Studio 2010 was "slow, consumed a lot of memory and the worst thing, with enough modules loaded it stopped fitting into the 2GB address space on 32-bit machine," Osenkov wrote at the weekend. ®
Regcast training : Hyper-V 3.0, VM high availability and disaster recovery
COMMENTS
This is a classic case
of "its not a bug, its a feature!". Here you have a post where hundreds of people in the community responded saying that this "feature" violates the law of "least surprise". Whats more is that to "fix" it wouldn't break any other cases... it would simply cause it to behave correctly more often. And instead of admitting a failure in the CLR spec, Eric is defending C# by saying it adheres to the spec.
Look, it pisses off your users. It doesn't make any sense. Fixing it wouldn't hurt anything else. Fix it! Don't give long winded BS arguments.... never mind. If you can't see the logic here, you never will.
Really?
I agree c# is the best language currently, but are you confusing the language with the IDE? Just a couple things off the top of my head:
1. There is no good subversion integration
2. Solutions are created into their own folder, when even the IDE really wants them in the root
3. It is tightly integrated with MS languages
4. No support for XAML
5. Service packs require a completely clean machine, or else the install results in failure
Have you actually used NetBeans, Eclipse, or any other IDE for any amount of time, or are you just BSing?
Someone step up!
I hate that I have to admit liking visual studio better than any other IDE. Its the only MS product I like. But for native C++ the only IDE I've used that comes close is Xcode (which comes very close). I really wish someone would use this chance to step up and make a better IDE. Preferably for linux. I don't understand how anyone can use eclipse for c++, its just *so* slow even on my quadcore, and the UI is always finding new ways to confuse me. Kdevelop and anjuta might be within striking distance if they focus. As things stand I use vi, and I'm much slower without my intellisense encompassing every standard library and api I'm using.

IT infrastructure monitoring strategies
Agentless Backup is Not a Myth
Top 10 SIEM implementer’s checklist
Steps to Take Before Choosing a Business Continuity Partner
Enabling efficient data center monitoring