Visual Studio 2012 Update 1's XP targeting not work for project with blank Subsystem property - by Trout.Z

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


5
0
Sign in
to vote
ID 773506 Comments
Status Closed Workarounds
Type Bug Repros 3
Opened 12/5/2012 1:30:27 AM
Access Restriction Public

Description

When update 1 for 2012 issued, I tried it, and found some of my projects are not XP compatible by using v110_xp, and then I found that it's because they've got empty Subsystem specified.
Sign in to post a comment.
Posted by Microsoft on 4/29/2014 at 12:31 PM
Thank you for reporting this issue. This issue has been fixed in Visual Studio 2013. You can install a trial version of Visual Studio 2013 with the fix from: http://go.microsoft.com/?linkid=9832436
Posted by Microsoft on 2/8/2013 at 6:00 PM
Hello Trout.Z
Thank you openning a Connect report. We will be adding a warning to address this issue.
Felix Huang
VC++ Project & Build
Posted by Microsoft on 2/8/2013 at 6:00 PM
Hello Trout.Z
Thank you openning a Connect report. We will be adding a warning to address this issue.
Felix Huang
VC++ Project & Build
Posted by Microsoft on 12/6/2012 at 12:12 AM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Posted by Shane Hickson on 12/5/2012 at 3:06 AM
Expected results (rehashed):

The output exe "SHOULD" run on XP, "AND" output window "SHOULD" give some waring message telling me it's not working due to blank Subsytem.

Please fix it !
Posted by Microsoft on 12/5/2012 at 1:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)