-
Notifications
You must be signed in to change notification settings - Fork 64
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
NPM version of switch-to-packages and -projects broken after latest VS update #93
Comments
Full stack trace: |
I have the same problem. Apparently, it changes the reference of the solution, but does not add the project to the solution |
Can you clone the repo and try to find a fix locally and create a PR? |
The problem is that there are missing assemblies in: "C:\Program Files\dotnet\sdk\5.0.300-preview.21180.15\en\Microsoft.Build.resources.dll" Microsoft.NET.Sdk.WorkloadManifestReader |
For me same problem - after VS2022 is installed everything blow up. |
Same thing for me. |
I am using the NPM version due to having full .NET framework projects in my solution.
After updating to the latest version of Visual Studio (16.9.2) all projects are failing to switch with the following error:
The project '{pathTo/myProj.csproj}' could not be loaded: System.InvalidOperationException: Not a project: {pathTo/myProj.csproj} ---> Microsoft.Build.Exceptions.InvalidProjectFileException: Invalid static method invocation syntax: "[MSBuild]::AreFeaturesEnabled('16.8')". Method '[MSBuild]::AreFeaturesEnabled' not found. Static method invocation should be of the form:$([FullTypeName]::Method()), e.g. $ ([System.IO.Path]::Combine(
a
,b
)). Check that all parameters are defined, are of the correct type, and are specified in the right order. C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets{stack trace}
This is fixed if I delete the offending "AreFeaturesEnabled" PropertyGroup in Microsoft.Common.CurrentVersion.targets,
any ideas why this problem is occurring?
The text was updated successfully, but these errors were encountered: