Reasons for upgrading from VS2003 to VS2008
-
I received an email that we would not be doing the upgrade unless I can provide 'business reasons' for why we should upgrade. I'm doing some research on my own, but thought that you guys could give me quite a few that I would probably overlook. Thanks!
i went from sharpDevelop(studying) to VS2008(started working) some of my SharpDev versions crashed frequently, i dont know how stable VS2003 or VS2005 was but ive yet to crash VS2008 also you can change the target framework (2.0, 3.0, 3.5) with the click of a button which is kinda cool :bob:
Harvey Saayman - South Africa Junior Developer .Net, C#, SQL
you.suck = (you.passion != Programming) -
Because mainstream support ends in October[^]?
Jon Sagara On a traffic light yellow means yield, and green means go. On a banana, it's just the opposite, yellow means go ahead, green means stop, and red means, where'd you get that banana? -- Mitch Hedberg .NET Blog | Personal Blog | Articles
I really should learn to refresh the window when I spend 8 minutes looking for the link to the support lifecycle web page. :)
Simon
-
I received an email that we would not be doing the upgrade unless I can provide 'business reasons' for why we should upgrade. I'm doing some research on my own, but thought that you guys could give me quite a few that I would probably overlook. Thanks!
jchigg2000 wrote:
'business reasons' for why we should upgrade
Does adding a new tool to your resume qualify as one?
-
I received an email that we would not be doing the upgrade unless I can provide 'business reasons' for why we should upgrade. I'm doing some research on my own, but thought that you guys could give me quite a few that I would probably overlook. Thanks!
WPF and WIC if you do a lot of work with graphics. Still have to agree with a couple of the above posts biggest is loss of support.
this thing looks like it was written by an epileptic ferret Dave Kreskowiak
-
I received an email that we would not be doing the upgrade unless I can provide 'business reasons' for why we should upgrade. I'm doing some research on my own, but thought that you guys could give me quite a few that I would probably overlook. Thanks!
.NET 2.0 has a lot more features than 1.1. They really went through and enhanced the API set a lot. Generics are a great addition to the Framework - no more casting when getting data from collections, and no more boxing and unboxing of value types. In addition, they went through a large amount of stabilisation and reliability work for the inclusion in SQL Server 2005 (as CLR stored procedures, functions, etc). To develop for .NET 2.0, you could go for Visual Studio 2005 or 2008. I haven't really tried it yet, but VS2008 should be better on Windows Vista than 2005 which requires a special update. Visual Studio .NET 2003 is not officially supported on Windows Vista - even though it's still in support on other platforms, they won't support you on Vista.
DoEvents: Generating unexpected recursion since 1991
-
I received an email that we would not be doing the upgrade unless I can provide 'business reasons' for why we should upgrade. I'm doing some research on my own, but thought that you guys could give me quite a few that I would probably overlook. Thanks!
These are great! I agree that loss of support would be one of the main ones. I'm not sure if adding another tool to my resume is going to be a selling point! :) They are concerned with having to 'support' multiple development tools...we still have some VB6!!
-
i went from sharpDevelop(studying) to VS2008(started working) some of my SharpDev versions crashed frequently, i dont know how stable VS2003 or VS2005 was but ive yet to crash VS2008 also you can change the target framework (2.0, 3.0, 3.5) with the click of a button which is kinda cool :bob:
Harvey Saayman - South Africa Junior Developer .Net, C#, SQL
you.suck = (you.passion != Programming)HarveySaayman wrote:
ive yet to crash VS2008
You aren't trying hard enough young man.
My blog is acceptably unique.
-
HarveySaayman wrote:
ive yet to crash VS2008
You aren't trying hard enough young man.
My blog is acceptably unique.
bwhahaha! perhaps not, but Ive only been using it since January... maybe Microsoft hasn't "flicked the switch" yet :laugh:
Harvey Saayman - South Africa Junior Developer .Net, C#, SQL
you.suck = (you.passion != Programming) -
- Better gradients - Toolbar icons more inline with the blurry, illegible Office 2003 icons. - Because Microsoft released it Don't feel bad, until a month ago I was still on VS 2003 at work. Now I have VS 2005, but as far as I know no one at work has 2008.
¡El diablo está en mis pantalones! ¡Mire, mire! Real Mentats use only 100% pure, unfooled around with Sapho Juice(tm)! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! VCF Blog
Jim Crafton wrote:
as far as I know no one has 2008.
I have VS 2008 :) but you don't me :)
Thanks and Regards, Michael Sync ( Blog: http://michaelsync.net)
-
I received an email that we would not be doing the upgrade unless I can provide 'business reasons' for why we should upgrade. I'm doing some research on my own, but thought that you guys could give me quite a few that I would probably overlook. Thanks!
I'm in the same boat, pushing for an upgrade but need to provide more compelling reasons than "it will be slightly faster and less annoying to develop". Ending support is an interesting reason, but the first question from management will be what does Microsoft supporting vs2003 get me? It's not like there's a hot-line that I can call with questions. Also, it would seem to me from that chart that support ended in 10/9/2007 three quarters of a year ago. The best that I can come up with is "you're going to have a tough time hiring good people to work with shitty tools" but since I'm the only developer and they have no plans of expanding the team that's not too compelling either...
-
- Better gradients - Toolbar icons more inline with the blurry, illegible Office 2003 icons. - Because Microsoft released it Don't feel bad, until a month ago I was still on VS 2003 at work. Now I have VS 2005, but as far as I know no one at work has 2008.
¡El diablo está en mis pantalones! ¡Mire, mire! Real Mentats use only 100% pure, unfooled around with Sapho Juice(tm)! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! VCF Blog
Jim Crafton wrote:
but as far as I know no one has 2008
I've been using it for months - It is great!
Recent blog posts: * Introduction to LINQ to XML (Part 1) - (Part 2) - (part 3) My website | Blog
-
I'm in the same boat, pushing for an upgrade but need to provide more compelling reasons than "it will be slightly faster and less annoying to develop". Ending support is an interesting reason, but the first question from management will be what does Microsoft supporting vs2003 get me? It's not like there's a hot-line that I can call with questions. Also, it would seem to me from that chart that support ended in 10/9/2007 three quarters of a year ago. The best that I can come up with is "you're going to have a tough time hiring good people to work with shitty tools" but since I'm the only developer and they have no plans of expanding the team that's not too compelling either...
I think if I was the only developer, I'd just start using the express edition until they went ahead and upgraded.
-
WPF and WIC if you do a lot of work with graphics. Still have to agree with a couple of the above posts biggest is loss of support.
this thing looks like it was written by an epileptic ferret Dave Kreskowiak
What is WIC?
Thanks and Regards, Michael Sync ( Blog: http://michaelsync.net)
-
I received an email that we would not be doing the upgrade unless I can provide 'business reasons' for why we should upgrade. I'm doing some research on my own, but thought that you guys could give me quite a few that I would probably overlook. Thanks!
What kind of projects do you work on? What size are they?
Todd Smith
-
Jim Crafton wrote:
but as far as I know no one has 2008
I've been using it for months - It is great!
Recent blog posts: * Introduction to LINQ to XML (Part 1) - (Part 2) - (part 3) My website | Blog
Hardy, har har, should have written "but as far as I know no one at work has 2008"
¡El diablo está en mis pantalones! ¡Mire, mire! Real Mentats use only 100% pure, unfooled around with Sapho Juice(tm)! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! VCF Blog
-
I'm in the same boat, pushing for an upgrade but need to provide more compelling reasons than "it will be slightly faster and less annoying to develop". Ending support is an interesting reason, but the first question from management will be what does Microsoft supporting vs2003 get me? It's not like there's a hot-line that I can call with questions. Also, it would seem to me from that chart that support ended in 10/9/2007 three quarters of a year ago. The best that I can come up with is "you're going to have a tough time hiring good people to work with shitty tools" but since I'm the only developer and they have no plans of expanding the team that's not too compelling either...
Togakangaroo wrote:
Ending support is an interesting reason, but the first question from management will be what does Microsoft supporting vs2003 get me? It's not like there's a hot-line that I can call with questions.
Well, actually, there is a hot line you can call with questions. If you have an MSDN subscription you get some free calls, if not, you pay per "incident". But more importantly, "support" is a guarantee from Microsoft that the product will continue to work. Once support ends, you have no guarantee that it will still work. MS might release a patch to windows to fix some critical security flaw, but in doing so, breaks VS2003, well they aren't going to care.
Simon
-
What kind of projects do you work on? What size are they?
Todd Smith
I work for a large health insurance company. Many of the projects are > 1yr in development time, so fairly large.
-
VS 2003 is really suck. If you are using VS 2005 or 2008, you won't look back to VS 2003. Upgrade it ~ - if you want to improve the developer's productivity - if you want to develop .NET 2.0 or 3.0 or 3.5 projects. (ASP.NET 3.5 or 2.0 is really awesome. ) etc
Thanks and Regards, Michael Sync ( Blog: http://michaelsync.net)
You need to correct your grammar. It should be: "VS 2003 is teh suck"
cheers, Chris Maunder
CodeProject.com : C++ MVP
-
I'll give you one dam good one: Mainsteam support ends this year[^]. Forget the rest, don't use unsupported software to develop your app's you're only asking for trouble.
Simon
-
I received an email that we would not be doing the upgrade unless I can provide 'business reasons' for why we should upgrade. I'm doing some research on my own, but thought that you guys could give me quite a few that I would probably overlook. Thanks!
Because, like, it's currently 2008, and Visual Studio is called "Visual Studio 2008" so they, like, go together. Like Peanut butter and Jam. Or something. Just tell him all the cool kids are using VS 2008 and he doesn't want to be considered uncool, right?
cheers, Chris Maunder
CodeProject.com : C++ MVP