Look at
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/bdadotnetarch14.asp
.
--- Colesy <[EMAIL PROTECTED]> escribió: > Hi - I've
been pulling my hair out for the last
> month trying to make the
> right choice for our systems middle tier. I was
> hoping that someone
Don't want to sound too spammy here, but the team that I work for built
a Visual Studio .NET Add-in that will do properties like this for you.
If you're interested, check out the screenshots on the Codify website
[1] or take a look at the description [2] of the Simple Property Builder
template.
P
> Also, some ams have rules. Our rules say: NO PUBLIC VARIABLES. NEVER.
Thomas,
IMHO This is a good rule - as long as it applies to public classes only. But
if the classes are private to your assembly, I don't see the point of not
having public members. After all, there can be quite a performance
Here's a question that I had recently, that's sort of related to your thread. I was
writing code
that had to be optimized for speed, and one of the things I did to speed things up was
use
immutable objects. I made the properties of each of these objects into readonly
fields, and
assigned their
What about later extensibility? Do you want all the clients of your
objects to HAVE to recompile?
Also, some ams have rules. Our rules say: NO PUBLIC VARIABLES. NEVER.
:-)
Leaves us with a lot of properties.
That said - I don't think we need a keyboard,j ust some automatism to
write this code f
>I find it is very common to have a private field that properties use to
hold there value, like
>get{return holder;}set{holder=value;}
If that's all you are doing in a property's methods then why not remove the
property and make the private field public?
[)amien
=
Personally I would be wary of remoting with callback or events;
see http://www.ingorammer.com/RemotingFAQ/RemotingUseCases.html
especially if you are looking for scalability, LAN's and events/callbacks.
-Original Message-
From: Colesy [mailto:[EMAIL PROTECTED]
Sent: 21 October 2003 02:
Hi - I've been pulling my hair out for the last month trying to make the
right choice for our systems middle tier. I was hoping that someone out
there might be able to suggest the best fit: basically we are building an
IVR system with C#.NET, handling potentially 100's of calls on competition
lines
I find it is very common to have a private field that properties use to hold
there value, like
get{return holder;}set{holder=value;}
Does anyone have opinions regarding making that a part of a language, much
like 'value' is in C#? Of course it would compile to exactly what it
compiles to now. It
