Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add infos regarding applicationExecutablePath #116

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add infos regarding applicationExecutablePath #116

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -128,6 +128,11 @@ ReleaseCandidate: `rc`

In version 4 any type of pre-release descriptor, as well as build metadata, will be available. It will fulfill the complete semantic versioning specification and have an abstract version system.

### Specifying an `applicationExecutablePath`

Under some circumstances the UpdateManager is not able to obtain the correct executable path. While the update might work during a debug build, an update with an actual release build will lead to errors while unpacking and copying the files into your application path.
To help nUpdate to find the correct program path the UpdateManager accepts `applicationExectuablePath` as a parameter. With recent .NET versions an executable path is provided by `AppContext.BaseDirectory`. Please note that the UpdateManager needs also the name of your application, so as an example the parameter could be `applicationExecutablePath: AppContext.BaseDirectory + "MyApp.exe"`.

## Supported by

<img src="https://www.nupdate.net/jetbrains.png" width="96" height="96"/>