502.5 - ANCM Out-Of-Process Startup Failure after I downgrade to 6.0

mc 3,641

please check the error:

Unhandled exception. System.IO.FileLoadException: Could not load file or assembly 'System.Runtime, Version=7.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The located assembly's manifest definition does not match the assembly reference. (0x80131040)
File name: 'System.Runtime, Version=7.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
   at Program.<Main>$(String[] args)
Unhandled exception. System.IO.FileLoadException: Could not load file or assembly 'System.Runtime, Version=7.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The located assembly's manifest definition does not match the assembly reference. (0x80131040)
File name: 'System.Runtime, Version=7.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
   at Program.<Main>$(String[] args)

I changed the target from 7.0 to 6.0 but publish file still use 7.0

Lex Li (Microsoft) 4,662 Reputation points Microsoft Employee

2023-04-01T08:44:11.5+00:00

So, after changing net7.0 in your project file to net6.0 you did run dotnet publish again to publish the artifacts, didn't you? Can you verify the actual published configuration by opening up the .json files? They can tell you whether .NET 6 or 7 is used. Learning that is critical before moving on.
mc 3,641 Reputation points

2023-04-01T10:16:22.1+00:00

yes ,I do have run dotnet publish again and check the json file

and more when I change to 6.0, I can not login (use cookie) it seems the cookie is not valid. by press F5 to debug
mc 3,641 Reputation points

2023-04-01T13:29:17.35+00:00

any update?
AgaveJoe 26,186 Reputation points

2023-04-01T15:45:37.0966667+00:00

The error indicates the application is looking for .NET 7. I'm guessing you made a mistake down grading the application.

The community cannot see you code so we have no way to help you. Publish your project of GitHub if you need community debugging support. Otherwise, you can take a few seconds to review your project references.
mc 3,641 Reputation points

2023-04-01T15:56:11.8566667+00:00

you can create a .net 7 project and downgrade it to 6.0 and check it.
Lex Li (Microsoft) 4,662 Reputation points Microsoft Employee

2023-04-01T16:06:25.2966667+00:00

Cannot even reproduce it. What I tried is 1) create a .NET 7 MVC project dotnet new mvc 2) Make sure it runs dotnet run 3) Downgrade it to .NET 6 manually. 4) Remove implicit usings and fix compilation. 5) dotnet run launches the project on .NET 6. I will move on to test this on IIS and see whether the issue is specific to ASP.NET Core module.
Lex Li (Microsoft) 4,662 Reputation points Microsoft Employee

2023-04-01T16:20:58.15+00:00

Cannot reproduce what you described on IIS with out of process mode. What output do you get from dotnet --info that might give some hints. Besides, you might need to share more details how you published it and configure on IIS to help others investigate further.
mc 3,641 Reputation points

2023-04-03T00:56:51.96+00:00

I know it maybe the cache if I use dotnet publish it is ok but use visual studio it is wrong.
Lex Li (Microsoft) 4,662 Reputation points Microsoft Employee

2023-04-03T05:27:43.3+00:00

Then you might consider reporting this issue to Visual Studio team and let them take a look, https://learn.microsoft.com/en-us/visualstudio/ide/how-to-report-a-problem-with-visual-studio?view=vs-2022