-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Microsoft.Build.Exceptions.InvalidProjectFileException: The imported project "C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\Sdks\Microsoft.NET.Sdk.Web\Sdk\Sdk.props #20168
Comments
@srivatsn / @livarcocc - does this belong on project system or sdk? |
This seems like an issue that should go to the SDK. However, @abhijitparkhi1983, did you install the core workload when installing the 2017 BUILD SKU? |
Note that the .NET Core workload of BuildTools is only in the 15.3 Preview (not sure if it was in Preview1) |
When you say core workload, you mean .NET Core. Right ? Was also wondering about the relation between SDK and .NET core. Can you please elaborate. |
@srivatsn , |
@Pilchie , Is there any document/list which you can share with me which details all the pre-requisites required for opening any solution (under any .net application build on .NET Version 3.5 and above at least) using Roslyn on a Server machine where we dont have any version of Visual Studios installed. |
@abhijitparkhi1983 No - it depends on exactly what types of projects you want to open. Since MSBuild is an extensible system, any 3rd party can create project types with it's own SDKs etc. There is no way for us to know what all the dependencies of all projects will be. |
While installing Visual Studios 2015 Build Tool, i dont get an option for Core Workload. I just have following two options under WorkLoads:
I had checked both of them while installing the Build tool. |
Version Used:
1.3.1 / 2.2.0
Steps to Reproduce:
Microsoft.Build.Exceptions.InvalidProjectFileException: The imported project "C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\Sdks\Microsoft.NET.Sdk.Web\Sdk\Sdk.props" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.
Environment Details:
Expected Behavior:
The Solution should open successfully. But certainly this case should be handled for deployments on server machine where Visual Studios cannot be installed.
Actual Behavior:
Microsoft.Build.Exceptions.InvalidProjectFileException: The imported project "C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\Sdks\Microsoft.NET.Sdk.Web\Sdk\Sdk.props" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.
The text was updated successfully, but these errors were encountered: