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

Project.AdditionalDocuments is empty after acepting a refactor that Adds an Additional Document. #19503

Closed
danmendonca opened this issue May 15, 2017 · 1 comment
Labels
Resolution-Duplicate The described behavior is tracked in another issue

Comments

@danmendonca
Copy link

Version Used:
1.3.2
Steps to Reproduce:

  1. In Visual Studio 2017, write a code refactor that generates na AdditionalDocument and add it to the a Project through Project.AddAdditionalDocument(string, SourceText,, Folders)
  2. Though the Visual Studio Instance now has the AdditionalDocument visible in the solution explorer, if you get the instance of the modified Project, property AdditionalDocuments count is 0.

Expected Behavior:
After adding na AdditionalDocument to a Project, when running getting the new instance the Document should be available in the Project AdditionalDocuments property
Actual Behavior:
2017-05-15 1
There are no Additional Documents in the Project AdditionalDocuments collection

@sharwell
Copy link
Member

This bit me as well while working on StyleCop Analyzers. It appears to be a duplicate of #4655.

@sharwell sharwell added the Resolution-Duplicate The described behavior is tracked in another issue label May 15, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution-Duplicate The described behavior is tracked in another issue
Projects
None yet
Development

No branches or pull requests

2 participants