-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Specify required .NET version #341
Comments
The way we'd probably deal with it is via another Squirrel attribute in your EXE - we can scan all of those, use that to write an entry in the VS_VERSION_INFO block with the required .NET version, then load it in Setup.exe. So the steps would be something like:
|
Lets see if I am understanding this correctly:
Is that correct? I assume there is no "framework bootstrapping" in squirrel for windows because of 1. Or did i miss something? (I, too, am eyeing .net 4.6 for an upcoming release) |
Any progress on this? |
Has there been any progress on this? |
@chizran Nope! I'd take a very thoughtfully written PR to add this though |
I've got a .NET461 branch. I suppose you could build it, and replace the setup.exe in the nuget package folder. Not really convenient though. But maybe it gives some pointers. I currently have no need for the MSBuild support, but rather use it in electron-winstaller because I use it with Electron+Edge to run .NET 4.6 code :) |
Can this be marked as closed? #940 is now included in the released versions of Squirrel. |
Due to some updates in one of our dependencies (Roslyn, specifically) we're looking at having to start targeting .NET 4.6 in the near future (possibly even the RC version).
Just wanted to get an issue posted to start a discussion about if/how squirrel might deal with this.
The text was updated successfully, but these errors were encountered: