Add --title to Squirrel.exe pack?
See original GitHub issueThe entry in Programs and Features is determined by the --packName
parameter to Squirrel.exe pack ...
According to the Squirrel naming conventions, that entry is set by the title
property on the NuGet package metadata. Could we get a --title option added to pack
to set this value when we are skipping the NuGet packaging? That way we could have spaces and dots in the Programs and Features entry.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
A simple way to package an app · Issue #630 · Squirrel ...
Solution needs to have nuget.exe available for example by installing NuGet.CommandLine package. And also it suffers from this bug when sometimes ...
Read more >docs / using / naming.md
Squirrel NuGet Package Metadata title property. [assembly: AssemblyDescription("MyApp") (from AssemblyInfo.cs ); Filename of the Exe (e.g., MyApp) ...
Read more >Application Deployment Made Easy
Smoothly Deploying Your App With Squirrel. Many .NET developers are familiar with ClickOnce, Microsoft's simple deployment solution for quickly packaging ...
Read more >Squirrel for Windows
Squirrel for Windows is nifty. It really meets the goals set out for it in the README. It's fast, it makes setup that...
Read more >Deploy WPF Application with squirrel.windows and no ...
Case 1: I created a NugetPackage with the Nuget Package Explorer. Than releasify it over the Package Manager Console "squirrel --releasify ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is now released in 2.7.79.
689b7ec778326cad5831eeb03ea441480ab99b29 I have fixed several issues related to using dots and dashes in package id’s,
My-Package3.Cool
is a perfectly valid ID and is working fine now.995dd6379a9a450948548285707567de7ace58e0 I have also deprecated
--packName
and replaced it with a separate id (required) and title (optional) parameter.--packName
will continue to work the same way it used to, but it will not be listed in the-h
output, and may be removed in a future version.This will be in the next pre-release.