Event Logging Using Reflection
When exceptions occur during the execution of an application, the stack trace contains the detailed location of where the exception is originated.
When exceptions occur during the execution of an application, the stack trace contains the detailed location of where the exception is originated.
Reflection is case sensitive by default, which comes at no surprise to most C# developers.
Download DynamicEvent.zip In an article earlier, I discussed how to dynamically load an assembly and execute it via the contract of a predefined interface.
Download ReflectionTest.zip There are already many good guides out there illustrating how to construct a weakly coupled system that dynamically loads in modules as needed. In .Net, this can be accomplished using reflection.
Download readfileviareflection.zip In .Net, an XML file or even a CSV file can easily be mapped to an object using proper attributes. Using the reflected object type, such XML or CSV files can easily be deserialized into the corresponding object.
Background In .Net, distributed computing can be done in a number of ways.
In a post last year, I wrote about the pitfalls when generating classes using the xsd tool in .Net framework 1.1.