Hi lblgen team,

we are planning to use llblgen in the development of a suite of commericial software product. we have evaluated it several times but not throughly. I have questions, is it possible to renamed the assembly into something the that will not messup our BIN directories. because it will look like a third part assembly on deployed app and its not so appealing to customers to see those SD..... DD , can we just say recompile it into MyCompany.MyProduct.Data.Helpers etc.

Thank you.

Rodel E. Dagumampan Lead .NET Software Engineer FlexMerchant Software Inc MCTS - Web, Microsoft MVP - C#

No reply?

suddenserenity wrote:

No reply?

We're based in Europe, so in a different timezone

A licensee gets access to the sourcecode of the runtime library, and can recompile that code, alter it and also rename the assembly names if required.

will we be guarantee that there are no fatal effects with the generated code or something. is it guranteed that there are no dependencies on these filenames like having AsseblyLoad, Reflection, etc.

I havent checked the prices for this license but you may post it here. We are very much interested.

Many thanks fellow. -rodel

suddenserenity wrote:

will we be guarantee that there are no fatal effects with the generated code or something. is it guranteed that there are no dependencies on these filenames like having AsseblyLoad, Reflection, etc.

I havent checked the prices for this license but you may post it here. We are very much interested.

Many thanks fellow. -rodel

We don't load the runtime libs manually, they're normal assemblies referenced by you in your generated code projects. There's no tie to the name of the assemblies in the runtime lib, other than that the initial vs.net project file generated refers to the original names but that's a one-time name change.

Of course, the query engine assemblies reference the ORMSupportClasses assembly, so you have to change that reference in the runtime lib sourcecode. Our runtimelibs are build using nmake files which are shipped with the sourcecode, so you've to alter a couple of names there, but that's it.

There's one caveat: the sourcecode is licensed to an LLBLGen Pro licensee with a BSD2 style license, which means that if you alter anything, you've to mention the copyright statement in your documentation and/or application.

Prices are available here: http://www.llblgen.com/pages/buy.aspx

We don't have a separate sourcecode license, all licensees get access to the sourcecode (except for the designer)