Hello

I just got LLBGEN started learing and using it. I just have one serious question.

I noticed that without adding the reference of Proprietary DLL like ORMapper.DLL, SD.LLBLGEN.....DLL, the generated code is rendered use less.

My doubt is since these are Proprietary DLL's what if tomorrow if I have to work on different OS. Let us say Windows 2012 ! ! (when released).

How can a code generated using LLBLGEN 2.6 can be used on Windows 2012 since it uses Proprietary DLL

Warm Regards

Shekar

It's build on top of .net 2.x, so as long as .net 2.x is supported on windows (and you can be sure about that, or at least the .net framework of windows <high number> is compatible with it, the code will run without problems. A licensee also has the sourcecode of the runtime, so you can recompile the code for the .net framework of the future if you need to.

To Conclude Please clarify what I have understood is right based on your answer

LLBLGEN Dll's are related to framework and not OS.

I mean as long as I use .Net 3.5 all DLL's will work which is built on .Net 3.5 " IRRESPECTIVE OF WHICH WINDOWS OS VERSION I AM USING"

If .NET frame work is changed, then probably I will have to regenerate the project for respective version and nothing else.

Am I correct?

• Shekar

Otis wrote:

It's build on top of .net 2.x, so as long as .net 2.x is supported on windows (and you can be sure about that, or at least the .net framework of windows <high number> is compatible with it, the code will run without problems. A licensee also has the sourcecode of the runtime, so you can recompile the code for the .net framework of the future if you need to.

shekar wrote:

To Conclude Please clarify what I have understood is right based on your answer

LLBLGEN Dll's are related to framework and not OS.

I mean as long as I use .Net 3.5 all DLL's will work which is built on .Net 3.5 " IRRESPECTIVE OF WHICH WINDOWS OS VERSION I AM USING"

If .NET frame work is changed, then probably I will have to regenerate the project for respective version and nothing else.

Am I correct?

• Shekar

yes. Microsoft also makes sure that new .net frameworks are compatible with old ones at least compatible with .NET 2.0, as it will otherwise break their own code as well.

LLBLGEN Dll's are related to framework and not OS.

I mean as long as I use .Net 3.5 all DLL's will work which is built on .Net 3.5 " IRRESPECTIVE OF WHICH WINDOWS OS VERSION I AM USING"

Correct.

If .NET frame work is changed, then probably I will have to regenerate the project for respective version and nothing else.

Am I correct?

Correct and also you should have the source code of LLBLGen Dlls so you can recompile them on any future framework version.

Thanks. You may close this issue now

• Shekar

Walaa wrote:

LLBLGEN Dll's are related to framework and not OS.

I mean as long as I use .Net 3.5 all DLL's will work which is built on .Net 3.5 " IRRESPECTIVE OF WHICH WINDOWS OS VERSION I AM USING"

Correct.

If .NET frame work is changed, then probably I will have to regenerate the project for respective version and nothing else.

Am I correct?

Correct and also you should have the source code of LLBLGen Dlls so you can recompile them on any future framework version.