-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Applications missing DLL Files after automatic update #102804
Comments
It looks like your "base" framework (Microsoft.NET.App) and ASP.NET framework (Microsoft.AspNetCore.App) are messed up by the update. Can you run After update of this month, I have both 6.0.30 and 6.0.31 on my machine. |
@huoyaoyuan
But as far as i remember this is intended by the Auto update behaviour for dotnet. It was announced not that much time ago. So its not messed up actually its only trying to still run the old version thats not available anymore as the auto update is removing the previous version. |
@jkotas Thanks a lot. Thats seems to be exactly the issue(s) im referring to. |
Good Morning,
Description
some month ago we enabled the automatic updates on virtual machines in our environment to receive continous security patches for the several .NET versions (.NET 6, .NET 7, .NET 8) used by our applications. For that we used the suggested method announced some while ago in the Blog.
For scheduling the updates we are using Windows Update configured on the virtual machine as well as the Azure Update Manager.
Now yesterday (28.05.2024) when the new update for the .NET has been released again a lot of API's are running into errors pointing out that certain dll files are missing. The API's in general were still running and also reachable (e.g swagger / health endpoints). But in case there were calls that involved more logic we faced a lot of errors. Some examples i found related to missing dlls were:
I know that these dependencies are part of the update but im wondering why they are not reloaded the same way as its handled with .NET. This seems to me like a bug as there seems to be a missing reload of the runtime files or the applications only partially reload their dependencies. Expecially it seems to be an issue with dependencies located in the AspNetCore Namespace. This is part of the update but isn't reloaded by the applications what sounds to me like something is missing in that place.
Is there any way to prevent this behaviour ?
Are there any other ways to receive updates without having such an impact on productive applications ?
Thanks in advance.
The text was updated successfully, but these errors were encountered: