C
C#2y ago
Sawaid

Does Changing CLR version from V4 to No Managed Code in IIS has any effect on request?

We have a situation in our development that we hosted out identity server on IIS having its CLR version to V4. We use Office365 for OAuth (I don't know what that means) It worked perfectly with our web application and even was working perfectly on postman. However, when we sent the call through Apple iOS, it resulted in invalid_code. However after changing its CLR version to No Managed Code. It started working fine. What could be the reason for it. A senior colleague of mine said that CLR was messing up with the request but I don't buy into it. Can someone give a satisfactory answer?
3 Replies
SuperBrain
SuperBrain2y ago
V4 is for old ASP.NEt apps. If you're using .NET 6, then you have to set it to "No Managed Code". Otherwise your app won't work.
Sawaid
Sawaid2y ago
It was running. I don't think it was built with .NET 6. The identity server is pretty old. Most probably 3.1 or even before that. But the question is does it mess up with the request?
Cisien
Cisien2y ago
It changes how the app pool sets up the pipeline No managed code means it wont look for .net framework code and only load native handlers. In .net core and newer.net, this is the asp.net core handler, which hands the request off to your code