We upgraded Entity framework in a .NET Core project to 7.0 and suddenly inserts into a SQL Table were no longer working – nothing got inserted and there was no error. Let’s check the breaking changes document: https://learn.microsoft.com/en-us/ef/core/what-is-new/ef-core-7.0/breaking-changes SQL Server tables with triggers or certain computed columns now require special EF Core configuration Old behaviorPrevious... » read more
Upgrading an Azure .NET web app from 4.6 to 4.8 and when we published the staging version it worked, but the the identical site but with different database references threw this great error when it deployed. This is after removing some old compiler packages like Microsoft.CodeDom.Providers.DotNetCompilerPlatform that are no longer required, during the upgrade. It... » read more
During a painful switch from .NET Framework 4.6 to 4.8 I encountered this error: This comes from AutoMapper and it seems that at some point (version 8.0) that things changed which we can find in their pleasantly useful documentation. To save you the trouble here’s the links: In my case I had two changes: First... » read more
Updating a .NET website from 4.6 to 4.8 and after updating all the packages in Visual Studio’s package NuGet Package manager, I got the following warning that wouldn’t go away: Following that link https://docs.nuget.org/docs/workflows/reinstalling-packages it suggested updating your packages would fix it, which it didn’t for me. So then I tried re-installing each package in... » read more
We upgraded an Azure .NET web app to use .NET 6.0 instead of 4.6.2, in itself something of a task for this app. But when we then tried to deploy it to Azure, GitHub failed on the build with dotnet stage: So this is clearly a problem with the deployment .yml, since we changed the... » read more
There are a couple of likely causes, search Stack Overflow for “EntityStates.Modified”, this might be required in your case. For me this was different, the cause was a table that didn’t have a primary key. Our code used to work then stopped working when we moved to Azure SQL Server. We were making a change... » read more
If you have a bunch of databases that you want to migrate into a single Azure SQL DB, and the table names are all different then that’s quite easy. If you don’t mind renaming things, then there’s a solution for same-named tables too… Add/migrate one database Head over to the Azure SQL section https://portal.azure.com/#create/Microsoft.AzureSQL Create... » read more
Azure .NET web apps connecting to an AWS SQL database kept throwing up this error sporadically, seemingly without any pattern. The full message was this: An unhandled exception occurred while processing the request. Win32Exception: An existing connection was forcibly closed by the remote host. Unknown location.SqlException: A connection was successfully established with the server, but... » read more
Newtonsoft.Json.JsonSerializationException: ‘Error converting value {null} to type “System.Boolean”. Code like this can generate the error: This happens when the bool field in your source is null, and the model you’re converting into’s matching field does not allow nulls. If you don’t mind this field being null in your destination model item, then you can just... » read more