Home
Help
Register
Log in

Search

 
   Active Threads  

You are here: Home > LLBLGen Pro > Bugs & Issues> The provider did not return a ProviderManifest instance
 

Pages: 1
Bugs & Issues
The provider did not return a ProviderManifest instance
Page:1/1 

  Print all messages in this thread  
Poster Message
Emmanuel
User



Location:
Ottawa, Canada
Joined on:
13-Jan-2006 23:14:31
Posted:
167 posts
# 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.




  Top
Emmanuel
User



Location:
Ottawa, Canada
Joined on:
13-Jan-2006 23:14:31
Posted:
167 posts
# 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.


  Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
37880 posts
# 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
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
Emmanuel
User



Location:
Ottawa, Canada
Joined on:
13-Jan-2006 23:14:31
Posted:
167 posts
# 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.


  Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
37880 posts
# 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
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
Pages: 1  


Powered by HnD ©2002-2007 Solutions Design
HnD uses LLBLGen Pro

Version: 2.1.12172008 Final.