web.config AspNetCoreModuleV2 SQLite unable to open database file

[SeriaWei]

Unable to open database file

web.config AspNetCoreModuleV2 SQLite throw the exception "unable to open database file".

ConnectionString

"ConnectionString": "Data Source=Database.sqlite"

But when i change to use AspNetCoreModule or change the connection string to Data Source=D:\\ZKEACMS\\Database.sqlite the application run correctly.

web.config

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <location path="." inheritInChildApplications="false">
    <system.webServer>
      <handlers>
        <add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModuleV2" resourceType="Unspecified" />
      </handlers>
      <aspNetCore processPath="dotnet" arguments=".\ZKEACMS.WebHost.dll" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" hostingModel="InProcess" />
    </system.webServer>
  </location>
</configuration>

[SeriaWei]

IIS Version :10.0

[pakrym]

It's probably due to the CurrentDirectory issue: #4206. Here is our recommended workaround for now: https://github.com/aspnet/Docs/blob/master/aspnetcore/host-and-deploy/aspnet-core-module/samples_snapshot/2.x/CurrentDirectoryHelpers.cs. Call CurrentDirectoryHelpers.SetCurrentDirectory() first thing in Program.Main. This will be fixed in a patch.

[SeriaWei]

I found that, System.IO.Directory.GetCurrentDirectory() not return the right directory

[SeriaWei]

@pakrym Thanks.

[pakrym]

I assume the workaround has resolved your issue. Feel free to reopen otherwise.

[ericjohannsen]

How would the work-around help when attempting to create a SQLite database from Package Manager Console?

PM> Update-Database
SQLite Error 14: 'unable to open database file'.

[pakrym]

@ericjohannsen the issue in this thread is not related to your problem and neither is the workaround. It's only applicable to applications running in IIS using AspNetCore InProcess hosting model. Can you please file your issue in http://github.com/aspnet/EntityFrameworkCore

[ericjohannsen]

@pakrym Are you certain? The issue is that EF receives its configuration from AspNetCore using this line:

    services.AddDbContext<MyContext>(options =>
        options.UseSqlite(Configuration.GetConnectionString("DefaultConnection")));

I can make it work by hacking appsettings.json like this:

  "ConnectionStrings": {
    //"DefaultConnection": "Filename=./db/my.db"
    "DefaultConnection": "Data Source=E:/dev/myproject/wwwroot/db/my.db"
  },

Have a look at this documentation,

If your startup project is an ASP.NET Core app, the tools try to obtain the DbContext object from the application's service provider.

The tools first try to obtain the service provider by invoking Program.BuildWebHost() and accessing the IWebHost.Services property.

If you still feel the issue is not related to how AspNetCore sets the current directory, please provide enough context so I can explain to the EF Core team why the problem resides with them.

[jkotalik]

I would make sure that you are running on ASP.NET Core 2.2.2 and check again.

[ericjohannsen]

I'm running on ASP.NET Core 2.2.3.