Slashdot Mirror
Inside Visual Studio 2008
mlimber writes "Dr Dobb's Journal has a peek at what is new in Microsoft's Visual Studio 2008. Most of the features discussed in the article are related to .NET, web development, and the IDE itself. However, Herb Sutter, Microsoft software architect and chair of the ISO C++ Standards committee, blogged about some developments on the C++ front. This includes a significantly enhanced MFC for GUI building, and the inclusion of TR1 (library extensions published by the C++ standards committee, most of which have also been incorporated into the next C++ standard)."
It's already out....
Uh, GCC doesn't even support C99 why would you expect MS to be?
http://gcc.gnu.org/c99status.html
Unfortunately for me, they removed the visual XML schema designer which was
nice to get a quick overview of schema (for editing, nobody sane would anything except XML mode).
Kernel developers, system programmers and embedded developers do a lot of C, so does a lot of scientists who write in C instead of Fortran (as the restrict keyword in C99 solves the main issues with writing numerical code in C). Language runtimes tend to be written in C as well (e.g. the standard python distribution). So yes, people still write in C. Some developers (application developers for example), should naturally not write in pure C for most part (there are obviously some performance critical parts that are suitable for C).
Herb Sutter wrote in his blog (which was linked in the submission) that the only thing from TR1 for C++ not implemented was C99 support. So I guess not.
VS 2003 does not (C++) do real time error highlighting.
You need to use 3rd party plug-ins.
installs Visual Asisst http://www.wholetomato.com/
Yep. Works great now.
(No, I don't work there. Just been a long-time customer.)
Save the Music; Save the World at http://www.TuneTriever.com (Our latest Android game)
Have you tried MSVC++ 2005?
.net extensions are optional. And, in my opinion, crap. If you want to use .net, you're better off with C#.
.exe; and that it supports building .exes that run on Windows 95.
The debugger is leaps and bounds ahead of the VC6 one.
It supports parallel building of multiple projects on multicore cpus / multiple cpus (massively reducing build time).
Built in x86-64 compiling / debugging (local machine and network) support.
It supports link-time code generation (a major optimization improvement). The Pro version also supports profile-guided optimization.
It supports OpenMP multithreading extensions for C++.
Many many other improvements.
The C++
Note: VC++ 2005 Express Edition (the free version) doesn't come with the Windows Platform SDK, and if you don't install it is only good for developing C++.net apps.
The ONLY advantages to VC6 are: that it links programs against the VC6 runtime dll, which comes with most versions of Windows, right back to some 9x editions, where with VC2005 it links against the VC8 runtime dll, which most people need to install / you need to distribute it with your program / you need to static link with it, resulting in a larger
Basically VC6's only advantage is that it's old.
Take a look at the Visual Studio Express range - it's not full featured, but they are given away for free. These days the only people paying for Visual Studio are people who want the Pro features, and software shops, who can usually afford to pay for the software that drives their business anyway.
Plus they committed, in my opinion, the unforgivable sin of trying to push their _s* functions that they said were "safe" instead of ones like strncat, strncpy, etc. The first time I compiled some code in VS2005 I freaked...what are all these warnings? Then I discover it's Microsoft being "helpful" and I was annoyed. Then I realized they wanted to make my code entirely Windows-dependent (functions that start with _ are not standard) and I was enraged. What *really* enraged me was that you have to turn these stupid warnings off per project
I will give VS2008 a chance, but VS2005 with all its "standards compliant goodness" was not enough to sway me from VS6. The bloated IDE + improper warnings has utterly soured me on developing for windows; I don't want to do
Visual Studio highlights errors in Visual Basic.NET code and has done this since at least 2003.
I'm not sure why they can't extend this functionality to C#; the languages are very similar.
Bull. I have written plenty of good C++ code, and I've read lots more, over the 16 years I've been using the language. C++ requires discipline, no doubt, but used correctly it can be both extremely productive and extremely efficient.
If you have the guts, read this.Read it before, disagree with some of it, most of the rest is overstated, there are a couple of real, but avoidable, issues mentioned.
Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
The ONLY advantages to VC6 are: [snip]
I think you forgot a few. For one thing, VC6 is actually responsive as an IDE, and doesn't go into a trance for several minutes at the slightest provocation. For another, the online help is actually helpful: if you look up a C++ library function, for example, it tells you about the library function, and not some completely irrelevant class with a vaguely similar name in the .Net framework (after taking half a minute to fire up the help system before it does anything else). Then there's the browse toolbar, which was simple and effective, yet strangely is still missing several .Net-friendly versions later despite widespread criticism of its removal.
Yes, at my office we also have people who prefer to use VC++ 6. Sure, there are some minor advantages in the later versions, but I think (and we've measured these things where it matters) that most of those you cited are over-rated. Many of us long for the days when we have a simple, responsive, usable IDE.
If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
Yes, all of this stuff is C++ specific. VC++6 was a decent IDE for its time. When the first version of VS.Net came out, the architecture behind VS moved to a common core for all languages. That was fine if you were using something like C# or VB.Net, as they were new and you had all the .Net trickery to support them. However, a lot of useful stuff from VC++6, such as the browse toolbar I mentioned, couldn't be readily supported in this new multi-lingual architecture and therefore got dropped as MS effectively moved to the least common denominator.
The problem is, while there is a lot of compensating value in more recent VS releases for those using the new .Net languages, the C++ world has been pretty much left out in the cold. In the debugger, we get modest improvements in autoexp.dat, but the managed folks get full visualizers. C++ (and C++/CLI, where applicable) have lagged behind in getting proper designers for forms and such. The help system is so horribly bloated and .Net-centric now that while MSDN used to be the poster child of good technical reference material it is now almost literally useless for a C++ developer. And yes, as mentioned before, the IDE's performance and usability absolutely sucks compared to VC++6, to the point where I have seen experienced developers confront management with some hard facts and refuse to use the "upgraded" versions until compelled to do so.
If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
where (n => n < 10)
select (n => n) That is just poor code. A more elegant example using LINQ would be:
mylist.Where(n => n < 10)
I have been using LINQ for the past couple of months and have found it fantastic.