Business entity with additional properties

[Stefano]

Hi all,

I'm designing classes for my application.

I'd like to create a business entity that could be expanded with other properties
when needed.

For example, this could be my entity:

MyBusinessClass
-> Property1
-> Property2
-> ...
-> OtherProperties

The "OtherProperties" property of the class could expose a name value collection
with the other properties associated to the entity.

Now, the question is:
can I use System.Configuration.SettingsProperty class to define the additional
property, and so declare the "OtherProperty" as SettingsPropertyCollection?

I mean: has someone used this before? Are this classes designed for this
purpose?

Thanks

Bye

Stefano

[Nicholas Paldino [.NET/C# MVP]]

Stefano,

You ^could^, but I don't think that this would be a good idea. The
reason for this is that every instance of your object (with each instance
representing separate entities) would share the same values, which is what I
am sure you don't want.

Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"Stefano" <st*****************@giasoft.it> wrote in message
news:43*************************@msnews.microsoft. com...

Hi all,

I'm designing classes for my application.

I'd like to create a business entity that could be expanded with other
properties when needed.

For example, this could be my entity:

MyBusinessClass
-> Property1
-> Property2
-> ...
-> OtherProperties

The "OtherProperties" property of the class could expose a name value
collection with the other properties associated to the entity.

Now, the question is:
can I use System.Configuration.SettingsProperty class to define the
additional property, and so declare the "OtherProperty" as
SettingsPropertyCollection?

I mean: has someone used this before? Are this classes designed for this
purpose?

Thanks

Bye

Stefano

[Stefano]

Hello Nicholas Paldino [.NET/C# MVP],

You ^could^, but I don't think that this would be a good idea.
The reason for this is that every instance of your object (with each
instance representing separate entities) would share the same values,
which is what I am sure you don't want.

I'm not sure that values will be shared.
Why did you say that?

I'm looking inside, using a reflector... that classes (SettingsProperty and
SettingsPropertyValue) doesn't have static members.

So, what is the correct use that we can do about this classes?

Thanks

Bye

[Nicholas Paldino [.NET/C# MVP]]

Stefano,

It doesn't have static members, but the classes are meant to store
values that are used application-wide, not instance-wide.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"Stefano" <st*****************@giasoft.it> wrote in message
news:43*************************@msnews.microsoft. com...

Hello Nicholas Paldino [.NET/C# MVP],

You ^could^, but I don't think that this would be a good idea.
The reason for this is that every instance of your object (with each
instance representing separate entities) would share the same values,
which is what I am sure you don't want.

I'm not sure that values will be shared.
Why did you say that?

I'm looking inside, using a reflector... that classes (SettingsProperty
and SettingsPropertyValue) doesn't have static members.

So, what is the correct use that we can do about this classes?

Thanks

Bye

[Stefano]

Hello Nicholas Paldino [.NET/C# MVP],

thanks for the answer. You're right.

Anyway...

It could be great if the BCL had supplied a class that we could have used
in order to define a property, like the one that Vadym suggests:

public class CustomProperty
{
Name
PropertyType
Value
SerializedValue
....
}

Stefano,

It doesn't have static members, but the classes are meant to store
values that are used application-wide, not instance-wide.

"Stefano" <st*****************@giasoft.it> wrote in message
news:43*************************@msnews.microsoft. com...

Hello Nicholas Paldino [.NET/C# MVP],

You ^could^, but I don't think that this would be a good idea.
The reason for this is that every instance of your object (with each
instance representing separate entities) would share the same
values,
which is what I am sure you don't want.

I'm not sure that values will be shared.
Why did you say that?
I'm looking inside, using a reflector... that classes
(SettingsProperty and SettingsPropertyValue) doesn't have static
members.

So, what is the correct use that we can do about this classes?

Thanks

Bye