Skip to content
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

Setting output/Releases folder #219

Open
stefanolson opened this issue Nov 28, 2013 · 2 comments
Open

Setting output/Releases folder #219

stefanolson opened this issue Nov 28, 2013 · 2 comments

Comments

@stefanolson
Copy link

In my solution I have two projects that use Squirrel. Unfortunately, this means that whenever you call New-Release for one project it creates a setup.exe that kills the previous one.

So there are a couple of issues here:

  1. I can't seem to specify a releases directory, as is suggested here: GNU/Linux Support Squirrel.Windows#106
    if I do that I get this output from powershell:
    PM> new-release -ReleasesDirectory c:\temp
    New-Release : A parameter cannot be found that matches parameter name 'ReleasesDirectory'.

How do I specify a different directory?

2 If a change from one project to another and call New-Release, the resulting setup just crashes. Basically it appears that the process that builds the setup doesn't completely overwrite the previous setup, if for example I change the title and then build a new release then the setup hasn't been updated with the new title. You basically have to delete all setup files to get it to build properly.

Stefan

@peters
Copy link
Contributor

peters commented Nov 29, 2013

@stefanolson
Copy link
Author

Thanks @peters. I looked through the file, but I'm not sure how to use it within the package manager console.

I decided the best thing to do this case is to create a second solution, so that it will correctly create the second project's setup un different folder.

I think future releases of Squirrel should place the releases in the project folder rather than the solution folder and this would solve the problem (do I need to submit a new feature request for that?)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants