When using "publish_nuget: true" my .nuspec is ignored and it is packaging the csproj instead
I have configured the following build and set it to
automatically perform a Nuget pack:
https://ci.appveyor.com/project/dan-turner/appconfigtransforms
On this repo:
https://github.com/dan-turner/AppConfigTransforms/tree/master/src/A...
I followed the instructions in the following thread (which
aren't in the doco btw):
http://help.appveyor.com/discussions/questions/1210-how-does-the-pa...
So I have a solution file, that solution file points at a
.csproj, there is a corresponding .nuspec sitting right next to it.
However as you can see in the build output it's calling:
nuget pack
"C:\<snip>\AppConfigTransforms.csproj"
instead of:
nuget pack
"C:\<snip>\AppConfigTransforms.nuspec"
Is this a bug?
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Feodor Fitsner on 05 Aug, 2015 05:02 PM
It's not a bug - this is how it's currently done.
You can use your own
nuget packcommand instead of "automatic" one.2 Posted by dan.p.turner on 06 Aug, 2015 01:36 AM
Ok, so at a guess your current logic for
publish_nuget: trueis:It would be awesome if you could change it to:
2.1 If there IS a matching .*proj, pack the .*proj
2.2 If there is NOT a matching .*proj, pack the .nuspec
The thing I'm trying to package simply contains some msbuild targets, the only reason I created the .csproj in the first place was to try and get appveyor to automatically package it. The problem is when it's packages using the .csproj the package ends up with a useless .dll produced by the project.
Support Staff 3 Posted by Feodor Fitsner on 06 Aug, 2015 04:51 AM
Yeah, thanks for suggestion.
Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:58 AM.