Support VS 2019 Solution Filter feature. Also supports project not in solution, or unloaded projects. Need to restore complete solution (via CLI or VS) first.

[davkean]

From @abpiskunov on August 29, 2017 16:32

I have follwoing solution structure:

ClassLibrary1 (classic net46)
somefolder
ClassLibrary7
\ClassLibrary7 (core net46)

ClassLibrary7 has project reference for ClassLibrary1 in the form that specify Guid:

<ProjectReference Include="..\..\..\ClassLibrary1\ClassLibrary1.csproj"> <Project>{2684d895-d7ce-4b24-a29e-caed2291e2ea}</Project> <Name>ClassLibrary1</Name> </ProjectReference>

Build fails both from VS and from command line saying that

"C:\Users\antonpis\source\repos\ClassLibrary7\ClassLibrary7\ClassLibrary7.csproj" (default target) (1) ->
(ReportAssetsLogMessages target) ->
c:\users\antonpis\source\repos\ClassLibrary7\ClassLibrary7\ClassLibrary7.csproj : error NU1105: Unable to find project information for 'c:\users\antonpis \source\ClassLibrary1\ClassLibrary1.csproj'. The project file may be invalid or missing targets required for restore. [C:\Users\antonpis\source\repos\Class Library7\ClassLibrary7\ClassLibrary7.csproj]

Classic csproj would work in this case (VS however showed a warning but built fine) both in VS and command line (command line did not have warnings)

Copied from original issue: dotnet/project-system#2759

[davkean]

From @abpiskunov on August 29, 2017 16:40

Note: removing Guid and Name metadata from ProjectReference would fix that, but imagine users converting tehir projects and see errors when where there should be no error at all... they know that csproj file does exist in that location.

[davkean]

Can you expand on above? Do you mean that ClassLibrary1.csproj is referenced but not included in the solution?

[davkean]

From @abpiskunov on August 30, 2017 0:28

yes, correct

[davkean]

This is NuGet not generating an assets file for this project. I have no idea what we should be doing about this situation.

[emgarten]

The reason NuGet does not generate an assets file is because when reading the project references from DTE there is a failure when trying to get the project details for the dependency project. If the project system fixed this then NuGet would restore the project.

Overall the error message looks correct here. I don't think that NuGet is the right home for this (if it should be fixed).

[abpiskunov]

what errors you get from DTE?

[emgarten]

Reference.SourceProject is null or throws an exception when accessing it. Which makes sense since the project system doesn't have the project which is outside of the solution, but this means that NuGet can't restore it since we are working within VS and not shelling out to restore any path found.

[abpiskunov]

hm , but you do have full path to csproj file don't you? it is specified in the ProjectReference. Could you do something with that without DTE?

[emgarten]

Not that I know of. NuGet currently doesn't have a way to work with msbuild directly from VS, the project system handles this and for classic projects NuGet works by using an interface to read PackageReferences, and IVSHierarchy/DTE to read properties needed for restore.

[emgarten]

The project system handles reading project files, which is the missing piece here, I think this issue is best tracked here: dotnet/project-system#2759

[jainaashish]

We met with project system and platform team about this issue, and the current thought is that NuGet can persist unhashed dependency graph of project so that later when the project is unloaded or out of solution, it can still use persisted dependency graph to continue with Restore. So reopening this issue for further tracking.

[jainaashish]

Took a stab at it and the initial POC is NuGet/NuGet.Client#2521

[thargy]

I am still getting this problem. In VS2022. If Sln S has project A that includes project B from outside of Sln S (in Sln T). Rebuilding B separately is not enough. I have to also run dotnet restore (via the CLI) on Sln S before project A will build.

So, in my scenario, where Sln S repo includes a submodule of Sln T and then adds a <ProjectReference> in A to B I cannot get it to build automatically on checkout.

However, adding the following:

  <Target Name="PreBuild" BeforeTargets="PreBuildEvent" Condition="Exists('$(SilkSource)')">
    <!-- Attempt workaround for https://github.com/NuGet/Home/issues/5820 -->
    <Exec Command="dotnet restore" />
  </Target>

At least allows dotnet build to run on clean checkout (though VS 2022 stil fails with the error until you run the CLI build/restore).