Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Fallback to package.Id if title not available #1447
Conversation
If a package title is not set in the nuspec tile, normal user installs work fine, but the installation folder set in the Wix for the machine wide installer becomes "%programfiles%\ Installer\ .... " - note the space where the title should be. When the folder is created this space is silently removed by the operating system, however in the registry Run entry, the space is present. As the name in the registry and the actual path don't match, the machine wide installer never runs. This change means that the installer falls back to using the id if the name is not available
|
I would rather that Releasify simply fails if title isn't present, can you do this instead? |
|
Yes I can do that if you're sure, the MS documentation on .nuspec files does this about the title though:
So it does feel like going against the spirit of the nuspec format a little not to fallback to the ID. It's your project through - let me know your thoughts and I'll implement it. |
If a package title is not set in the nuspec tile, normal user installs work fine, but the installation folder set in the Wix for the machine wide installer becomes "%programfiles%\ Installer\ .... " - note the space where the title should be.
When the folder is created this space is silently removed by the operating system, however in the registry Run entry, the space is present. As the name in the registry and the actual path don't match, the machine wide installer never runs.
This change means that the installer falls back to using the id if the name is not available