Stupid Question
Joined: 26-Oct-2003
Joined: 28-Jun-2004
Joined: 26-Oct-2003
Using the Object Browser is fine for me but I am trying to lead a team on our first project using LLBLGen and I am desperately looking for way's to hush the wining 
.
Joined: 26-Oct-2003
BSAPD wrote:
Using the Object Browser is fine for me but I am trying to lead a team on our first project using LLBLGen and I am desperately looking for way's to hush the wining
Well, you could iterate through each entitytype, then iterate through each field in the .Fields collection and print out it's name. Just a thought 
Jeff...
P.S. Just tell them they'll never have to create another DAL again. If that doesn't shut 'em up, I don't know what will. 
jeffreygg wrote:
Well, you could iterate through each entitytype, then iterate through each field in the .Fields collection and print out it's name. Just a thought
Thats not a half bad idea! Would be pretty easy too 
.
jeffreygg wrote:
P.S. Just tell them they'll never have to create another DAL again. If that doesn't shut 'em up, I don't know what will.
Man, I wish it was that easy!
We have a bunch of old school VB and ASP developers who don't even belive that OOP is better than Modular 
. Some of them make very good arguments too 
. But like with most things, I think after we get through this beginning stage they will see at least some value .
BSAPD wrote:
Using the Object Browser is fine for me but I am trying to lead a team on our first project using LLBLGen and I am desperately looking for way's to hush the wining
To get a nice .chm file you definitely should check out ndoc.
Just generate a C# version of the code, compile it with teh option to generate xml output as well (it's a vs.net project setting), then run ndoc on the xml and assembly and you're done.
NDoc needs with Northwind about 15 minutes to generate the .chm which is the reference manual for llblgen pro. Your team members can also use that one, as it illustrates the methods available.
Otis wrote:
To get a nice .chm file you definitely should check out ndoc.
Just generate a C# version of the code, compile it with teh option to generate xml output as well (it's a vs.net project setting), then run ndoc on the xml and assembly and you're done.
NDoc needs with Northwind about 15 minutes to generate the .chm which is the reference manual for llblgen pro. Your team members can also use that one, as it illustrates the methods available.
Speaking of NDoc, I am curious, why the comments that get generated in the VB.NET template are not in the format NDoc can use? We use NDoc for all our VB.NET projects and it works fine using three apostrophes ('''<summary></summary>).
I forgot to mention there is also a VS Plug-In involved in this, VB Commenter (http://www.gotdotnet.com/community/workspaces/viewuploads.aspx?id=112b5449-f702-46e2-87fa-86bdf39a17dd).
I don't think it's well supported though, oh well.
BSAPD wrote:
Otis wrote:
To get a nice .chm file you definitely should check out ndoc.
Just generate a C# version of the code, compile it with teh option to generate xml output as well (it's a vs.net project setting), then run ndoc on the xml and assembly and you're done.
NDoc needs with Northwind about 15 minutes to generate the .chm which is the reference manual for llblgen pro. Your team members can also use that one, as it illustrates the methods available.
Speaking of NDoc, I am curious, why the comments that get generated in the VB.NET template are not in the format NDoc can use? We use NDoc for all our VB.NET projects and it works fine using three apostrophes ('''<summary></summary>).
I forgot to mention there is also a VS Plug-In involved in this, VB Commenter (http://www.gotdotnet.com/community/workspaces/viewuploads.aspx?id=112b5449-f702-46e2-87fa-86bdf39a17dd).
I don't think it's well supported though, oh well.
When I wrote the VB.NET templates I wasn't aware of a format for VB.NET. Whidbey also uses ''' so I'll change the comments in VB.NET in the future.