Update Build Requirements #474
Merged
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
Issue 7388 Update README.md Add .NET 6.0 to list of components
|
What required .NET v3.5? |
|
@robmen DTF |
|
Do you really still need to target .NET Framework 2.0 for wix v4? |
|
@ViktorHofer what do you mean? I'm only documenting what WiX is currently needing. @robmen Do I need to do anything else to nudge this PR along? |
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.
Issue 7388
Testing of the developer build on a clean VM has indicated to me that .NET 3.5 SP1 is needed and git.exe has to be in the command path for the gitinfo tasks to work. This can be one of several distros or the one optionally provided by VS.
I also noted that spectre mitigated libs are available but I haven't touched that part of the recommendation as I don't know the strategy there.
I kind of wanted to put a couple lines in there saying last tested on 12/5/2023 using VS 17.8.3 to help future developers troubleshooting issues but I don't know if the maintainers would want that.