EF Core DbContext Connection - Could Not Load File or Assembly

@JeffMercado

I don't believe so. All of our project-level nuget.config files, to include the project I'm connecting LINQPad to, have the following configuration:

nuget.config:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <config>
    <add key="globalPackagesFolder" value="./packages" />
  </config>
  <packageSources>
    <clear />
    <add key="NAVRES Nexus (v3)" 
         value="https://nexus.navres.dev/repository/nuget-all-v3/index.json" 
         protocolVersion="3" />
  </packageSources>
</configuration>

We proxy the NuGet repo via our on-prem Sonatype Nexus Repository Manager instance. This was one of the first things I had to configure with the portable version. From Tools -> Settings -> NuGet Settings -> Configure NuGet Sources, I have our Nexus instance registered. Oddly, you can't delete the default NuGet 3 source, so I simply have it marked inactive.

Per the link you provided (https://www.linqpad.net/PortableDeployment.aspx - thank you), the changes made via the GUI of the portable LINQPad instance are being writting to a NuGetSources.xml located in the directory from which the portable executable was run.

This is juxtaposed with two other LINQPad directories (%USERPROFILE%/AppData/Local/LINQPad and %USERPROFILE%/AppData/Roaming/LINQPad), of which Local does NOT contain either NuGetConfig.xml nor NuGetSources.xml, while Remote contains both. However, the two files in Remote look to be default implementations:

NuGetConfig.xml:

<?xml version="1.0" encoding="utf-8"?>
<NuGetOptions xmlns="http://schemas.datacontract.org/2004/07/LINQPad">
  <LicensesToAutoAccept></LicensesToAutoAccept>
  <PackagesToAutoDownload></PackagesToAutoDownload>
</NuGetOptions>

NuGetSources.xml:

<?xml version="1.0" encoding="utf-8"?>
<NuGetSources>
  <Source Name="(default)" />
</NuGetSources>

I do not have a NuGetConfig.xml within the directory that contains the portable executable - so I don't think anything is being overruled. Could you give me an example of what you're thinking?

@JoeAlbahari

First off, brother... we'd be L-O-S-T without LINQPad. Our use of the tool over the years has, far and beyond been worth the investment we've put into the licenses. Thank you, thank you, THANK YOU!!!

Reply 1:

I agree that the portable instance should not be the culprit - just wanted to mention that so we're all on the same page. Indeed... the Web project (from my initial post, we have Core and Web) targets Microsoft.NET.Sdk.Web.

If I change this to Microsoft.NET.Sdk, a bunch of ASP.NET-related using statements need to be added - makes sense, got it and no big deal. However, we lose the the ASP.NET's Configuration system and its capability to layer appsettings.{environment}.json configurations (a bit of a deal breaker for us).

HOWEVER...... after adding all the (now needed) ASP.NET-related using statements and getting the code to build, LINQPad does successfully 1) recognize it needs the Microsoft.Extensions.Logging.Abstractions package, and 2) LINQPad brings it down. AND... I am able to get a connection in LINQPad to test successfully against the application's DbContext.

So we're in a bit of a Catch-22 here.

Reply 2:

Requested attempt 1:

Attempted and got:

Message: Could not load file or assembly 'Microsoft.Extensions.DependencyInjection.Abstractions, Version=10.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'. The system cannot find the file specified."

Stack trace:

   at Microsoft.EntityFrameworkCore.DbContext..ctor(DbContextOptions options)
   at Microsoft.EntityFrameworkCore.DbContext..ctor(DbContextOptions options)
   at Reserve.Locker.Common.Database.Auditing.Legacy.CommonDbContext..ctor(DbContextOptions options)
   at Reserve.Locker.Common.Database.Auditing.Legacy.AuditedDbContext..ctor(DbContextOptions options, IAuditUsernameProvider auditUsernameProvider)
   at Reserve.Locker.TNRSubscription.Core.Data.Database.AppDbContext..ctor(DbContextOptions`1 options) in C:\Source\Reserve.Locker.TNRSubscription\src\Reserve.Locker.TNRSubscription.Core\Data\Database\AppDbContext.cs, line 24
   at UserQuery.Main(), line 2

Requested attempt 2:

I can successfully instantiate and dump, but of course... I can't expand any data collections because of the following. Just not sure if you were expecting this or not.

Message: No database provider has been configured for this DbContext. A provider can be configured by overriding the 'DbContext.OnConfiguring' method or by using 'AddDbContext' on the application service provider. If 'AddDbContext' is used, then also ensure that your DbContext type accepts a DbContextOptions object in its constructor and passes it to the base constructor for DbContext.

Stack trace:

   at Microsoft.EntityFrameworkCore.Internal.DbContextServices.Initialize(IServiceProvider scopedProvider, DbContextOptions contextOptions, DbContext context)
   at Microsoft.EntityFrameworkCore.DbContext.get_ContextServices()
   at Microsoft.EntityFrameworkCore.DbContext.get_Model()
   at Microsoft.EntityFrameworkCore.Internal.InternalDbSet`1.get_EntityType()
   at Microsoft.EntityFrameworkCore.Internal.InternalDbSet`1.CheckState()
   at Microsoft.EntityFrameworkCore.Internal.InternalDbSet`1.get_EntityQueryable()
   at Microsoft.EntityFrameworkCore.Internal.InternalDbSet`1.System.Collections.IEnumerable.GetEnumerator()