print entitys from designer

Posts   
 
    
jspanocsi
User
Posts: 145
Joined: 04-Mar-2005
# Posted on: 29-Dec-2005 17:21:07   

Is there a way to print entity information from the llbl designer? I need to create some documentation for other developers.

Something like CustomerEntity -> Table CUS104 Fields: Recordid -> CUS104ID CustomerName -> cname

etc etc

If not that would be a good feature to add... wink Thanks!

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39930
Joined: 17-Aug-2003
# Posted on: 29-Dec-2005 18:07:14   

Not at the moment. You could generate a .chm documentation file from the generated code which does contain this information, using ndoc for example. Then the developers could search and browse through the info on their system instead through paper simple_smile

Frans Bouma | Lead developer LLBLGen Pro
jspanocsi
User
Posts: 145
Joined: 04-Mar-2005
# Posted on: 03-Jan-2006 18:35:07   

do you happen to know anything other than ndoc? It doesn't work very well with vs.net 2005 disappointed

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39930
Joined: 17-Aug-2003
# Posted on: 04-Jan-2006 09:15:26   

jspanocsi wrote:

do you happen to know anything other than ndoc? It doesn't work very well with vs.net 2005 disappointed

You mean with generics ? I havent tried ndoc with code specially written for .net 2.0.

Frans Bouma | Lead developer LLBLGen Pro
jspanocsi
User
Posts: 145
Joined: 04-Mar-2005
# Posted on: 06-Jan-2006 15:27:20   

no just in general. I can't run ndoc on an llbl gened project that's compiled in 2005. It blows up. Sorry I don't have the error in front of me or I'd post it. You have to have vs 2003 installed to get ndoc to even work and I don't have that at work.

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39930
Joined: 17-Aug-2003
# Posted on: 06-Jan-2006 15:36:40   

I haven't tried it for automated doc production, but if you sign up for the visual studio integration partner program (it's free) at the msdn site, you can download the SDK for vs.net 2005, which comes with a 3rd party documentation toolkit. Again, I'm not sure if it's capable of generating automated documentation.

Frans Bouma | Lead developer LLBLGen Pro
jspanocsi
User
Posts: 145
Joined: 04-Mar-2005
# Posted on: 06-Feb-2006 15:19:56   

this got me in the right direction. The product in the sdk was something by innovasys. this lead me to documentX which does this. It's pretty good, but about 450 bucks.

this lead me to try other things first... One thought for the LLBL IDE is to have the grids export to excel. This would probably be a quick easy solution for you. I'm not sure about Janus grid, but with infragistics it was as easy as droping an export control on the form and pointing it at the grid.

Would your pluging model allow for me doing this? I can get to everything in the llbl file right? I might look into this if I have time.

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39930
Joined: 17-Aug-2003
# Posted on: 06-Feb-2006 17:35:05   

jspanocsi wrote:

this got me in the right direction. The product in the sdk was something by innovasys. this lead me to documentX which does this. It's pretty good, but about 450 bucks.

this lead me to try other things first... One thought for the LLBL IDE is to have the grids export to excel. This would probably be a quick easy solution for you. I'm not sure about Janus grid, but with infragistics it was as easy as droping an export control on the form and pointing it at the grid.

Would your pluging model allow for me doing this? I can get to everything in the llbl file right? I might look into this if I have time.

It's an excellent option for a plugin simple_smile You can access any object, property and method in the project file. So you can export whatever you like to whatever format you need simple_smile

Frans Bouma | Lead developer LLBLGen Pro