-
Notifications
You must be signed in to change notification settings - Fork 4.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installing newer Microsoft.AspNetCore.App without same Microsoft.NETCore.App breaks FX resolution #90096
Comments
Tagging subscribers to this area: @vitek-karas, @agocke, @VSadov Issue DetailsDescriptionIf you explicitly specify a Reproduction Steps
<RuntimeFrameworkVersion>7.0.0</RuntimeFrameworkVersion>
<RollForward>LatestMinor</RollForward>
Expected behaviorThe roll forward behavior will match based on both required frameworks, ie continue to match on Actual behaviorHere is the output with
Regression?Not sure Known WorkaroundsInstall matching Configuration.NET 7 Other informationNo response
|
I don't think the host should try to do any more complicated reconciliation of frameworks which rely another framework version (like going through all possible combinations of what is installed to see if something would work). I think the solution should be on the installer side - we expect a framework to also install the corresponding version of any frameworks that it depends on. Unfortunately, ASP.NET Core installers do not do this right now - this has sometimes resulted in issues/confusion . @richlander filed an issue a while back to track that: dotnet/aspnetcore#49562 |
Can we back up? What is the scenario you are wanting to enable? Is the issue that you wanted both frameworks updated when you installed ASP.NET Core 7.0.9? If so, then that other issue referenced is indeed the problem and we should focus on that. |
Thanks for the comments. The issue was that installing just ASP.NET Core 7.0.9 broke something that was working. And I went down a rabbit hole thinking I was targeting 7.0.9 somehow. (I learnt a lot about specifying SDKs though 😄). The Making the ASP.NET Core installer install both frameworks would fix the issue 👍 I'm still unsure why the FX resolver does the second loop that convinces it to look for 7.0.9, (when it was happy with 7.0.8?), but my C++ is pretty poor. 😆 |
Perfect. That helps a bunch ...
Agree. |
I'm closing this issue in favor of the other one. |
You specified |
Description
If you explicitly specify a
RuntimeFrameworkVersion
with aRollForward
strategy for aMicrosoft.NET.Sdk.Web
app, then it breaks if you install a newer version ofMicrosoft.AspNetCore.App
(eg.7.0.9
) but don't also install the correspondingMicrosoft.NETCore.App
framework.Reproduction Steps
Microsoft.NETCore.App
version7.0.8
andMicrosoft.AspNetCore.App
version7.0.8
.dotnet new web
)RuntimeFrameworkVersion
andRollForward
properties:Microsoft.AspNetCore.App
version7.0.9
You must install or update .NET to run this application.
Expected behavior
The roll forward behavior will match based on both required frameworks, ie continue to match on
7.0.8
in this case.Actual behavior
Here is the output with
COREHOST_TRACE=1
configured:Regression?
Not sure
Known Workarounds
Install matching
Microsoft.NETCore.App
version. There could be some time between where any launching of new processes won't work until this is done? (Unless there is an atomic way to do both?)Configuration
.NET 7
OS Name: Microsoft Windows 11 Enterprise
OS Version: 10.0.22621 N/A Build 22621
Other information
No response
The text was updated successfully, but these errors were encountered: