Closed itn3000 closed 5 years ago
Thanks! I'd heard about this issue but hadn't had time to investigate yet. I'll look into fixing it over the weekend (or sooner if I get the time).
Hi. I'll try to get a new release out tomorrow (need to do some proper regression testing) but I can post a .vsix
package for you to try out if you like.
hmm, when both "Current" and "15.0" toolset is existing in ProjectCollection.Toolsets, MSBuild tried to use "15.0" and throw exception. I create PR as tintoy/msbuild-project-tools-server#12 . I hope it will help this issue.
Thanks! I've merged your fix and will try building a new package this afternoon to try out :)
Do we need to remove the 15.0
toolset, or just set Current
as the default? Otherwise, what happens when the user opens an old-style project that has the Toolset
attribute on its <Project>
element?
I might need to add some tests for this before publishing a new version of the extension...
(the user can override the MSBuild SDK directory via environment variable, but I think I'll also add a config setting so it can be workspace-specific; eventually, this may need to be configurable per-project...)
Ok, would you mind trying this new build of the extension package?
msbuild-project-tools-0.2.51.zip
I'll open a separate issue for adding a config setting that enables the user to specify / override additional MSBuild toolsets.
I've tested this locally (both with and without the new 3.x preview SDK installed) and it seems to work correctly, so if the new build works for you then I'll publish it. The custom config stuff will be published in the next release.
I also tried updated extension, and It seemed to work correctly. Thank you for fixing it.
Great! Thanks for reporting it :)
I've published the new version so it should be available for general install.
Environment
msbuild extension version is "0.2.50"
here is the
dotnet --info
result;Steps to reproduce
dotnet new console
Expected Result
project file can be opened with no error
Actual Result
Almost extension seems to work correctly, but the following error is always occured.
this is because dotnet-sdk renamed Microsoft.Common.props's directory from "15.0" to "Current" since dotnet-sdk-3.0. (perhaps since this commit)