ProjectReferences do not work for a NoTargets project that sets TargetFrameworks and NoTargetsDoNotReferenceOutputAssemblies

[ericstj]

It seems that the NoTargets project is getting confused if it's in an outer or inner build.

Try the attached repro:
noBuildCrossTargeting.zip

When building this you'll see:

C:\Program Files\dotnet\sdk\8.0.100-preview.7.23369.9\Microsoft.Common.CurrentVersion.targets(1842,5): error : Project
'..\lib\lib.csproj' targets 'net8.0'. It cannot be referenced by a project that targets '.NETFramework,Version=v4.0'. [
C:\scratch\noBuildCrossTargeting\notargets\notargets.proj]

This is happening because common targets is setting TargetFrameworkIdentifier and TargetFrameworkVersion. Probably the fix here is to see what happens in outer build of a CSProj and try to match that.

cc @carlossanlop @ViktorHofer

[jeffkl]

For some reason, the .NET SDK doesn't have the built-in outer/inner build logic for anything project that's not a .csproj or '.vbproj.

If you rename your NoTargets project to notargets.csproj, it works just fine. The .proj extension only imports Microsoft.Common.targets.

[baronfel]

@jeffkl mind dropping a link to what you're seeing that logic? I'd hope that fsproj at minimum were also considered there and I want to ensure parity.

[jeffkl]

@baronfel yeah sorry .fsproj is included as well.

https://github.com/dotnet/sdk/blob/6db46d4ceca5fd2312fa6ce98632d905f36f4c35/src/Tasks/Microsoft.NET.Build.Tasks/sdk/Sdk.targets#L24-L33