Forum C# Updating to 2.3 and VS2008

Updating to 2.3 and VS2008

Postby partybrian5000 » January 4th, 2012, 11:25 pm

Hey guys, I'm being told repeatedly to update by the development server jobby, but when I go to update it turns out that I can no longer use the VS2008 solutions and would have to upgrade to 2010 in order to use the product. Is VS2010 absolutely needed for the Net4.0 nonsense or is it possible for you to provide a 2008 friendly set up. I heavily prefer using VS2008 over 2010 and given that I have no use for .NET 4.0 features and I can't seem to be able to turn off the update thing from popping up every few hours, not to mention I don't want to use outdated stuff (for example I now get some thread hanging exception warning or something sporadically that I hadn't experienced until today) if I can avoid it.
partybrian5000
 
Posts: 3
Joined: September 28th, 2011, 7:37 pm

Re: Updating to 2.3 and VS2008

Postby Oliver » January 5th, 2012, 1:53 pm

Hey,

Sorry but a consequence of supporting .NET 4.0 (a MUCH requested feature) was that the development server itself has to run 4.0.

Sadly visual studio 2008 does not support .NET 4.0 apps.

You can use the free Visual Studio 2010 Express instead of upgrading the full studio. Personally I've found 2010 to be much faster and more stable than 2008.

You can continue using the old version (as long as you can live with the update dialogs). At some point, we'll make a change on the backend that requires that you upgrade to the newst version, and then you'll be required to upgrade.
I'm not sure, but i think one of those changes is planed for one of the next release.

I'm very sorry about the inconvenience. We know that upgrading to .NET 4.0 would cause some troubles, but we felt it was the right time to do it and that the benefits outweigh the problems.

Best,
Oliver
User avatar
Oliver
.IO
 
Posts: 1159
Joined: January 12th, 2010, 8:29 am

Re: Updating to 2.3 and VS2008

Postby partybrian5000 » January 23rd, 2012, 7:19 pm

Thanks for the reply, I updated and while i'd still prefer VS2008 it's not a huge deal. It would be good if you could make this clearer to other people updating as it looked more like you forgot to include a 2008 solution rather than an intentional deprecation enforcement or whatever this would be called.
partybrian5000
 
Posts: 3
Joined: September 28th, 2011, 7:37 pm


Return to C#