Skip to content

Conversation

@JanProvaznik
Copy link
Member

Summary

  • Captures RAR's DependsOnNETStandard output property
  • Copies netstandard.dll from the Facades folder when the project depends on netstandard

This is a minimal extension to PR #12980 that completes the fix for issue #12933.

Test plan

  • Build ASP.NET WebSite project referencing netstandard2.0 library
  • Verify netstandard.dll is copied to website/Bin folder
  • Verify build succeeds (aspnet_compiler passes)
  • Run SolutionProjectGenerator unit tests (160 passed, 0 failed)

Jeremy Spedding and others added 4 commits January 15, 2026 11:04
I am unsure if this has undesirable performace implications
ASP.NET WebSite projects (legacy, no .csproj) that reference
netstandard2.0 libraries fail at runtime because netstandard.dll
is not copied to the bin folder.

This extends PR dotnet#12980 by:
1. Capturing RAR's DependsOnNETStandard output property
2. Copying netstandard.dll from the Facades folder when needed

The fix only applies to .NET Framework 4.7.1+ where netstandard
facades are available in the Reference Assemblies Facades folder.

Fixes dotnet#12933

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>
@johnazule
Copy link

johnazule commented Jan 19, 2026

We probably want to add SkipUnchangedFiles to this copy, as this current implementation will copy the facades folder for every project reference that depends on netstandard

rarTask.AddOutputItem("CopyLocalFiles", copyLocalFilesItemName, null);

// Capture whether RAR detected a dependency on netstandard
string dependsOnNetStandardPropertyName = GenerateSafePropertyName(project, "_DependsOnNETStandard");

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should probably be declared with the other property names above

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants