|
Apart from the fact that there's a go-live license, you don't have to be running production code on it. If you development cycle is longer than about 6-8 months, the product will probably be finished about the time yours is.
--
Where are we going? And why am I in this handbasket?
|
|
|
|
|
perhaps i am just feeling cynical today, but isn't this the same as voting "never"?
i would like to see a service pack for .NET 2003 so that i spend less time each day swearing at the IDE *sigh*
as for upgrading, work will either upgrade or they wont, and if they upgrade then i get upgraded. so i don't really have any say in the matter.
i expect to install beta 2 at home some time soon for my own purposes though.
zen is the art of being at one with the two'ness
|
|
|
|
|
Why do you feel cynical? You're perfect right! Working with VS2003 means having open VC6 in parallel (to work with resources) and a bunch of painting tools (if you've got to deal with bitmaps, pngs and alike).
The reason I use VC2003 is the sourcecode editor and the fact that MSDN wont integrate with VC6 anymore.
I think of evaluating VC2005, but if it doesn't fix the bugs in VC2003, I will stick with what I got.
|
|
|
|
|
then I will upgrade.
The perils of working for yourself. Having to choose between paying the mortage for a couple of months or buying a copy of VS 2005 Pro. Personally, I'd choose VS2005 but I don't think the bank would like it 
Michael
CP Blog [^] Development Blog [^]
|
|
|
|
|
Also think about countries that don't have such a great USD exchange rate. To be legal in some cases the cost might even be one months salary but not one months increase in productivity.
I went to DevWeek UK in Feb and the common phase from the presenters was "This feature will probably be removed in the next version because they don't have time to test it". Does that mean that the intended features for VS 2005 will be in VS 2006  I doubt the version after 2006 will be any cheaper.
Can you say "Obsolete by design" :->
http://doubin.forwardslash.com[^]
|
|
|
|
|
Doubin wrote:
Does that mean that the intended features for VS 2005 will be in VS 2006
With all the delays, it appears to me that VS2005 may become VS2006.
|
|
|
|
|
... I will upgrade when I need to?... i.e. when there are some features of the IDE that I actually need or would help me to be more productive in my job
Regards,
Brian Dela 
Co-author of the Microsoft Outlook Answer Book[^].
Now Bloging![^]
|
|
|
|
|
Well if you need to target .NET 2.0 then you'll need to upgrade. And ASP.NET 2, really does look sweet.
Michael
CP Blog [^] Development Blog [^]
|
|
|
|
|
Michael P Butler wrote:
Well if you need to target .NET 2.0 then you'll need to upgrade. And ASP.NET 2, really does look sweet.
Yes, both of those would fall under "when I need to or when it would make my work more productive"
Regards,
Brian Dela
Co-author of the Microsoft Outlook Answer Book[^].
Now Bloging![^]
|
|
|
|
|
You might want to check your link to the Outlook Answer book, I keep getting "Product not found". So unless the link is a subtle joke about how difficult it is to get answers to outlook problems, you may want to change it. 
Michael
CP Blog [^] Development Blog [^]
|
|
|
|
|
Thanks Michael. AW seemed to have removed the product page.
Regards,
Brian Dela
Now Bloging![^]
|
|
|
|
|
Brian Delahunty wrote:
when there are some features of the IDE that I actually need or would help me to be more productive in my job
Refactoring?
"A people that values its privileges above its principles soon loses both."
-- Dwight D. Eisenhower
|
|
|
|
|
jdunlap wrote:
Refactoring?
True.
Regards,
Brian Dela
Now Bloging![^]
|
|
|
|
|
If you can't find SOMETHING in VS2005 to improve your productivity or give you a feature that you really like then either you're not looking very hard, or you really aren't doing much programming.
--
Where are we going? And why am I in this handbasket?
|
|
|
|
|
I already use visual studio 2005 just because the IDE is improved enormously. I only miss the class wizard from VS 6.0, but I think that I'll get over it soon.
Some things I like about VS 2005:
<list>
Improved intellisense
Integrated testing (although I don't know how to use it yet)
Tabbed windows
Complete customizable GUI
Improved compiler
Support for native code
The things I don't like about VS 2005
<list>
No class wizard 
It crashed more than VS 6.0 (Good hopes for the official release)
I really hope that the official release becomes just as stable as VS 6.0, but with so many integrated features and customizable things there just have to be bugs...
I also got the blogging virus..[^]
|
|
|
|
|
It's a beta version you know, they tend to crash....
I think the official version won't crash that often if you report the crashes to microsoft. So they can do something about it
WM.
What about weapons of mass-construction?
|
|
|
|
|
Bob Stanneveld wrote:
Some things I like about VS 2005:
Improved intellisense
Integrated testing (although I don't know how to use it yet)
Tabbed windows
Complete customizable GUI
Improved compiler
Support for native code
That sounds promising, but I still haven't heard whether they fixed the bugs that really bother me in VC 2002. In particular, did they fix the bug in which they substituted numbers for command IDs in the resource file, and did they fix the bug in which when you used their code to automatically add a message handler to the mainframe in one project of the workspace, it would sometimes put the implementation in the other? These seem like major IDE failures to me, and I do not want to upgrade till they are fixed.
Nathan Holt
|
|
|
|
|
I didn't experiance any of those nasty things, but I haven't used the IDE very extensively. All I can say is that I'm very happy with it and that I will exploit it as much as I can.
I don't know if MS gives them in your neighbourhood, but here in holland, MS is giving free crash courses for migrating to VS 2005. I already put the date in my agenda .
I also got the blogging virus..[^]
|
|
|
|
|
I hope that they've fixed those bugs, especially the one that corresponds to message handler code generation.
Of course there are many others. IDE sometimes just hangs at startup utilizing 100% CPU. This somehow correlates with the number of open documents (hangs if there are no open documents).
Software is too expensive to build cheaply...
|
|
|
|
|
I think the guys at MS are implementing new features instead of fixing bugs and improving performance.
And the half class wizard is extremly slowly, its poor stuff.
I dont like in that you cant delete a member or a user definded function with the GUI. Also if you change the access mode for wizarded functions you get another access entry in the header file.
I hope the developers in MS have to use their actual product. 
But I bet the use VC 6, because the can debug W9x!!!
Try this @ home. (B&B)
|
|
|
|
|
I intend to use VC++ 6, VC++ 7.1 and VC++ 2005 side by side.
Nish
|
|
|
|
|
|
Bob Stanneveld wrote:
Why?
I have clients using VC6, some using VC 7.1 and some who will use VC 2005. So I've got to support all versions.
Nish
|
|
|
|
|
So he can get something else done in VC6 while waiting for the sluggish UI's to respond in 03 and 05.
onwards and upwards...
|
|
|
|
|
Nishant S wrote:
I intend to use VC++ 6, VC++ 7.1 and VC++ 2005 side by side.
The same for me. Got one active project on VC++ 6, a C++ project that uses VS2003 - neither of those will be using the new compiler. Its not worth the hassle.
All my C# projects will be upgrade to .NET 2.0, so VS2005 will be a must.
Michael
CP Blog [^] Development Blog [^]
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
