|
As an independant developer I have found that I can produce better code, faster using c# than C++.
My investment in VS2003 and C# has paid off .
Productivity and language improvements in .NET 2 and the new VS200x will make my life easier. (I hope!) I don't think my ROI on 200x will be as much as in the VS2003 case.
M Dunn is right , you can produce great s/w with VS6 , why wouldn't you be able to? Will the new safe libs for VC++ make his software better? Probably.
My software is used in an environment that I control and not in a large corprate roll-out so any new framework bugs etc are fairly easily 'compensated' for.
I must admit , I love change and the whole learning proccess. If MS had a fan club, I would be in it.
Arrgghhh $549 . I hereby retract all above comments.
.nuetter
|
|
|
|
|
Give an example of 'better code, faster' using c#.
|
|
|
|
|
I like to think of myself as an under funded developer. Not someone who is left behind. I have run a few of my WxWidgets projects through the First Beta of Visual C++ 2005, and liked the results. I may continue on down that road some day if I can find the funds.
|
|
|
|
|
The Express versions of VS will only be $49.
That's pretty affordable.
--
Where are we going? And why am I in this handbasket?
|
|
|
|
|
Thanks for the tip. The express version is more then enough for the projects that I will be using it for.
|
|
|
|
|
David Gallagher wrote:
Just put your money on the table and hold your breath.
I don't think so
Johan Rosengren
|
|
|
|
|
For now I will stick with VS.NET 2003 but when I consider it necessary I will upgrade to VS.NET 2005.
|
|
|
|
|
Being a AutoCAD/ObjectARX developer I am stuck with the horrible VS2002 version for at least another year.
Johannes
|
|
|
|
|
Actually, I was playing even with Beta 1, but to actually migrate the production code to VS 2005 I'll wait at least 3 months after the release. The things I am looking forward most are C++/CLI and new VSS. Anyway, I don't expect this to be a huge leap such as moving from VC++ 6 to VC++ 7.1
My programming blahblahblah blog. If you ever find anything useful here, please let me know to remove it.
|
|
|
|
|
Some of us are too poor for £500-odd in one go
|
|
|
|
|
Yeah, but thats $500, which these days is probably about £100.
(I know, I'm just kidding).
|
|
|
|
|
Upgrading a compiler while a project is active or nearing completion is just plain dumb. A new compiler changes the resulting program completely, and you will invalidate all of your testing and possibly introduce new bugs - if you are lucky enough to get all your code to compile. The danger is even worse if you have any 3rd party or open-source components.
The last time we upgraded a compiler, it was before we started doing work on the next version of our stuff, and we kept around the old one for the "legacy" code. This upgrade, if we do it at all, will be no different. That could be any arbitrary amount of time after 2005 is released.
The generation of random numbers is too important to be left to chance.
|
|
|
|
|
Besides the cycle of our own procduct, we should make sure our developing partner are ready to upgrade to VS 2005, because we use some of 3rd-part tools and libraries.
I am flying
|
|
|
|
|
I am just interested to know why some people voted they were already using VS 2005, considering that its not legal to be running any production code on this. Are you using this purely for testing purposes?
|
|
|
|
|
Beta 2 has a Go-Live[^] license. I downloaded Beta 2 on Saturday night, making "Already using it" a valid choice (though it wasn't my choice).
Charlie
if(!curlies){ return; }
|
|
|
|
|
As a part of my internship I have to "experiment" with VS 2005. I have to learn as much as I can from it and advise about if the company should migrate or not. Back at home I'm already migrating my C++ code.
I also got the blogging virus..[^]
|
|
|
|
|
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![^]
|
|
|
|