Hello,

We just adopted LLBLGen Pro as our ORM for our applications. We purchased a few licenses, with the intention of having a few designated sr. developers generating code. In this scenario, a junior developer would request code regeneration if the change he/she was working on required it.

All of our developers are doing their development on their own virtual machines, and the LLBLGen application (with the runtime framework) will only be installed on a few of the VMs. My question is, is there a redistributable framework package or other option to easily place the llblgen framework on the developers who do not have the llblgen pro application installed, so when they work with generated code, it will just work, without them having to do some file copying or re-referencing in their projects.

Another thought I had, was to copy all of the runtime assemblies into a single folder in source control, and have the developers check them out, but I am thinking this would cause a broken reference issue when the source code was generated, because the project would be referencing the assemblies that were installed with LLBLGEN pro, which would not exist on the VMs that do not have LLBLGEN pro installed. Thoughts on this as well?

Thanks, Shaun

The single folder in source control containing the runtime assemblies is the way to go. The way to avoid the broken references is to generate the code once, so that the default generated project references the installed versions.

If you then open this project in visual studio, and point the references to the assemblies in your folder, LLBLGen is smart enough not to rewrite the references next time the code is generated.

Matt

Ok, that is what I kind of thought. Thanks for the help!

No Problem!

Matt