|
@@ -33,7 +33,7 @@ The cause of this problem is that the solution filter you are using does not inc
|
|
|
### You can fix this in one of three ways
|
|
### You can fix this in one of three ways
|
|
|
|
|
|
|
|
1. Build the project on command line. In most cases, running `build.cmd` on command line solves this problem.
|
|
1. Build the project on command line. In most cases, running `build.cmd` on command line solves this problem.
|
|
|
-2. If the project is missing from the .sln file entirely, you can use `dotnet sln add` to add it, or else right click on the solution/folder in Visual Studio and choose Add->Existing Project, and adding it.
|
|
|
|
|
|
|
+2. If the project is missing from the .sln file entirely, you can use `dotnet sln add` to add it, or else right click on the solution/folder in Visual Studio and choose Add->Existing Project.
|
|
|
3. If it is present in the .sln, but not the .slnf, you can update the solution filter to include the missing project. You can either do this one by right-clicking on project in Visual Studio and choosing to load it's direct dependencies, and then saving. Alternatively, you can hand edit the .slnf file - it's a fairly simple json format.
|
|
3. If it is present in the .sln, but not the .slnf, you can update the solution filter to include the missing project. You can either do this one by right-clicking on project in Visual Studio and choosing to load it's direct dependencies, and then saving. Alternatively, you can hand edit the .slnf file - it's a fairly simple json format.
|
|
|
|
|
|
|
|
## Error MSB4019: The imported project "…\artifacts\bin\GenerateFiles\Directory.Build.props" was not found
|
|
## Error MSB4019: The imported project "…\artifacts\bin\GenerateFiles\Directory.Build.props" was not found
|