-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Rebuild does not handle visual basic my templates #51873
Labels
Area-Infrastructure
Bug
New Language Feature - Rebuild
Compiler ability to verify provenance of code via rebuild operations
Milestone
Comments
jaredpar
added
Bug
New Language Feature - Rebuild
Compiler ability to verify provenance of code via rebuild operations
labels
Mar 15, 2021
dotnet-issue-labeler
bot
added
Area-Infrastructure
untriaged
Issues and PRs which have not yet been triaged by a lead
labels
Mar 15, 2021
jaredpar
removed
the
untriaged
Issues and PRs which have not yet been triaged by a lead
label
Mar 15, 2021
jaredpar
added a commit
to jaredpar/roslyn
that referenced
this issue
Mar 16, 2021
This changes the rebuild unit tests to fully round trip the `Compilation` they are building and verify the output byte for byte matches the input. Issue dotnet#51873 discovered working on the change
jaredpar
added a commit
to jaredpar/roslyn
that referenced
this issue
Mar 16, 2021
The parse options weren't correctly being hooked up to the `CompilationOptions` and that was breaking round tripping closes dotnet#51873
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Area-Infrastructure
Bug
New Language Feature - Rebuild
Compiler ability to verify provenance of code via rebuild operations
The rebuild provenance for Visual Basic does not handle templates correctly. The rebuild is working within our code base because we have the VB runtime embedded in all cases which suppresses the my templates. Once that is turned off though our rebuild mis-handles them in the rebuild compilation.
The text was updated successfully, but these errors were encountered: