support XP for 4.5 until the end of XP support!
So many entreprises have to continue to support XP because microsoft themself still support it until 2014!
Because of this we have to ban 4.5 development on any products that is sold externally.
Please come back on this marketing decision and provide a 4.5 framework that the entreprises can work with!
Thanks SlickRick and everyone else for sharing feedback on this issue. We have published Visual Studio 2012 supported platforms here: http://www.microsoft.com/visualstudio/11/en-us/products/compatibility.
While Windows XP and Windows Server 2003 are not supported by .NET Framework 4.5, they remain as a supported targeted platform in Visual Studio 2012 by targeting .NET Framework 4.0. More information is available here: http://blogs.msdn.com/b/visualstudio/archive/2012/05/18/a-look-ahead-at-the-visual-studio-11-product-lineup-and-platform-support.aspx.
For those still needing to support Windows XP and Windows Server 2003, we’ve added value down-level to .NET Framework 4.0 from 4.5 via platform updates (4.0.1, 4.0.2 and 4.0.3) and standalone libraries (http://blogs.msdn.com/b/bclteam/archive/2012/10/22/using-async-await-without-net-framework-4-5.aspx and http://nuget.org/packages/Microsoft.Net.Http).
.NET Framework Team
Peter has right. Windows XP and Windows Server 2003 are not supported for .NET Framework 4.5.
It would be nice to be able edit vbscript in Visual Studio using intellisense.
scH4MMer, exactly which issue are you referring to?
This is a real head scratcher. How do I make the case to my manager for upgrading to VS2012 when this issue could come back to bite us? What is Microsoft's explanation for putting us in this position?
Some of the readers of this idea may also be interested in http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/3127346-support-a-net-4-0-service-pack-on-windows-xp-supp.
Peter S commented
Is this not the same suggestion that MS already has declined ?
Reinhard Ostermeier commented
@John Saunders: oh, sorry for that. I got there something wrong then.
@Reinhard: you may misunderstand: I don't work for Microsoft. I have no colleagues to whom to bring this.
Reinhard Ostermeier commented
I have voted for this, even that I know that the chance MS releases 4.5 for XP is low.
As an good enough alternative I would like to see an .net service pack for XP.
Now that even John Saunders says he would vote for this I see a good chance that this could happen.
Mr. Saunders, may be you coluld bring this directly to your colleges, if not already happend.
Also a comment like 'I would vote for a request for an "XP service pack" that fixes the same .NET 4,0 bugs that are fixed in .NET 4.5. I do not support a request to implement .NET 4.5 on XP.' in the forum you mentioned would colld down the discussion there for sure.
@Jamie Clayton, do you see this affecting developers who can test their products on XP machines (running .NET 4.0). The problem that I'm aware of is developers who must develop and test on the same machine.
Jamie Clayton commented
I suspect this will be a barrier to entry for Windows 8 and VS2012 adoption by the developer community if this isn't addressed.
(I wish we could edit comments)
I would vote for a request for an "XP service pack" that fixes the same .NET 4,0 bugs that are fixed in .NET 4.5. I do not support a request to implement .NET 4.5 on XP.
To reiterate, there is no problem in using Visual Studio 2012 to develop code targeted for .NET 4.0 and Windows XP - unless you're depending on using the development machine to perform QA. As long as your QA system is running the same version of .NET as your customers will be using, there should not be a problem.
The greatest issue, as expressed in http://social.msdn.microsoft.com/Forums/en-US/wpf/thread/c05a8c02-de67-47a9-b4ed-fd8b622a7e4a/, involves developers who must both develop and test on a single machine. As such, they can't upgrade to Visual Studio 2012, since that would fix certain .NET 4.0 bugs on their lone machine. They would not know that they were depending on fixed bugs until their customers found the bugs in .NET 4.0, running on XP.
For just about anyone else, I would suggest that you test on XP if your customers require XP.
At the very least, the bug fixes introduced in 4.5 need to be made available on XP for 4.0 either as a service pack or a large patch. We absolutely must have parity in terms of stability, even if feature parity is not possible.
This also applies to Windows 7 PCs that still run .NET 4