Hello,

I'm trying to get the latest version of llblgen to work with the free version of Oracle.

Oracle 10g Release 2 Express, this comes with an ODP version of 10.2.0.100, is there a work around for this problem.

Thanx

James

IT should work with that ODP.NET version, you get an error of some kind?

Yes,

the main error that i have noe managed to get it down to is version miss match, llblgen reads the catalogue and creates the DAL accordingly, its only when the dal is activated that i seem to get the error.

Thanks.

You mean, when you want to fetch data? Which error do you get exactly? It's a bit hard to guess what's wrong if we don't know the details

The exact error that i have been getting are as follows

"The located assembl's manifest definition with name 'Oracle.DataAccess' does not match assembly reference"

Thanks

The 10.2.x.x odp.net also should redirect all references to that assembly through a policy file. Could you please check if in c:\windows\assembly there's a file called Policy.10.2.Oracle.DataAccess ?

Yes there is serveral references to 10.2.x i have the following:

Oracle.DataAccess 10.2.0.100 Oracle.DataAccess.resources 10.2.0.100 - Multiple versions for different cultures

hope this helps.

Thanx

But no policy file? Policy.10.2.Oracle.DataAccess ?

No i do not have that within the c:\windows\assembly folder

phoenix wrote:

No i do not have that within the c:\windows\assembly folder

Ok, then that's the problem. For my understanding, the 10.2.x provider is still beta, which might be the reason why they didn't provide the policy file.

Ok, open llblgenpro.exe.config in a texteditor and add an assembly redirect to the list of redirects you already see in that config file. It should be something like: <dependentAssembly> <assemblyIdentity name="Oracle.DataAccess" publicKeyToken="89b483f429c47342" culture="neutral" /> <bindingRedirect oldVersion="9.2.0.0-10.1.0.999" newVersion="10.2.0.100"/> </dependentAssembly>

you also need to add that to your own app.config file to make sure the DQE is able to use the proper oracle odp.net assembly.

I'm not sure if this works or not, as 10.2.0.x is IMHO still beta and probably has different assembly layout but it's worth a shot.

Hello,

I have tried the above fix but still i get the same error,

"The located assembly's manifest definition with name 'Oracle.DataAccess' does not match the assembly reference "

The exception details: System.IO.FileNotFoundException: File or dependancy not found.

From the assembly load trace:

Log: DisplayName = Oracle.DataAccess, Version=10.1.0.301, culture=nutral, publickey=89b483f429c47342(fully- specified) Log: Publisher Policy file is not found.

i have also added the details into the c:\windows\Microsoft.Net\Framework\aspnet.config file. this still has the same effect.

Thanks

then the redirect as defined isn't correct. What did you add to the llblgenpro.exe.config file and where did you place that exactly?

Hello, I added the provided code into the AssemblyBinding section of the llblgenpro.exe.config file.

Within that section i inserted the code block just above the "probing" section and below the "SD.LLBLGEN.Pro.LptParser" definition.

This is the code that i added, as posted in an earlier message

<dependentAssembly> <assemblyIdentity name="Oracle.DataAccess" publicKeyToken="89b483f429c47342" culture="neutral" /> <bindingRedirect oldVersion="9.2.0.0-10.1.0.999" newVersion="10.2.0.100"/> </dependentAssembly>

Thank you

Huh? hmm.... That's impossible, with that in place, when you then create a new project, it should load the assembly just fine...

Fixed the problem,

i have managed to come up with a solutions that solves the problem, going along the lines of your deifinition, add the following lines of code to the bottom of you app.config file just before the close of configuration.

<runtime> <assemblyBinding xlms="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="Oracle.DataAccess" publicKeyToken="89B483F429c7342"/> <bindingRedirect oldVersion="10.1.0.000-10.2.0.100" newVersion="10.2.0.100"/> </dependentAssembly> </assemblyBinding> </runtime>

Hope this help anyone else who may have the same problem as i did, thanks for all your help Otis.

Glad it's fixed. Still strange it didn't work with the other redirect though...

I have been fighting with this same problem off and on for days.

The redirects were not working. The fusion logs just showed that it was not finding the redirect, but no clue why.

Finally I changed:

  <assemblyBinding>

To

  <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">

And all is well with the world. The redirects work as expected.

I don't understand the config schema process well enough to know what was changed or not found, etc, but it sure did something!

Pat Connelly

Hmm, you needed the redirects in a web.config file? because the schema isn't required normally...

No, this was in the App.config for a windows form application.

Very strange... but thanks for the info!