New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 781832 link

Starred by 1 user
Status: Archived
Owner: ----
Closed: Nov 9
Cc:
brucedaw...@chromium.org
wfh@chromium.org
dpranke@chromium.org
thakis@chromium.org
█ brettw@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Starting a debug session in Visual Studio always tries to build now

Project Member Reported by jam@chromium.org, Nov 6 2017 
Something seems to have changed for me last week with the automatically generated VS solution/project. I'm using the most up to date Visual Studio 2017.

When I hit F5 now, it doesn't launch the process to debug. Instead VS tries to build.

I've always had my "Build and Run" options's "On Run, when projects are out of date:" to be "Never build".

Either something changed in how GN generates the solution/project, or it was an update of VS. Note that I had to re-generate my project files last week after the clang switch, the previous ones were months old.

Comment 1 by brucedaw...@chromium.org, Nov 6 2017 

The version of gn.exe that I am running was built October 16th. Looking at the history in src\tools\gn I can see a few changes that might be the difference - "Generate projects for Visual Studio 2017 by default" perhaps? - but nothing definitive.

Maybe try building a few custom versions of gn from various sync-points and see if any of them work better?

It's possible it could be the VS change as well. I don't normally launch the debugger from the generated projects so I haven't noticed this.

Comment 2 by brucedaw...@chromium.org, Nov 6 2017 

Have you tried using Build-> Configuration Manager to mark the project as being not buildable? I've done this in the past to avoid this problem, although it can be unwieldy with huge solution files.

It has the advantage of not relying on a global VS setting.

Comment 3 by jam@chromium.org, Nov 6 2017 

I haven't tried different GN versions (a bit time constrained this week). I was mostly hoping that someone would know what if any caused this change.

Regarding configuration manager, yeah I had tried that.

Comment 4 by jam@chromium.org, Nov 8 2017 

Update: I tried using Visual Studio Preview, instead of normal VS, and this isn't broken anymore! So I believe this is a bug in the latest VS release (non-preview).

Comment 5 by jam@chromium.org, Nov 8 2017 

Specifically, I'm on:
VS: 15.0.2629.2
VS Preview: 15.5.27009.1

Comment 6 by jam@chromium.org, Nov 8 2017 

I'm not sure why it showed such an old build for the non-preview, I regularly update. Anyways I tried updating again and it went to 15.4.2, and yet the problem persisted.
Project Member

Comment 7 by sheriffbot@chromium.org, Nov 9

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
►

Sign in to add a comment