Skip to content

Conversation

@johnazule
Copy link

Fixes #12933

Context

Currently we don't provide a target framework version when generating metaprojects for asp websites, which leads reference table to assume that the framework version is 4.6.0, which apparently does not contain a reference for netstandard2.0.

Changes Made

Add a TargetFrameworkVersion based on the provided target framework moniker

Copy link
Member

@JanProvaznik JanProvaznik left a comment

Choose a reason for hiding this comment

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

could you please provide a minimal demo which this change fixes? I don't think it's necessary to add a unit test but I'd like to see the scenario and have clear evidence it's fixed with the change.

@johnazule
Copy link
Author

TestSolution.zip
This is a small project which show cases the difference. This PR currently doesn't add in the netstandard.dll to the bin folder but otherwise it addresses the dependency issues

Jeremy Spedding added 2 commits January 10, 2026 00:37
I am unsure if this has undesirable performace implications
@johnazule johnazule force-pushed the bugfix/fix-asp-websites-failing-to-resolve-projects-that-depend-on-netstandard branch from f14ad00 to 0f99717 Compare January 9, 2026 13:37
@johnazule johnazule requested a review from JanProvaznik January 9, 2026 13:38
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.

ASP .Net Framework 4.8 webSITE cannot resolve assembly references for projects with dependency on netstandard2.0

2 participants