Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changes in referenced projects are not seen until restart #2872

Closed
vasily-kirichenko opened this issue Apr 18, 2017 · 8 comments
Closed

Changes in referenced projects are not seen until restart #2872

vasily-kirichenko opened this issue Apr 18, 2017 · 8 comments
Labels
Bug Impact-High (Internal MS Team use only) Describes an issue with extreme impact on existing code. Regression
Milestone

Comments

@vasily-kirichenko
Copy link
Contributor

1

I think it's a huge bug.

@majocha
Copy link
Contributor

majocha commented Apr 18, 2017

I've noticed it will refresh when you click and focus the editor.
Still, it's not what one would expect.

It's bad already that you need to save the changes in one project to get them propagated to other project.

@vasily-kirichenko
Copy link
Contributor Author

vasily-kirichenko commented Apr 18, 2017

@majocha things are much worse. Restarting VS does not help (!). Rebuild does not help. Only deleting obj and bin folders does. And it is not reproduced on Debug configuration, only on Release (I mean the configuration that the test solution uses, not VFT is build on).

@majocha
Copy link
Contributor

majocha commented Apr 18, 2017

New project system desperately needed.

@vasily-kirichenko
Copy link
Contributor Author

:) I strongly believe someone is working on it right now. Right now.

@dsyme
Copy link
Contributor

dsyme commented Apr 18, 2017

@vasily-kirichenko I would have thought the DLL timestamps of the newly compiled DLL were being checked, causing a recheck in the dependent file. I don't think it's a project system bug. This is the incremental builder or something else in the process of rechecking files.

Any chance you could you make a minimal repro with exact steps?

@cartermp cartermp added this to the VS 2017 Updates milestone Apr 21, 2017
@dsyme dsyme added Regression Impact-High (Internal MS Team use only) Describes an issue with extreme impact on existing code. labels May 10, 2017
@dsyme
Copy link
Contributor

dsyme commented May 11, 2017

I believe this is fixed by #3025, at least for the cases I've been looking at. I've manually tested on an EXE project referencing a DLL library project, and changes in the library project such as

  • remove file from library project (correctly makes red squiggly appear automatically in open file of EXE project)
  • add file to library project (correctly makes red squiggly disappear automatically in open file of EXE project)
  • remove reference from library project
  • add reference to library project

There may be additional cases such as renames and others not covered by that, where we need to listen to RDT

@vasily-kirichenko
Copy link
Contributor Author

I've tested it on a small solution, it's fixed in #3025.

@dsyme
Copy link
Contributor

dsyme commented May 16, 2017

Fixed by #3025

@dsyme dsyme closed this as completed May 16, 2017
@cartermp cartermp modified the milestones: VS 2017 Updates, 15.3 Jun 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Impact-High (Internal MS Team use only) Describes an issue with extreme impact on existing code. Regression
Projects
None yet
Development

No branches or pull requests

4 participants