What other people say about Microsoft Visual Studio Professional 2005 [OLD VERSION]

Main Categories

Microsoft Visual Studio Professional 2005 [OLD VERSION] From:Microsoft , Microsoft Software ,
See Product Page	User Rating:Amazon Sales Rank:#1254

Page: << 1 2 3 4 >>
14 of 14 customers found the following review helpful: Good IDE but Poor Choice for Older C++ Code, 2007-02-23 Like other reviewers, I have found that older C and C++ projects (VS2003, VC++6, etc) usually will not work with Visual Studio 2005. You'll get tons of compile errors and warnings, unresolved linker symbols, etc. and you will spend a LOT of time changing your program to make it work, if you can make it work at all. And the import wizard did not help much in this respect. Also, I found it troubling that there are a lot of nice formatting and Intellisense options for C#, but not for C++. There is some rudimentary formatting and Intellisense functionality for C++, but it is much more limited than what you get for C#. So, one of the nice features of VS is missing for C++. Why? It seems this is the MS way of getting us to use their chosen language, C#. It certainly makes me wonder about the future of C++ at Microsoft. That said, there are still lots of nice features in Visual Studio 2005, and for new C++ projects its not too bad (except for limited formatting and IntelliSense functionality). I could get new projects up and running quickly and painlessly, and I liked the many build/debug features used in VS2005. 5 of 15 customers found the following review helpful: Worst Visual Studio ever Published, 2007-02-05 If you are starting from scratch; this may work. But if you have thousands of lines of C++ code that you'd like to port to the new runtime, forget about this crap. This code has compiled in Visual Studio 2002 and 2003 with only minor adjustments. Upgrading to 2005 has been basically a brick wall. I attempted the port. After a few dozen iterations, I started hitting problems with attributed ATL service classes that could not resolve base class references. Code that is executed in the compiled binary in the previous release; but that this new compiler reports as missing. And I still have 89 errors. Since I don't have the source, I cannot fix this with any kind of macro. Nice box you've painted me into Microsoft. The upgrade is not important enough for me to mess with this stuff. I have a deadline end of month. 1 of 8 customers found the following review helpful: Microsoft Visual Studio Professional 2005, 2007-01-18 Although I have not used the product as much as I would like, from installation to using the help documentation, I believe I will benifit in upgrading from the Microsoft Visual Basic 6 product. Lots of good improvements. 1 of 5 customers found the following review helpful: Only game in town, 2007-01-03 I don't find the product as easy to work with as its predecessors, but this is the way Microsoft is pushing application development, so it is a "must-have". 8 of 8 customers found the following review helpful: Almost there..., 2006-12-07 This is the best Visual Studio in awhile, but its still not there yet (especially for C++ developers, but its closer). On the positive side, C++ developers now have the cleaner syntax of C++ / CLI (there are battles raging about that name) which apparently is on a fast-track ISO certification. We shall see what happens. On the downside: still no STL / CLR dotNET. However, MS has a beta for DL, but its containers are not compatible with dotNET (yet). Good idea to stick with C# until this is fixed. The UI tools continue to soar ahead for all the dotNET languages, and I don't see any difference between C++ and the others in that department anymore. VB and C# both pick up edit & continue, good for me `cause I like grew used to it in C++. Call graphing is still only in C++. The IDE UI is tabbed, and has line revision colors on all languages. Line numbering is optional, as always, but its still simply absolute lines (not code lines). This can be a pain going cross-platform with C++. Datatips are pretty capable and improved, and can drill down into containers easily. The help system is pretty much a flood. Too much information, and there is no way to directly determine where its pulling its information from. This bites when you have multiple Visual Studios & associated MSDNs & would like confirmation that its pulling the collections correctly. As for the packaging, Visual Studio 2005 Professional edition comes with 2 product CDs, 3 MSDN CDs, and a Microsoft SQL Server 2005 Developer Edition DVD, a small product guide booklet, and two posters (one thats useless, and one of dotNET 2.0 namespaces). 3-stars, as the help system needs some work, and VC++ lacks an effective STL under dotNET. Here's hoping for VS2007:)
Page: << 1 2 3 4 >>