Questions and Answers on any aspect of .NET. Now closed.
I'm using custom attributes in some of my classes to form an sql statemment for creating a database where I'm planning to store instances of these classes. There's a class in this hierarcy that has a lot of simple private fields for which I created fake properties that do nothing but marked with the custom attribute (to describe a table's field) and marked them as private. But I found out that they weren't in the resulting sql statement. After I marked one of these private property as public and formed the sql it appered.
The question is - How to use the custom attributes in the way I did, but not exposing these fake properties (not to pollute the class interface)?
Tuesday, January 16, 2007
This topic is archived. No further replies will be accepted.Other recent topics
Powered by FogBugz