It took me a couple of parses to spot something suspicious. Here’s an abridged example of the csproj file:
Visual studio extensions and updates value cannot be null upgrade#
During the migration I’d used the NuGet package manager to upgrade the packages after first editing my csproj to use netcoreapp2.0. However they all seemed to suggest that indeed it was due to bad configuration of some form or another. Eventually I decided to double check my csproj file reference. Odd!Īt this stage I resorted to Google and found a few similar sounding issues and StackOverflow posts. So this would suggest that in fact the configuration was working and the connection string was being read in. However, if I ran the application from Visual Studio, I could see the database being created and migrated (we have a Database.Migrate() call in our code). I must have messed something up when performing the configuration changes as part of the upgrade to ASP.NET Core 2.0. In principle this would seem like a fairly obvious problem. The key part of the error is “Value cannot be null. Parameter name: connectionString at .NotEmpty(String value, String parameterName) at (DbContextOptionsBuilder optionsBuilder, String connectionString, Action`1 NpgsqlOptionsAction)
> System.ArgumentNullException: Value cannot be null. : Failure while building 'Lambda: Invoke(value(StructureMap.ContainerExtensions+>c_Displa圜lass9_0).descriptor.ImplementationFactory, IContext.GetInstance())', check the inner exception for detailsġ.) Lambda: Invoke(value(StructureMap.ContainerExtensions+c_Displa圜lass9_0).descriptor.ImplementationFactory, IContext.GetInstance())Ģ.) Instance of DbContextOptions (System.Object)ģ.) Container.GetInstance(DbContextOptions)Ĥ.) Lambda: Invoke(value(StructureMap.ContainerExtensions+c_Displa圜lass9_0).descriptor.ImplementationFactory, IContext.GetInstance())ĥ.) Instance of (System.Object)Ħ.) All registered children for IEnumerable I won’t include it all here but the higher frames are as follows… This started to run and then threw an error and dumped out a stack trace.
I attempted to run in the following command…ĭotnet ef migrations add "dummy migration" The last step there is to run in a dummy migration to the project. My last change was to fix-up the migrations in the project due to changes in the NpgSql project as detailed in their migration documentation. After working my way through the various breaking changes to things such as authorisation I was pretty much at the point where my project was compiling again. I was upgrading a quite mature ASP.NET Core 1.0 project to ASP.NET Core 2.0 today and ran into an odd issue which took me a good half hour to track down.
0 kommentar(er)
