Azure Functions问题：自定义数据层库可编译但无法运行

Hey there! Let's dig into why your EF 6.1.3 data layer isn't working with your .NET 4.6 Azure Function even though it compiles. Here are the most common fixes and checks I've seen work for similar issues:

1. Ensure EF Assemblies Are Deployed Correctly #

Azure Functions might not copy all required Entity Framework binaries to the runtime environment, even if your library compiles:

• In your data layer project, set Copy Local to True for all EF-related references (like EntityFramework.dll and EntityFramework.SqlServer.dll).
• After deployment, verify these DLLs exist in your function's bin folder (use Kudu Console: Function App > Advanced Tools > Go > Debug Console > Site > wwwroot > [your function folder] > bin).

2. Double-Check Connection String Setup #

Even if you can read the connection string, how you use it with EF matters:

• If your DbContext uses a connection string name, ensure it matches exactly what's in local.settings.json (local dev) and the Function App Configuration (Azure portal).
• Pull the connection string dynamically instead of hardcoding it:

  var connString = ConfigurationManager.ConnectionStrings["YourConnStringName"].ConnectionString;
  var dbContext = new YourDbContext(connString);
  

• In Azure portal, set the connection string type to Custom (not "SQL Azure")—EF 6 expects its own format, not the platform-specific one.

3. Disable Automatic EF Initialization #

EF's automatic database initialization often causes issues in serverless environments:

• Add this to your DbContext constructor to turn off initialization entirely:

  public YourDbContext(string connString) : base(connString)
  {
      Database.SetInitializer<YourDbContext>(null);
  }
  

• Avoid automatic migrations—make sure your Azure SQL schema is already up to date with manual migrations.

4. Verify Azure SQL Access Permissions #

A working connection string doesn't guarantee the function can reach the database:

• In Azure SQL Server settings, enable Allow Azure services and resources to access this server in the firewall rules.
• Confirm the SQL user in your connection string has db_datareader/db_datawriter permissions (or higher) on the target table.
• Test the connection string locally with a simple console app to rule out SQL-side issues.

5. Check Function Runtime Compatibility #

Ensure your function runtime supports .NET 4.6:

• In Azure portal, go to Function App > Configuration > General settings > Runtime stack. Select .NET Framework and confirm the version is compatible (v1 runtime natively supports .NET 4.6; newer runtimes may work but double-check).
• For local development, make sure local.settings.json includes:

  "FUNCTIONS_WORKER_RUNTIME": "dotnet"
  

6. Enable Verbose Logging for Debugging #

To get exact error details, turn on detailed logging:

• In local.settings.json, add:

  "AzureFunctionsJobHost__logging__logLevel__Default": "Debug"
  

• In Azure portal, use the Log stream (Function App > Monitoring > Log stream) to capture exceptions when running the function. Look for EF-specific errors like missing assemblies or initialization failures.

If you can share the exact error message from logs, that'll help narrow down the issue even faster!

内容的提问来源于stack exchange，提问作者Richard Griffiths