The provider did not return a ProviderManifest instance

Posts   
 
    
Emmanuel
User
Posts: 167
Joined: 13-Jan-2006
# Posted on: 17-Jun-2015 02:54:52   

Just upgraded my designer from the Feb 16 2015 build to the June 9 2015 and tried to recompile my generated project. But an now getting an error in the generated edmx file now:

"Error 168: The provider did not return a ProviderManifest instance. The provider did not return a ProviderManifest instance."

I tried changing the "Provider manifest token value" from "2012" that I had when I successfully compiled Feb 16 2015 code to "2008" but that didn't help.

EF6, .NET4.5, General template group, SD.EntityFramework.v6 (Code First) preset.

Emmanuel
User
Posts: 167
Joined: 13-Jan-2006
# Posted on: 17-Jun-2015 03:26:55   

Emmanuel wrote:

Just upgraded my designer from the Feb 16 2015 build to the June 9 2015 and tried to recompile my generated project. But an now getting an error in the generated edmx file now:

"Error 168: The provider did not return a ProviderManifest instance. The provider did not return a ProviderManifest instance."

I tried changing the "Provider manifest token value" from "2012" that I had when I successfully compiled Feb 16 2015 code to "2008" but that didn't help.

EF6, .NET4.5, General template group, SD.EntityFramework.v6 (Code First) preset.

My fault. I didn't notice that after upgrading the designer, the Generate source code dialog changed my selected preset from Code First to Db.

It also changed the order of my template bindings precedence.

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39613
Joined: 17-Aug-2003
# Posted on: 17-Jun-2015 09:33:27   

Emmanuel wrote:

Emmanuel wrote:

Just upgraded my designer from the Feb 16 2015 build to the June 9 2015 and tried to recompile my generated project. But an now getting an error in the generated edmx file now:

"Error 168: The provider did not return a ProviderManifest instance. The provider did not return a ProviderManifest instance."

I tried changing the "Provider manifest token value" from "2012" that I had when I successfully compiled Feb 16 2015 code to "2008" but that didn't help.

EF6, .NET4.5, General template group, SD.EntityFramework.v6 (Code First) preset.

My fault. I didn't notice that after upgrading the designer, the Generate source code dialog changed my selected preset from Code First to Db.

It also changed the order of my template bindings precedence.

That's odd. Did you change .net version by any chance? The preset and template binding precedence is stored in the project file and is used as-is, it's not changed between builds.

Frans Bouma | Lead developer LLBLGen Pro
Emmanuel
User
Posts: 167
Joined: 13-Jan-2006
# Posted on: 17-Jun-2015 15:31:17   

Otis wrote:

Emmanuel wrote:

Emmanuel wrote:

Just upgraded my designer from the Feb 16 2015 build to the June 9 2015 and tried to recompile my generated project. But an now getting an error in the generated edmx file now:

"Error 168: The provider did not return a ProviderManifest instance. The provider did not return a ProviderManifest instance."

I tried changing the "Provider manifest token value" from "2012" that I had when I successfully compiled Feb 16 2015 code to "2008" but that didn't help.

EF6, .NET4.5, General template group, SD.EntityFramework.v6 (Code First) preset.

My fault. I didn't notice that after upgrading the designer, the Generate source code dialog changed my selected preset from Code First to Db.

It also changed the order of my template bindings precedence.

That's odd. Did you change .net version by any chance? The preset and template binding precedence is stored in the project file and is used as-is, it's not changed between builds.

You're correct. I changed from .NET 4 to 4.5 - hadn't noticed that doing that undid my present and template order of precedence.

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39613
Joined: 17-Aug-2003
# Posted on: 17-Jun-2015 17:57:51   

Yes it resets the bindings/presets as it does a complete re-filter on assets. I'll make a note that we document this properly so confusion is avoided.

Frans Bouma | Lead developer LLBLGen Pro