-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Install-Package Squirrel.Client does not generate .nuspec file #246
Comments
I've come back to an existing Squirrel-based project after a few months, and am getting the same error when trying to run When I run the command, Process Monitor shows that devenv is searching all directories in my path for I see that |
It is working for me in visual studio 2013 update 2 RC (ie, the latest version of visual studio) |
I've just tried it with Update 2, but it has unsurprisingly (since Squirrel should already work on VS 2012 onwards) failed to resolve my issue. I feel like something very obvious is amiss. |
The same issue for me as well, and I'm using:
|
Same for me. No nuspec file and no New-Release command. My install is the following
|
I think squirrel transition is still in progress as of #211. we need to use Shimmer package for now. More info at this Bradley Grainger's gist |
I get the same problem. |
I really wanted to ship an update, so I came back to my project and figured out how to get it working.
BTW, when I tried updating the previous version of my app to the latest (generated via this procedure), installing the delta package failed, and Squirrel just gave up (instead of falling back to the full package). I don't know if this was just a local problem, but I'm now deleting the delta packages before publishing, as a precaution. |
@bgrainger, your delta issue is caused by a problem with extracting the Delta. It should go to the full if the Delta fails, but the exception isn't handled within squirrel, thus it can't fall back. The issue has been reported here Stefan |
Any fix for this problem? I want to use Squirrel:( |
Same issue, with both Visual Studio 2013 Professional Update 2 and Visual Studio Express 2013 Update 2, with NuGet 2.8.50313.46. No nuspec file was created, and the Package Manager console only shows dependency installations. |
Just as a heads up, it seems like this Squirrel is road kill and work appears to be focused here on a cut down version: |
As per the QuickStart guide, I have run
Install-Package Squirrel.Client -Project TestApp
in a clean solution with a single WPF project created solely for testing. There were no errors and all references appeared in the solution. However, the .nuspec file is not automatically opened in VS and I can't find it in any folder.
Lastly, running
New-Release
results in the following error:The term 'New-Release' is not recognized as the name of a cmdlet, function, script file, or operable program.
I am using VS 2013, .NET 4.5 and the latest NuGet.
The text was updated successfully, but these errors were encountered: