<p>As of the fall of 2008 I'm about to embark on a new development cycle for a major product that has a winforms and an asp.net interface.  We use Telerik, DevExpress and Infragistics components in it and all are going to have a release within a month or so which will be the one I target for our spring release of our product.  </p>

<p>They all support VS2005 and we will continue to target .net 2+ so I can't see any compelling reason so far to upgrade to VS2008.</p>

<p>Has anyone found a compelling reason for upgrading to VS2008?</p>

[{'answer_id': 64853, 'author': 'John Sheehan', 'author_id': 1786, 'author_profile': 'https://Stackoverflow.com/users/1786', 'pm_score': 4, 'selected': False, 'text': "<p>It's worth it. It's faster, the designer is vastly improved (split view, faster context switching), it has better support for javascript and when you're ready to target 3.5, you'll be ready to go.</p>\n"}, {'answer_id': 64866, 'author': 'Scott Dorman', 'author_id': 1559, 'author_profile': 'https://Stackoverflow.com/users/1559', 'pm_score': 3, 'selected': False, 'text': "<p>Yes, it's definately worth the upgrade. I would actaully say go straight to VS2008 SP1 as well. There have been a lot of IDE improvements (usability features and speed) and improvements in the web development experience as well including better JS and CSS support.</p>\n"}, {'answer_id': 64870, 'author': 'Joel Martinez', 'author_id': 5416, 'author_profile': 'https://Stackoverflow.com/users/5416', 'pm_score': 3, 'selected': True, 'text': "<p>If you have a release within a month, I'd suggest <strong>not</strong> upgrading.  Make the upgrade to 2k8 part of the next major release ... no reason you should risk something not working quite the same or some other complication if everything is working as is.</p>\n"}, {'answer_id': 64876, 'author': 'Zach', 'author_id': 8720, 'author_profile': 'https://Stackoverflow.com/users/8720', 'pm_score': 0, 'selected': False, 'text': "<p>It is worth the upgrade for me for the main reason that I can target different .NET versions (2, 3, 3.5) from the same IDE whereas in the past, one version of Visual Studio supported one version of .NET.</p>\n\n<p>The UI seems much more responsive now, but the core set of tools and processes hasn't changed that much.</p>\n"}, {'answer_id': 64910, 'author': 'SaaS Developer', 'author_id': 7215, 'author_profile': 'https://Stackoverflow.com/users/7215', 'pm_score': 2, 'selected': False, 'text': "<p>To add to John's post, there is also built in unit testing, built in refactoring, code analysis, and the web designer for html\\javascript is vastly improved.  I can't think of any reason why you wouldn't upgrade.</p>\n"}, {'answer_id': 64955, 'author': 'Mark Cidade', 'author_id': 1659, 'author_profile': 'https://Stackoverflow.com/users/1659', 'pm_score': 3, 'selected': False, 'text': '<p>These are Microsoft\'s <a href="http://download.microsoft.com/download/3/B/D/3BDDC5D5-E8CF-4031-A12A-B072ECA27C42/VS2008PETopTenFSEMEA.doc" rel="nofollow noreferrer">10 reasons to upgrade</a> (.DOC):</p>\n\n<ol>\n<li>LINQ support</li>\n<li>Same designer elements as Microsoft Expression (Web and Blend)</li>\n<li>AJAX and WCF/REST</li>\n<li>Better WPF support</li>\n<li>Improved MSTEST (also included in Professional edition)</li>\n<li>Improved HTML, CSS, and JavaScript editors</li>\n<li>Choose from Project settings which version of the framework to target</li>\n<li>Improved Office dev tools, including ribbon UI and Click-Once support </li>\n<li>Integrated WCF and WWF support</li>\n<li>Better performance and stability</li>\n</ol>\n'}, {'answer_id': 64987, 'author': 'Community', 'author_id': -1, 'author_profile': 'https://Stackoverflow.com/users/-1', 'pm_score': 0, 'selected': False, 'text': '<p>The new C# language features are compelling for me:</p>\n\n<p>automatic properties, object initializers, collection initializers, extension methods, lambda expressions.</p>\n\n<p>For a quick overview from the guy responsible, see:\n<a href="http://weblogs.asp.net/scottgu/archive/2007/03/08/new-c-orcas-language-features-automatic-properties-object-initializers-and-collection-initializers.aspx" rel="nofollow noreferrer">http://weblogs.asp.net/scottgu/archive/2007/03/08/new-c-orcas-language-features-automatic-properties-object-initializers-and-collection-initializers.aspx</a>\n<a href="http://weblogs.asp.net/scottgu/archive/2007/03/13/new-orcas-language-feature-extension-methods.aspx" rel="nofollow noreferrer">http://weblogs.asp.net/scottgu/archive/2007/03/13/new-orcas-language-feature-extension-methods.aspx</a>\n<a href="http://weblogs.asp.net/scottgu/archive/2007/04/08/new-orcas-language-feature-lambda-expressions.aspx" rel="nofollow noreferrer">http://weblogs.asp.net/scottgu/archive/2007/04/08/new-orcas-language-feature-lambda-expressions.aspx</a></p>\n'}, {'answer_id': 64998, 'author': 'Community', 'author_id': -1, 'author_profile': 'https://Stackoverflow.com/users/-1', 'pm_score': 0, 'selected': False, 'text': "<p>I agree with Mr. Martinez in that I wouldn't port any existing projects up to the 3.5 framework, but the split designer and javascript debugging is worthwhile on its own.</p>\n"}, {'answer_id': 65005, 'author': 'ADB', 'author_id': 3610, 'author_profile': 'https://Stackoverflow.com/users/3610', 'pm_score': 0, 'selected': False, 'text': "<p>Upgrade, you will not regret it in the slightest. In particular, Linq is going to make your life so much easier. There there are the extensions for c#.</p>\n\n<p>That's barely touching the surface, there is certainly new toys in the area you are developing as well, either web, desktop or server.</p>\n"}, {'answer_id': 65012, 'author': 'Jeremy', 'author_id': 8557, 'author_profile': 'https://Stackoverflow.com/users/8557', 'pm_score': 0, 'selected': False, 'text': '<p>I\'d upgrade, but set aside some time for the install process. It took two hours on my moderately fast dev workstation, and I\'m still doing updates, patches, hotfixes, two hours after the install finished...  (haven\'t gotten any "real work" done today at all!)</p>\n'}, {'answer_id': 65068, 'author': 'Saul Dolgin', 'author_id': 8305, 'author_profile': 'https://Stackoverflow.com/users/8305', 'pm_score': 0, 'selected': False, 'text': '<p>It is helpful in the particular case you describe.  Consider the following:</p>\n\n<p>1) You are at the start of a development cycle.  It is always easier to make these types of changes at the start of or between cycles as opposed to in the middle of one.  Given this principle, your next convenient time to upgrade (if the schedule is not delayed) would be next Spring.  </p>\n\n<p>2) VS2008 allows for the compiler to target any specific .NET runtime version including 2.0 if you need to continue supporting an older framework.</p>\n\n<p>Also, as some of the other answers have suggested, go straight to SP1.  The service pack upgrade experience was not nearly as big of an ordeal as VS2005 SP1... at least in my experience.</p>\n'}, {'answer_id': 65564, 'author': 'JRoppert', 'author_id': 6777, 'author_profile': 'https://Stackoverflow.com/users/6777', 'pm_score': 0, 'selected': False, 'text': "<p>VS 2008 is not the point. The latest .Net package is the point. You can use Linq and all the other new Features with notepad and the commandline compiler but i guess that is more theoretical. So my statement is yes, .net 3.5 is the recommendation but using it without VS 2008 isn't a good idea.</p>\n"}]
['https://Stackoverflow.com/questions/64839', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/8939/']