151 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Jeffrey commented  ·  May 23, 2013 6:04 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Microsoft... Action required here!

• John Saunders commented  ·  May 22, 2013 5:58 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Because Microsoft felt like it?

• Richard commented  ·  May 22, 2013 4:33 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  @John: If updates to .NET for XP ended in 2009, then why does it support 4.0, which was released in April 2010?

• John Saunders commented  ·  May 21, 2013 9:56 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  @PR: you're mistaken. Windows XP has one more year of "Extended Support". Take a look at http://support.microsoft.com/gp/lifepolicy and you'll see that Extended Support includes paid support, security update support, Microsoft Knowledge Base, and the Microsoft Support site.

  It does not include updates to the Microsoft .NET Framework. That might have been included in Mainstream Support, but that ended back in 2009.

• PR commented  ·  May 21, 2013 9:51 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  what the ****? there is still one more here till xp support is dropped. why the **** is microsoft being so unsupportive? technically, anyone can file a law suit again microsoft for not making dot net fx work on windows xp because although it is microsoft life cycle policy, windows xp has one more year

• LS commented  ·  May 16, 2013 7:54 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Ballmer says, "Developers, developers, developers!"

  .Net and VS teams say, "Go f--- yourselves!"

• Anonymous commented  ·  May 13, 2013 7:04 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  VS 2012 Loss platform independent character. so it is a failure product.

• Otto commented  ·  April 18, 2013 6:23 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Well, thanks Mic.
  Nice strategy. Distributed vendor lock-in.
  Let the programmers convince their clients to upgrade.

  I don't know if I will be able to convince my boss to free budget to upgrade servers OS, SQLServers version, desktops OS, let alone force the clients to do it, only to make the development proces somewhat easier.

  You're probably not aware of some economic and financial problems here and there (around the world but probably not in Redmond).

  How about some intrinsic supporting argumentation instead of 'not in our support policy', like 'We can't get it to work on XP because of ... , or it will have a terrible impact on the ...'.

• Nelson Reis commented  ·  April 15, 2013 5:44 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  As James said, the result of this decision on my company was to not update to the latest framework.

  So if Microsoft wanted to force more updates from older OS by this decision, maybe it is getting the opposite results... it's called the Cobra Effect: http://en.wikipedia.org/wiki/Cobra_effect

• Anonymous commented  ·  April 15, 2013 1:03 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  This is ridiculous for the Commercial industry, we have clients that simply can't afford to upgrade their servers every 3 years to keep in line with Microsoft's release schedule.

  Please re-visit this decision as it will only result in a smaller uptake of the latest framework.

  Thank you.
  James.

• Ron Barone commented  ·  April 10, 2013 4:24 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  My God. I run into CONSTANT problems with WPF bugs that happen in XP but cant be reproduced on a system with .NET 4.5. These are deep rooted bugs in threading (multiple dispatchers) and even in dataset binding. Microsoft is making it VERY hard on the developers over on this and will not cause any innovation or forced OS upgrades because the devs cant force their paying business users to upgrade machines "just because". So us as developers spend countless wasted hours in testing and debugging on two separate platforms. Very frustrating that the targeting uses 4.5 and not 4.0 code. Even if the targeting used 4.0 DLLs so we could debug the code we write it would be more than helpful.

• The Angry Guy commented  ·  March 30, 2013 3:21 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Microsoft. There billions of dollars aren't enough. They want us to buy the latest OS for this to work. This is not fair, I as a user, cannot use programs usable on 7 and 8. I just bought an unusable program, because Microsoft is being lazy. Wow, just wow.

• Stephen Dickinson commented  ·  March 22, 2013 2:45 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I find myself in yet another catch 22 mess with Microsoft. I find problems with .NET 3.5 mean that VS2012 C# programs will not work on my Win-7 dual monitor PC configuration, where as .NET 4.5 will - I am therefore forced to use .NET 4.5. However I have customers who still use Win-XP. Please can you make Win-XP/.NET 4.5 compatible.

  I am appalled the way Microsoft treat it's customers - forcing people to purchase later software and OS versions when what they have is quite adequate. It wouldn't be so bad if the new software was a real improvement and not just a marketing/sales gimmick (having tried Win-8 I have actually moved back to Win-7) .

• Scott commented  ·  March 20, 2013 4:58 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Just spent 4 months updating 2 million lines of code to 4.5 to use Async. Most of the target machines are still on XP

• Richard commented  ·  March 7, 2013 3:29 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  @Minni: No, a .NET 4.5 application won't work on XP. You'll need to change it to target 4.0 and test it thoroughly on a computer which doesn't have 4.5 installed to make sure you're not depending on bug-fixes which aren't available for XP.

• Minni commented  ·  March 6, 2013 5:55 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  We are developing a WPF application using VS2012 and .net framework 4.5. It'll be installed on some of the Windows XP systems so will it work or not.
  If not, can we make it work using some pack ?

• lucho commented  ·  March 5, 2013 11:44 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  dude, make it for xp, dont be a dork ...

• Anonymous commented  ·  February 20, 2013 3:13 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  You are losing on this Move. I don't expect my company to move our development PC's from Windows XP in the next years so i'm stuked using vb 2010 for the next years

• Anonymous commented  ·  February 19, 2013 7:52 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Just got completely screwed by this one. Thanks Microsoft! Let me go undo all of our work for the last 2 weeks. Bunch of f*!?!(* m-o-r-o-n-s. Why would you make a ".5" release do something as major as discontinuing one of the most popular operating systems in the world?!?!?!?

• Nick commented  ·  February 1, 2013 5:21 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  This is a bad dream. I guess I just assumed it would work. We just finished updating our 4.0 based application to use async. 6 months wasted. Need to go back to 4.0. 90% of our customers us XP. Perhaps we can use the asyncctp.