It would be nice if the entity constructors were put into a code region.

BOb

Could you explain why exactly this is better?

I agree with Bob, I've changed it myself (in the EntityUsingEntityBase_classes).

It's better, because I've nothing to do in that code, and in a region we can hide it

BertS wrote:

I agree with Bob, I've changed it myself (in the EntityUsingEntityBase_classes).

It's better, because I've nothing to do in that code, and in a region we can hide it

Isn't in then better to simply hide all the code which isn't updateable in a region?

Otis wrote:

BertS wrote:

I agree with Bob, I've changed it myself (in the EntityUsingEntityBase_classes).

It's better, because I've nothing to do in that code, and in a region we can hide it

Isn't in then better to simply hide all the code which isn't updateable in a region?

Let me be more clear. In the self-servicing two class scenerio the Entity classes constructors are not in ANY region. So, the code can not be collapased and hidden.

BOb

pilotboba wrote:

Otis wrote:

BertS wrote:

I agree with Bob, I've changed it myself (in the EntityUsingEntityBase_classes).

It's better, because I've nothing to do in that code, and in a region we can hide it

Isn't in then better to simply hide all the code which isn't updateable in a region?

Let me be more clear. In the self-servicing two class scenerio the Entity classes constructors are not in ANY region. So, the code can not be collapased and hidden.

BOb

I assume you're talking about the derived classes? (as in the entitybase classes, a lot of code isn't in a region as well). I've added the regions to the 1.0.2005.1 code

Otis wrote:

I assume you're talking about the derived classes? (as in the entitybase classes, a lot of code isn't in a region as well). I've added the regions to the 1.0.2005.1 code

Yes, the derived classes. I don't much care about the Base/Parent classes cause I don't work in them, and if I want to look at them I want to see the genned code.

Thanks...

BOb