This repository was archived by the owner on Jan 12, 2024. It is now read-only.
Fix to build of faulty Q# program succeeds when calling dotnet build twice
#570
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bettinaheim
approved these changes
Aug 15, 2020
Co-authored-by: Andres Paz <anpaz@microsoft.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change fixes an issue in which building a faulty Q# program succeeds when calling
dotnet buildtwice.This happens because a
bsonfile is generated when the program is built the first time, even though compilation failed. Whendotnet buildis invoked for the second time, thebsonfile already exists and it is newer than the originalqsfile, so the incremental build skips invoking the compiler command line tool.The fix is to delete the
bsonfile when Q# compilation fails.