-
Notifications
You must be signed in to change notification settings - Fork 71
Don't require nuspec name to match directory name #78
Conversation
It looks like my scenario would ideally be handled via #74 in the future, but I still think this approach is worth allowing, as well. |
What is the problem in using |
I didn't know that was an option, it looks like it fixes my issues. Thanks! |
Sorry, I spoke too soon. I still get the error "No nuspec file found in the package directory" if I specify |
Can you post a link to your code? |
You must rename your nuspec file to match the folder name. Then it will work, with this
Output:
|
Per majkinetor/au#78 (comment), the nuspec name needs to match the package name, and the package name needs to be specified in the update script
Thanks for the assistance, I've got it working now. |
Maybe something for the wiki, I suppose? |
Probably belongs in docs. Would get outdated a bit with #74 but I am not sure if time will allow. If anybody wants to update the README.md now with this scenario I wouldn't mind PR. |
My scenario is that I have multiple folders for the same package (beta or legacy versions), so I can't use the same folder name as the package for all of them.
Hope it helps. Thanks!