VS.2005 is it really usable ?
-
For serious professional C++/MFC (95%) and some C# (5%) ? It seems that I'm reading horrible stories about how bad the product is ( project performances, intellisense, ... ) ! We're mostly upgrading from VC6, I'm using VS.2003 which is working fine. Is it worth it to go to VS.2005? or should we wait and buy VS.2003 ( if that is still possible ) and upgrade later ? Thanks.
Maximilien Lincourt Your Head A Splode - Strong Bad
Without the various clarions of Micro$soft suxx, which unimpresses many as better suited for the open-source utopians sequestered at slashdot, the advice would be to install VS 2005. The ambition of many; perhaps not all, coders is to progress; a regression to VS 2003 is not in that path. The only appropriate concern for any company is a loss in revenue and Microsoft certainly understands this. The issues with VS 2005 will be fixed; if not, the market will migrate to another IDE and language.
-
Jörgen Sigvardsson wrote:
(Although, the compiler isn't all that safe, and may explode in your face, should you use anything fancy)
Yeah, like properly scoped for-loops! X| I've been writing the VS6 specific bits of Visual Lint (i.e. the VSPackage itself, which has to use MFC42) in VS6 and boy is it painful after 3 years of using VS2003 (the automation interface both sucks and blows too). :doh: Anna :rose: Currently working mostly on: Visual Lint :cool: Anna's Place | Tears and Laughter "Be yourself - not what others think you should be" - Marcia Graesch "Anna's just a sexy-looking lesbian tart" - A friend, trying to wind me up. It didn't work.
Anna-Jayne Metcalfe wrote:
both sucks and blows too
It should be noted that it does not do so concurrently. It's not that good. :-D
-- 100% natural. No superstitious additives.
-
Without the various clarions of Micro$soft suxx, which unimpresses many as better suited for the open-source utopians sequestered at slashdot, the advice would be to install VS 2005. The ambition of many; perhaps not all, coders is to progress; a regression to VS 2003 is not in that path. The only appropriate concern for any company is a loss in revenue and Microsoft certainly understands this. The issues with VS 2005 will be fixed; if not, the market will migrate to another IDE and language.
Grav-Vt wrote:
the advice would be to install VS 2005. The ambition of many; perhaps not all, coders is to progress; a regression to VS 2003 is not in that path.
You're not a C++ programmer, are you? :suss: The compiler may be sweet, but the IDE sucks for C++ development. Intellisense is always 4 builds behind.. :(
-- 100% natural. No superstitious additives.
-
I'd say go with VS 2005 - expect some IDE speed issues, specially for C++. But the SP will be out by end of this year and hopefully it will all be good then. Regards, Nish
Nish’s thoughts on MFC, C++/CLI and .NET (my blog)
Currently working on C++/CLI in Action for Manning Publications. Also visit the Ultimate Toolbox blog (New)We were using VS2003 for some time, and moved to VS2005 as soon as it was available to us. Yes, there speed of the IDE was frustrating, but overall our productivity has increased. VS2005 and .Net2 are VASTLY better than their earlier versions. (Hope I'm not off topic here, because my experience is limited here to C#, ASP and a bit of VB) :)
-
Don't forget the service pack for VS.Net 2003 - target is June 2006! We're waiting expectantly :) But you know MS... not the most reliable when it comes to deadlines. http://msdn.microsoft.com/vstudio/support/servicing/sp1_vs03/default.aspx mt
-
For serious professional C++/MFC (95%) and some C# (5%) ? It seems that I'm reading horrible stories about how bad the product is ( project performances, intellisense, ... ) ! We're mostly upgrading from VC6, I'm using VS.2003 which is working fine. Is it worth it to go to VS.2005? or should we wait and buy VS.2003 ( if that is still possible ) and upgrade later ? Thanks.
Maximilien Lincourt Your Head A Splode - Strong Bad
ummm your mileage may vary. But on a philosophical plane : VS 2005 is a keeper. I have been using MS development environments since... let's see... VB1... (I did C on Windows before that, but there was no "environment") I have used just about everything in between, either occasionally or intensively. There are good products and bad products, the equivalent of Windows 95 and Windows ME respectively. I have just finished two weeks doing C# on VS 2005, and I'm very pleased with it, i.e. it's a quantum leap in productivity. I especially like the Source Safe integration and the deployment aids. Alistair (no quote, no logo)
-
For serious professional C++/MFC (95%) and some C# (5%) ? It seems that I'm reading horrible stories about how bad the product is ( project performances, intellisense, ... ) ! We're mostly upgrading from VC6, I'm using VS.2003 which is working fine. Is it worth it to go to VS.2005? or should we wait and buy VS.2003 ( if that is still possible ) and upgrade later ? Thanks.
Maximilien Lincourt Your Head A Splode - Strong Bad
VS2005 is first usable version for writing mixed managed/unmanaged applications. In previous versions, it was possible to write pure .NET applications or pure unmanaged applications. Managed C++ which is supposed to be bridge between managed and unmanaged world, was buggy and unusable. After learning some mixed programming samples written in 2005 version, specifically, Managed Spy++ from MSDN Magazine, I decided to change development platform from MFC to C#, C++/CLI. BTW, I am developing real time applications, so this decision was not trivial. Intellisence problems can be solved with Visual Assist. Standard Microsoft reply to Intellisence problem is "You have some bugs in your code". In any case don't start with 2003 version. 2005 version has new C++/CLI syntax, code written in previous version is complied only with /oldsyntax flag, and generally, should be rewritten.
-
Not for critical appdev it's not, too many hiccups and uncertainties. And much of it's documentation out of date (eg it barely acknowledges NET2.0 and C#2.0), much of it is useless, the english is atrocious, full of split infinitives and sentences ending in prepositions; which results in it being ambiguous and downright misleading at times. I've not used VS for C/C++, I'm still working at the > for that sort of work.