Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
init-wrap: new -Name input #157
We use bzr for revision control, and very often use "feature branches" for doing our work. Since bzr uses separate directories for each branch, we often have a setup like:
When we add a new .csproj to the solution, we of course need to update the project file to use the OpenWrap targets instead of the default ones. As far as I know, the only way to do that is with the "init-wrap" command. Unfortunately, init-wrap uses the directory name for the package name, so doing something like:
"ftr_branch_two> o init-wrap -All true -NoSymlinks true -IgnoreFileName .bzrignore"
Results in a new ftr_branch_two.wrapdesc file getting generated. This then causes headaches for MSBuild, etc, etc.
This branch adds a new -PackageName parameter to init-wrap, so we can instead do:
"ftr_branch_two> o init-wrap -PackageName MyProject -All true -NoSymlinks true -IgnoreFileName .bzrignore"
And it detects the existing MyProject.wrapdesc and behaves as expected.
Thoughts? Suggestions on a better way to handle this?
Let me check if I understand the scenario.
init-wrap Target Name
init-wrap . Name
If that's the case, pacakge name should still default to the existing values or you'd end up breaking some of those scenarios. I'd also prefer if it was called Name, as there's plenty of projects that need to be created that do not end up being a package (although it'd of course be much better if everything was a pacakge :) )
Yes, those are the the scenarios. I can easily rename the parameter to "Name" instead. If you check out the PackageName property, it does replicate the existing "default values" if the parameter isn't explicitly specified. Is that what you meant by "still default to the existing values" ?