JetEntityFrameworkProvider数据库优先模式使用问题求助（VS2017+Access2016）

Hey there, let's work through your JetEntityFrameworkProvider setup problems together—here's what you need to check and adjust:

1. Handling the Missing Key.snk File #

You’re right that newer versions of the JetEntityFrameworkProvider NuGet package no longer include a default Key.snk file, so adding your own is the correct first step. But there are a couple more things to verify:

• Configure Assembly Signing: Right-click your project → Properties → Signing tab. Check the box "Sign the assembly", then use the dropdown to select your custom Key.snk file. Make sure the file is properly added to your project (set its "Copy to Output Directory" property to "Do not copy" to avoid unnecessary duplication).
• Confirm EF & Provider Compatibility: Ensure your project references Entity Framework 6.x (since JetEntityFrameworkProvider 6.4.1 targets EF6). VS2017 works perfectly with EF6, but double-check that there are no version mismatches in your NuGet packages.
• Validate Connection String: For Access 2016, your connection string should look something like this:

  Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\Path\To\YourDatabase.accdb;Persist Security Info=False;
  

  Also, make sure you have the correct Access Database Engine (ACE) driver installed: match the bitness (32/64) to your project’s build configuration. If you’re using AnyCPU, uncheck "Prefer 32-bit" in your project’s build properties if you have the 64-bit driver installed.

2. JetDdexProvider & GenerateAssemblyInfo=false Setup #

Setting GenerateAssemblyInfo=false to centralize versioning is a smart move—here’s how to make sure it works smoothly:

• Manual Assembly Versioning: Since you’ve disabled auto-generated assembly info, you’ll need to maintain version details in your project’s AssemblyInfo.cs file. Add or update these attributes:

  [assembly: AssemblyVersion("1.0.0.0")]
  [assembly: AssemblyFileVersion("1.0.0.0")]
  

  This ensures consistent versioning across your project without conflicts from auto-generated files.
• Verify DDEX Integration: If you’re using the JetDdexProvider for database design tools in VS, restart Visual Studio after making the NuGet package changes. Then go to Tools → Options → Data Connections → Data Sources to confirm the Jet provider appears in the list. If it doesn’t, you may need to repair the NuGet package (right-click the package → Manage NuGet Packages → Uninstall, then reinstall) to trigger proper DDEX registration.

Quick Additional Checks #

• Target Framework: Ensure your project targets .NET Framework 4.5 or later (JetEntityFrameworkProvider doesn’t support older frameworks).
• Runtime Errors: If you get a "Jet engine not found" error, double-check the ACE driver installation—match the bitness to your project’s build configuration to avoid mismatches.

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