Hi,

We have a lot of legacy code that uses LLBLGen Pro v3.5. We now have to add new features, and for this I wanted to use LLBLGen Pro v4.0. I compiled the project successfully, but I get the following run time exception:

The type initializer for 'SD.LLBLGen.Pro.ORMSupportClasses.DependencyInjectionInfoProviderSingleton' threw an exception

you can find detail info about exception in the text file that is attach herewith.

How do I address this?

NOTE: Migrating all the existing legacy code to LLBLGen Pro v4.0 is not possible. All the new features are totally independent of any existing code.

You're referencing in your code where you get this exception the v4.0 runtimes, however I think you refer to the v3.5 runtime assembly in your web/app.config file (for the section declarations). Please update your web/app.config file of your application which gives this exception.

thanks for your response,

Yes, we have DependencyInjectionSectionHandler registered for using additional library which references v3.5 runtime library. This is part of legacy code.

1) can i use both version of llblgen pro v3.5 and **llblgen pro v4.0 ** in the same web application. Our existing code use v3.5 and we are adding new functionality using v4.0.

2) We started using v4.0 for the new functionality as v4.0 is available on your website. If v3.5 and v4.0 cannot be used together then can i get trail version of llblgen pro v3.5.

3) If i have to use v3.5 then how do i get licence for llblgen pro v3.5.

Are you a v4 customer? (i.e. Did you bought a v4 license?)

You cannot use different runtime library version because at some point you will get ambiguity errors, and you actually have to generate and reference on your generated code. So, in your case I think you should use v3.5 for the moment. If you are a v4 customer, you can ask for a v3.5 license, you can do so in a HelpDesk thread, providing your CustomerID.

No, I was using v4.0 trail version for evaluating that it meet our requirements.

Do you mean that i will have to buy v4.0 to get v3.5. Is there any way that you provide me with the v3.5 trial installer so that it make thing moving faster because it has to go through our purchase process to purchase license.

chandu175 wrote:

No, I was using v4.0 trail version for evaluating that it meet our requirements.

Ok.

Do you mean that i will have to buy v4.0 to get v3.5. Is there any way that you provide me with the v3.5 trial installer so that it make thing moving faster because it has to go through our purchase process to purchase license.

What I wonder is: if you have a lot of 3.5 legacy code, how is that made if you don'thave a v3.5 license? Or is that created by a 3rd party and you have to adjust it?

If you purchase 4, you can request a v3.x license for free and we'll send you one. You can then download v3.5 from the website and make your changes and e.g. later on decide whether you want to move to v4.