JCooney.NET

# re: From the "What were they thinking?" department. 11/30/2003 4:25 PM Frans Bouma

The name for that tool is easy:
The developer of that tool was once a big fan of LLBLGen (he was on the mailinglist, and the connect screen of nGen is very similar to LLBLGen 1.x's connect screen). LLBL stands for Lower Level Business logic Layer Generator. Now, he must have thought: "I want to write a tool that does more than just that lower layer, I want to do n-layers, hence the name nGen."

For the successor of LLBLGen, now called LLBLGen Pro, I thought of renaming it to nGen too, but decided not to (didn't know ngen.exe was in the framework then ;)).

The tool itself is not that good, there are much better tools on the market.

# re: From the "What were they thinking?" department. 11/30/2003 4:25 PM Frans Bouma

"The tool itself is not that good, there are much better tools on the market."
With 'The Tool' I ment nGen of course :)

# re: From the "What were they thinking?" department. 12/7/2003 3:56 AM Kevin Swarts

I was a fan of LLBLGen for about 2 days, until I noticed that it doesn't make my development cycles any less easy, and infact just help to over complicatate things. This is why I decided to put as much resources/time I could into developing something that will actually solve my problems.

The connect screen was taken not from LLBLGen, but from one of MS's products. Can't rememeber which.

The name nGen has nothing to do with LLBLGen. The n comes from my company's name nAlliance which dates back to 2001. Infact all of the company's products are branded with an 'n'. The Gen is a common place name in the code generator market. LLBLGen was not the first, nor the last product to use it.

The name nGen was never meant to be permanent, it was a name picked for internal use, and it was released as an early beta as nGen, until a better name could be found. That's why we came up with LPLGen (Lowest Possible Level Generator). Just kidding, the new name is nDevelopment, and it's output is far easier to use than LLBLGen. It has been proven to work on a database with over 160 tables, and more than a dozen views. The best part is, it just works as soon as you connect to and analyze a database. The only thing you have to type (assuming your database attributes are good) is the output paths. You don't even have to start VS.Net, it will compile for you.

BTW. A new beta is out. <a href="http://www.nAlliance.com/Products/nDevelopment">http://www.nAlliance.com/Products/nDevelopment</a>