Mirrors/velopack
1
0
Fork 0
mirror of https://github.com/velopack/velopack.git synced 2025-10-25 15:19:22 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge remote-tracking branch 'upstream/develop' into develop

Browse Source
This commit is contained in:
Caelan
2022-06-15 23:08:18 -06:00
parent b2c954f9ca e298270bed
commit 7521c6b39c
2 changed files with 37 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
docs/contributing/building-squirrel.md
View File

@@ -11,11 +11,10 @@ For the Impatient:
git clone https://github.com/squirrel/squirrel.windows git clone https://github.com/squirrel/squirrel.windows
cd squirrel.windows cd squirrel.windows
git submodule update --init --recursive ## THIS IS THE PART YOU PROBABLY FORGOT git submodule update --init --recursive ## THIS IS THE PART YOU PROBABLY FORGOT
.\.NuGet\NuGet.exe restore devbuild.cmd
msbuild /p:Configuration=Release
``` ```
**Tip:** You can compile the Squirrel.Windows solution with Visual Studio version 2013 and above (including community edition). **Tip:** You can compile the Squirrel.Windows solution with Visual Studio version 2019 and above (including community edition).
**Tip:** For Visual Studio versions that use the Visual Studio Installer (2017/2019 and above), you will need to have at least both Desktop .NET development and Desktop C++ development workloads checked in the Visual Studio Installer. You will also need to make sure that the individual package for the VC++ version used by Squirrel is checked. **Tip:** For Visual Studio versions that use the Visual Studio Installer (2017/2019 and above), you will need to have at least both Desktop .NET development and Desktop C++ development workloads checked in the Visual Studio Installer. You will also need to make sure that the individual package for the VC++ version used by Squirrel is checked.

14
docs/using/machine-wide-installs.md
View File

@@ -8,11 +8,23 @@ Squirrel's Releasify command generates an MSI file suitable for installation via
So, most normal users should continue to run the Setup.exe's generated by Releasify, but if you want to have an IT Admin Friendly version, you can hand off the MSI So, most normal users should continue to run the Setup.exe's generated by Releasify, but if you want to have an IT Admin Friendly version, you can hand off the MSI
## Common pitfalls
### Missing data in `.nuspec`
Most users of Squirrel won't have to do anything new to enable this behavior, though certain NuGet package IDs / names might cause problems with MSI. Most users of Squirrel won't have to do anything new to enable this behavior, though certain NuGet package IDs / names might cause problems with MSI.
**Source:** See [issue #466](https://github.com/Squirrel/Squirrel.Windows/issues/466) for more details. **Source:** See [issue #466](https://github.com/Squirrel/Squirrel.Windows/issues/466) for more details.
### Disabling MSI Generation ### Nothing happens on login
In cases where the end user has previously installed your application, the installer that runs on login will not re-install your application on every login. This can easily be the case if you as a developer is testing out both the EXE and the MSI.
Squirrel leaves behind an almost-empty `%LocalAppData%\MyApp` folder after an uninstall. Deleting this folder (the entire folder, not just the contents) will allow the installer that runs on login to install successfully.
**Source:**: See [issue #555](https://github.com/Squirrel/Squirrel.Windows/issues/555#issuecomment-253265130) for details.
## Disabling MSI Generation
Generating MSIs can be disabled via the --no-msi flag as shown below: Generating MSIs can be disabled via the --no-msi flag as shown below:
~~~powershell ~~~powershell