Home
Help
Register
Log in

Search

 
   Active Threads  

You are here: Home > LLBLGen Pro > Architecture> Making Entity properties protected rather than public
 

Pages: 1
Architecture
Making Entity properties protected rather than public
Page:1/1 

  Print all messages in this thread  
Poster Message
Mountain
User



Location:
Florida
Joined on:
01-Apr-2005 05:05:51
Posted:
21 posts
# Posted on: 07-Apr-2005 00:36:19.  
For the Entity properties that correspond to our database columns, I would like to make them protected (by changing the template). If we always derive from these classes and make our own public methods where needed, will anything else in the generated code or ORM support classes break by making these methods protected? Thanks.
  Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
38092 posts
# Posted on: 07-Apr-2005 09:20:21.  
No they should be fine. The runtime libraries use the Fields object.

Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
Pages: 1  


Powered by HnD ©2002-2007 Solutions Design
HnD uses LLBLGen Pro

Version: 2.1.12172008 Final.