Add option.winVersionString for accurate process name (always nwjs previously) #459
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.
Fixes #196
Fixes #315
Add
option.winVersionString
for accurate process nameThe main goal was to fix the issue where the process showed up as
nwjs
in the Windows 10 Task Manager (now defaults to theoptions.appName
). When trying to changeFileDescription
viarcedit
as a post-process to thenw-builder
build, I would always get a blank/default-shimmer NW.js page when starting up the app instead of the specifiedmain
file.Allows you to edit the version string of the resultant Windows executable. These can be easily viewed in Properties -> Details,
Instead of just
version-string
, we could generalize this more to allow more of thercedit
options likefile-version
, perhaps asoptions.winRc
.version-string
covers these properties, https://msdn.microsoft.com/en-us/library/windows/desktop/aa381058.aspx#string-nameAlso see