Hey guys,

Has anyone rolled out LLBLGen Pro to the rest of your company. I work in a considerably large company, and I am worried about the skill of some of our developers (most have only a few years experience in scripting like asp, and have only made the jump into .NET in the last couple of months)

e.g. a lot of our developers work offsite, and I don't really want to spend all my time on the phone helping them out

How have you guys found rolling out LLBLGen Pro?

-Scott

PS: The project I worked on with LLBLGen worked extremely well,

smcculloch wrote:

Has anyone rolled out LLBLGen Pro to the rest of your company. I work in a considerably large company, and I am worried about the skill of some of our developers (most have only a few years experience in scripting like asp, and have only made the jump into .NET in the last couple of months) e.g. a lot of our developers work offsite, and I don't really want to spend all my time on the phone helping them out

Please keep in mind that LLBLGen Pro comes with a department license, so HP can buy one license but then not all 111,000 employees may use it. So if your company has for example 3 development departments, it should have a license for each department. This also distributes the roll-out problem -> each department takes care of which developers use the tool and can schedule support internally.

If your company has one development department and that department has the license, and as you said, a lot of the developers work off site (f.e. onsite at customers), they all can share the same license and it's f.e. wise to tell them about this forum where they can register and ask questions or read about questions others had (yes search is implemented soon ). This will make it a bit easier for you I think (although people are lazy and will call you anyway... )

PS: The project I worked on with LLBLGen worked extremely well,

Great! I read on asp.net you are also evaluating EntityBroker. I would be interested in the results of that evaluation if you want to share that with me (not for marketing purposes, just knowledge about where I can improve the tool )