-
Notifications
You must be signed in to change notification settings - Fork 392
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
MissingMethodException UnconfiguredProject.get_Services() in VS2019 when referencing ProjectSystem.15 #4608
Comments
@MBulli Microsoft.MSBuild from nuget is built against .NET Framework 4.6 so it's unclear how this is happening unless you are building your project against whatever MSBuild happens to be installed on the machine. Is that the case? |
Yes you're right, we weren't using the Nuget version. That fixed the warning. Thanks, silly mistake! |
Okay after fixing the wrong MSBuild references our extension still won't work.
This only happens in VS2019 and if I update the Nuget reference to ProjectSystem.16.0.374-pre it works again. Is this expected behavior or am I'm missing something obvious again? |
This was an intentional breaking change by the VS team. |
Again, thank you for the quick help :) |
Visual Studio Version: VS2019 Preview 3
Summary:
Our extension fails to build in VS2019. We reference
Microsoft.VisualStudio.ProjectSystem
,Microsoft.VisualStudio.ProjectSystem.Managed
andMicrosoft.VisualStudio.ProjectSystem.VS
all with version 15 because we still want to support VS2017. But we can't build the extension because ProjectSystem depends on Microsoft.Build assemblies which are targeting .Net framework 4.7. I don't know whether we do something wrong or it's a problem with VS2019.Steps to Reproduce:
Happens as soon as we try to build our extension in VS2019.
Expected Behavior:
Shouldn't visual studio assembly references be backwards compatible? I expected that VS2019 redirects the references to v16 assemblies which should work silently.
Actual Behavior:
Build fails because our extension targets .Net framework 4.6 but Microsoft.Build assemblies target 4.7.
User Impact:
We would need to build one assembly targeting VS2017 and one for VS2019 but sharing the same code.
The text was updated successfully, but these errors were encountered: