Unable to update solution - MSBUILD : error MSB1008: Only one project can be specified. #326
Comments
Looks a lot like #243 , but, well, that one is now covered by a tests and works. If you can't share the project code (just Most of all, welcome! |
Oh. Found the issue. Passing in NuGet sources doesn't quote the arguments - this doesn't trigger when adding them from command line, but when they're read from NuGet configuration, it does. |
I think it's here? It's not the quoting (could be...but) it seems that the project file goes at the END after the -s options. |
I'm getting this generated as command line: |
Is it not supposed to be |
No, that version fails (at least in some versions of |
Yep, you're right. My bad. I was confused. You are correct. |
So, now, having fixed that locally for myself, I now see multiple updates, but one run only updates one reference? Is that to be expected?
It stops there. Just updates the one. I have to run it n times? |
Uhm, right - @AnthonySteele ? :-) The |
Cool, thanks! I expected it would iterate. Even if it needed to dotnet restore or whatever. I'll keep this up to date as things continue! Thanks for your time! |
Hi. yes, the first way that NuKeeper worked was to tell it to "raise n Pull Requests, each containing 1 update" and NuKeeper would do the rest; including, if there are lots of possible updates, choosing the most important updates based on some heuristics. We do not yet support any Batching of updates in PRs since working out what to batch together is not trivial. Local modes are newer, and might be expanded in future. Right now it exits after applying 1 update. |
Gotcha. I like the LOCAL idea of creating n commits, each containing 1 update. I'm still getting emotionally used to the bot idea ;) |
It's a bit scary at first, indeed. Especially when something like https://www.nuget.org/packages/Microsoft.NET.Test.Sdk/ has a new stable release and ALL the projects in your organisation get a PR. |
The initial idea was taken from greenkeeper - the generated PR ties into whatever existing branch build and test automation you have. So if the PR passes the test suite, you should have some confidence for a person to press the "merge" button. Or if it's not a good PR, just close it, it hasn't actually broken anything :) |
Oddly unable to update my two project razor solution (Test->Website). I'm getting an odd MSBUILD error which usually means there's a path/trailing slash issue?
The text was updated successfully, but these errors were encountered: