I am running into some problems while trying to get DAAB from Enterprise library 5.0 running. I have followed the steps as per the tutorial, but am getting errors...
1) Download / install enterprise library
2) Add references to the blocks I need (common / data)
3) Imports
Imports Microsoft.Practices.EnterpriseLibrary.Common
Imports Microsoft.Practices.EnterpriseLibrary.Data
4) Through the enterprise library config software. I open up the web.config from my site. I then click Blocks, then Add data settings... fill in my details and save / close
5) I then (thinking setup is complete) try to get an instance of the database via
Dim db As Database = DatabaseFactory.CreateDatabase()
6) I compile and receive the following error:
Could not load file or assembly 'Microsoft.Practices.EnterpriseLibrary.Data, Version=5.0.414.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) (C:\site\web.config line 4)
Line 4 off my web.config was generated by the config tool and is:
<section name="dataConfiguration" type="Microsoft.Practices.EnterpriseLibrary.Data.Configuration.DatabaseSettings, Microsoft.Practices.EnterpriseLibrary.Data, Version=5.0.414.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="true" />
Am I missing a required step? Have I done the steps in the wrong order? Have I made a mistake?
Thanks a lot for the assistance.
The answer:
I had accidentaly referenced the assemblies from the src code folder. Which means the public tokens would have = null. I re-referenced to the assemblies in C:\Program Files\Microsoft Enterprise Library 5.0\Bin and the problem is now solved.
I already saw you got the answer; however, I wanted to point out that when you open the Config tool from VS, you have the option to tell the config tool what assemblies you want to have referenced:
When you fire up the config tool; it will reference the assemblies in the config file accordingly to your choice.
In addition to what @Nicolas answered you can over come this problem by removing public token in app.config where ever it being used with Enterprise Library 5.0 dll
Enterprise library has 2 downloads ...
Only the second one has the signed binaries ... which is what's necessary to resolve the "manifest definition does not match the assembly reference" error
(and FYI, the second one also includes the source code if you elect to install it)
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With