App doesn't perform in VS 2022 windows 11 exactly like VS 2019 WIndows 10

Corey Fleig 40

I wrote an online store using VS 2019 on Windows 10, MVC Core 3.1. Works perfectly.

I got a new pc with Windows 11, installed VS 2022, and ported the app over. I also resolved the issues from Startup.cs to Program.cs. Everything compiles. (MVC Core, .Net 8).

However, when I run the app inside VS 2022, out of about 10 anchored links, two of them don't fire. I set debug to stop in the controller, but it never gets there.

I didn't change any code at all in the views/controllers/Layout. Just Program.cs.

Any thoughts before I tear this app apart?

AgaveJoe 26,136 Reputation points

2024-04-05T19:34:46.9233333+00:00

Your guess is better than ours as we cannot see or run the code.
Corey Fleig 40 Reputation points

2024-04-05T19:43:04.0033333+00:00

I appreciate your participation. I didn't include code on purpose, only because I'm saying the code in every single file is identical, with the only exception being Program.cs.

I'm just wondering if anyone out there has been puzzled by inconsistent behavior and noticed that whenever you port from VS 2019 to VS 2022 and Windows 10 to Windows 11, watch out for { such-and-such}.

It's quite possible that I introduced something when I ported over, so I'm open to that.

I thought I'd ask before I spend hours and hours debugging every single line!
AgaveJoe 26,136 Reputation points

2024-04-05T20:04:37.7666667+00:00

I thought I'd ask before I spend hours and hours debugging every single line!

You said 2 out of 10 links are not working as expected. I'm not sure why you have to debug every single line when only two links are causing an issue.

The first step in troubleshooting is reproducing the problem. At this point you are the only one that can run the code. I would open Network trace view in the browser's dev tools then click the link. Do you see a GET request? If so, what did the server return? Perhaps a 404 or a 500? Once you have basic information then you can make a decision on the next troubleshooting step.

Accepted answer

Bruce (SqlWork.com) 56,531 Reputation points

2024-04-05T20:27:33.27+00:00

while debugging as suggested is probably the easiest, you can read through all the breaking changes since 3.1. one of them probably applies.

https://learn.microsoft.com/en-us/dotnet/core/compatibility/5.0

https://learn.microsoft.com/en-us/dotnet/core/compatibility/6.0

https://learn.microsoft.com/en-us/dotnet/core/compatibility/7.0

https://learn.microsoft.com/en-us/dotnet/core/compatibility/8.0
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

1 additional answer

Corey Fleig 40 Reputation points

2024-04-05T20:26:02.0466667+00:00

It doesn't appear to be a migrating issue. Network Trace View should help pinpoint the problem!
Please sign in to rate this answer.

0 comments No comments
Sign in to comment