Force Tool Restore and Formatting. Build for Debug and Release Configuration #277
Conversation
This file contains 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
TheAngryByrd
force-pushed
the
more-refinements
branch
from
4d55538
to
acafb82
Compare
TheAngryByrd
force-pushed
the
more-refinements
branch
5 times, most recently
from
1ecdfa9
to
572b213
Compare
TheAngryByrd
force-pushed
the
more-refinements
branch
from
572b213
to
e2948bf
Compare
TheAngryByrd
changed the title
TheAngryByrd
added a commit
that referenced
this pull request
Sep 17, 2023
## [0.35.0] - 2023-09-17 ### Changed - [Force Tool Restore and Formatting. Build for Debug and Release Configuration](#277) from @TheAngryByrd
TheAngryByrd
commented
Sep 17, 2023
Comment on lines
+15
to
+19
| <Target Name="ToolRestore" BeforeTargets="Restore;CollectPackageReferences;PaketRestore" Inputs="$(_DotnetToolManifestFile)" Outputs="$(_DotnetToolRestoreOutputFile)"> | ||
| <Exec Command="dotnet tool restore" WorkingDirectory="$(MSBuildThisFileDirectory)" StandardOutputImportance="High" StandardErrorImportance="High" /> | ||
| <MakeDir Directories="$(_BuildProjBaseIntermediateOutputPath)"/> | ||
| <Touch Files="$(_DotnetToolRestoreOutputFile)" AlwaysCreate="True" ForceTouch="True" /> | ||
| </Target> |
There was a problem hiding this comment.
@Tarmil, I used the Directory.Build.targets file from FSharp.SystemTextJson but I still had to make some changes to make it work from a complete clean clone.
Specifically the MakeDir to ensure the path exists and the BeforeTargets=PaketRestore.
Tagging you in case you want to use this.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Proposed Changes
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce to MiniScaffold?
Put an
xin the boxes that applyChecklist
Put an
xin the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...