Search

Behavior of 'Utility' configurations changed by Hauke H

Closed
as Duplicate Help for as Duplicate

3
0
Sign in
 to vote
Type: Bug
ID: 780017
Opened: 2/26/2013 1:32:36 AM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug

I have a solution (see attachment) with two projects, one with a 'Configuration Type' being 'Application (.exe)' and the other one being a 'Utility'.


The application project is configured as the startup project and is depending on the utility. The 'Utility' project contains a file whose 'Item Type' is set to 'Custom Build Tool'. For the sake of demonstration, the custom build tool's command simply echos a message.


The issue: In VC10, the utility project was executed every single time the application was strated with Strg+F5 (or just F5). Each run printed the echo message. In VC12, the utility project is run only when the application is build, as if it were merely a pre-build event. VC12 seems to decide that after the utility project has been run once, it is up to date whereas I expect it to run every single time.
Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling Version

Visual Studio 2012

What category (if any) best represents this feedback?

 

Steps to reproduce


Open the attached solutions (each with its designated Visual Studio version). Configure the project 'bar' (the application) to be your startup project. Run the project twice with Ctrl-F5.

On VC10, each run prints 'Why am I not run every single time?', on VC12 only the first run prints this message.

Product Language

English

Operating System

Windows 7 SP1

Operating System Language

English

Actual results


On VC12, the utility command is only run once.

Expected results


Even on VC12, the utility command should be run every time.

Locale

 
File Attachments
File Name Submitted By Submitted On File Size  
utility solutions.zip Hauke H 2/26/2013 21 KB
utility vc12.zip Hauke H 2/26/2013 12 KB
Sign in to post a comment.
Posted by Microsoft on 3/12/2013 at 1:15 PM
Hello Hauke,

The fix for this bug will be available with the next full release of Visual Studio. Unfortunately, it will not be available in a VS2012 CTP.

Thanks,
Atul Katti (Visual C++ Team)
Posted by Hauke H on 3/4/2013 at 8:43 AM
Hi James, thank you for the feedback. Could you be so kind to offer details on the version in which this issue is fixed/will be fixed? The support team states that the issue will be fixed in the "next full release of Visual Studio" in the other issue you have linked to. Does that mean Visual Studio 201x or can we hope for an earlier fix in a VS2012 CTP?
Posted by Microsoft on 3/4/2013 at 8:31 AM
Hi Hauke,

This sounds like same issue which has been reported to us here: https://connect.microsoft.com/VisualStudio/feedback/details/769495/custombuild-tool-not-building-properly-on-incremental-build. This is a bug in Visual Studio and has been fixed.

Thanks,
James Johansen
Visual C++ Team
Posted by Microsoft on 3/1/2013 at 4:05 AM
Hi Hauke H, thanks a lot for your response. I am so sorry that i understood this issue mistakenly. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Hauke H on 2/26/2013 at 11:35 PM
I attached an updated solution with improved names and less noisy output. The issue is not about the cout in the main.

There are now two projects, 'main' and 'utility project'. When you initially build the whole solution (F7 or Ctrl-Shift-B), the 'utility project' prints "Why am I not run every single time?" to the build output. If you build once again, nothing will be actually build but the 'utility project' prints the message again to the build output because it is considered out-dated and is therefore run by the IDE. This is the expected behavior.

Once you run the 'main' project via F5 or Ctrl-F5 this behavior changes. From now on, the 'utility project' is considered up-to-date by the IDE and never build again.

This is problematic for us since we need custom build events (however they are executed) which run every single time we start our project and in the past this could be realized via 'Utility' configurations.
Posted by Microsoft on 2/26/2013 at 11:13 PM
Hi Hauke, Thank you for submitting feedback on Visual Studio and .NET Framework. I can't repro your issue, VS 2012 prints "bar" every time, i use VS 2012 Update 2. Please help , thanks.
Posted by Microsoft on 2/26/2013 at 1:49 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)
Sign in to post a workaround.
© 2013 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement