Categories

Things in Metadata that are missing in Reflection

System.Reflection is a high-level way of describing Types in .NET targetted at managed code consumers. The API is easy to use, but does not expose all the information that's actually present and affecting decisions. For example, Reflection does not expose TypeRef , MemberRef, AssemblyRef, or other Ref tokens.

Filed under: Design, Architecture | On : 2008 Mar 15 | From: Mike Stalls blog |

A future world without the SQL Server Image/Text/NText data types. Now's the time to start planning for that future...

ASP.NET Case Study: Hang on WaitOne, WaitAny or WaitMultiple

Similar Posts

Describing Types in .NET

There are several different APIs for handling Types in .NET. Criteria For each category I want to call out Managed Unmanaged - is the API managed or unmanaged

Viewing types with Reflection-Only

It's natural for a tool to use Reflection-Only loading to load an assembly and view the types in it. For example, I used this in my pdb2xml tool. However

DatabaseConfigurationView Class in Enterprise Library Data Access Application Block - Read Database Connection Strings and Configuration

DatabaseConfigurationView Class in Enterprise Library Data Access Application Block - Read Database Connection Strings and Configuration by David Hayden

Calling printf from C# - The tale of the hidden __arglist keyword

Browsing the SSCLI can be enlighting from time to time (if not all the time). Take a look at the following function implemented in console.cs [HostProtection

Most Popular

How To Group ListView Items with ListViewGroup VB2005

Publishing Reporting Services reports to MOSS

How to bind Generic Dictionary with dropdown list

Parse Comma Delimited TextFile with Visual Basic 2005 TextFieldParser

Using the Active Directory Membership Provider with Forms Authentication in MOSS 2007

Using a parameterized SSIS package as a data source for SQL Reporting Services