You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This will generate a NuGet package from .nuspec file setting version from AssemblyInfo.cs and place it in OutDir (by default bin\Release). Then it will generate release files from it.
@@ -20,7 +26,23 @@ This will generate a NuGet package from .nuspec file setting version from Assemb
20
26
Here is an example `MyApp.nuspec` file for the above build target example.
21
27
22
28
```xml
23
-
<?xml version="1.0" encoding="utf-8"?><packagexmlns="http://schemas.microsoft.com/packaging/2010/07/nuspec.xsd"> <metadata> <id>MyApp</id> <!-- version will be replaced by MSBuild --> <version>0.0.0.0</version> <title>title</title> <authors>authors</authors> <description>description</description> <requireLicenseAcceptance>false</requireLicenseAcceptance> <copyright>Copyright 2016</copyright> <dependencies /> </metadata> <files> <filesrc="*.*"target="lib\net45\"exclude="*.pdb;*.nupkg;*.vshost.*"/> </files></package>
@@ -29,9 +51,10 @@ Please be aware of the following when using this solution:
29
51
30
52
* Solution needs to have nuget.exe available which can be accomplished by installing `NuGet.CommandLine` package in your solution.
31
53
32
-
~~~pm
54
+
```pm
33
55
PM> Install-Package NuGet.CommandLine
34
-
~~~
56
+
```
57
+
35
58
* It suffers from a bug when sometimes NuGet packages are not loaded properly and throws nuget/squirrel is not recogized (9009) errors.
36
59
**Tip:** In this case you may simply need to restart Visual Studio so the Package Manager Console will have loaded all the package tools
37
60
* If you get the following error you may need add the full path to squirrel.exe in the build target `Exec Command` call. `'squirrel' is not recognized as an internal or external command`
0 commit comments