.NET
Articles relating to .NET Framework or C# in general.
Attributes are elements of metadata that you can attach to entities such as assemblies, classes, methods, properties, et al. The .NET Framework makes use of many attributes that allow you to affect the behavior of the compiler or how the Framework uses an entity. For example, you can assign attributes to properties of a control object that allow a friendly name and description to be shown in the property browser in Visual Studio. At some point, you'll come into a situation where you'll want to use...
Keith Pijanowski had a great article in MSDN magazine titled “Enrich Your XML Serialization With Schema Providers in the .NET Framework.” His article talks about the use of XML schemas for the purpose of serialization with classes. Using an XML schema removes some of the limitations I mentioned in a previous article about using XML serialization including the need for a set accessor.
This of course brings a new problem to the table. Where do you put the schema files? The most obvious choi
Initialization parameters allow you to initialize the state of an event control based on your environment. For example, you might have a connection string defined as a initialization parameter, so that the connection can easily be changed. Registration arguments are conditions you place on the link between a producer and consumer. The condition determines whether or not an appropriate event is passed to the consumer.
Initialization parameters and registration arguments are defined within t
The iMotion Edgeware framework provides initialization parameters for event controls as well as registration arguments for the link between a producer and consumer. The initialization parameters and registration arguments only support string values, because they are saved as XML elements within the project configuration file.
Sometimes it is necessary to save an object that may have many fields as either an initialization parameter or a registration argument. Or worse if you want an array o
The EPCglobal tag data standards provides a calculation for the GTIN (global trade item number) check digit during SGTIN (serialized global trade item number) decoding. However, this algorithm although mathematically correct does not work computationally due to different methods of handling modulus for negative numbers.
The tag data standards document defines the calculation for the GTIN check digit as:
d14 = (-3(d1 + d3 + d5 + d7 + d9 + d11 + d13) - (d2 + d4 + d6 + d8 + d10 + d12)) mod 1
So, localizing display properties in the PropertyGrid has been done before. Probably ten different ways. However, until the .NET Framework 2.0 it required some messy implementation in the concrete class. Version 2.0 adds the TypeDescriptionProvider which can be tied to a particular class using the TypeDescriptionProviderAttribute. The attribute accepts a type that inherits the TypeDescriptionProvider base class...
I just had a dilemma today that called for a solution better than using if or case statements. After some thought, probably too much thought (my excuse is I'm tired), I determined that the Visitor pattern could do a much better job without being a maintenance nightmare...
This article discusses the creation of user defined aggregates (UDA) in SQL Server 2005.