Blog - Title

October, 2004

  • The C# Team

    Preprocess Win32 Messages through Windows Forms

    • 11 Comments
    In the unmanaged world, it was quite common to intercept Win32 messages as they were plucked off the message queue. In that rare case in which you wish to do so from a managed Windows Forms application, your first step is to build a helper class which...
  • The C# Team

    Be Mindful of the References / 'using' / Manifest Relationship

    • 9 Comments
    Given that the .NET platform encourages binary reuse of types, it is commonplace to set references to external assemblies using the Visual Studio .NET Add Reference dialog box. Many programmers (especially those of the C(++) ilk) fear that adding unnecessary...
  • The C# Team

    Activate 'Full Screen Mode' During your Source Code Editing

    • 11 Comments
    Okay, I admit this is a rather lame tip which can hardly qualify as 'insightful', however this is one of my favorite features of Visual Studio .NET (as well as previous editions of the Visual Studio product line) which many folks are (surprisingly) unaware...
  • The C# Team

    Leverage the C# Preprocessor

    • 7 Comments
    Like other languages in the C-family, C# supports a set of 'preprocessor' directives , most notably #define , #if and #endif (technically, csc.exe does not literally have a preprocessor as these symbols are resolved at the lexical analysis phase, but...
  • The C# Team

    Avoiding Type Name-Clashes using 'using'

    • 10 Comments
    You are already aware that the C# using keyword allows you to supply hints to the compiler regarding the fully qualified name of the types within a given *.cs file. However, what you may not know is that the using keyword also allows you to build aliases...
  • The C# Team

    Build 'Consistent' .NET assemblies with FxCop

    • 1 Comments
    The term 'best practices' sends chills up the spines of many people. Reason being, what is 'best' for one is 'horrible' for another. However, if you are interested in ensuring that your custom .NET assemblies are in-sync with the coding guidelines proposed...
  • The C# Team

    Simplified Interface Implementation a la VS .NET 2003

    • 2 Comments
    Another helpful feature of VS .NET 2003 has to do with the implementation of interface types. As you know, when a class or structure agrees to implement a given interface, it must implement all of the members. Assume you wish to support an interface containing...
  • The C# Team

    Simplified Event Handling a la VS .NET 2003

    • 3 Comments
    Working with events under the .NET platform requires you to be aware of a number of details. For example, if you know the name of the event you wish to handle, you must then know the name of the related delegate type. Once you know that much, you must...
  • The C# Team

    Integrate ildasm.exe into VS .NET 2002

    • 1 Comments
    VS .NET allows you to add any number of external tools to the Tools menu. One very helpful technique is to configure ildasm.exe to automatically load up the current assembly being compiled. While VS .NET 2003 sets this up automatically, VS .NET 2002 may...
  • The C# Team

    Add Custom .NET Assemblies to the Add Reference Dialog

    • 15 Comments
    As you most likely know by now, the Add References dialog of Visual Studio .NET does not list each and every assembly on your machine, does not directly map to the Global Assembly Cache and does not list your custom assemblies. Typically this limitation...
  • The C# Team

    Leverage C# Response Files at the Command Line

    • 3 Comments
    Although I'd bet most of you make use of VS .NET as opposed to the raw command line complier, csc.exe can be quite useful in a number of circumstances. However, few of us enjoy typing lengthy command line flags such as: csc /r: MyAsm.dll;MyOtherAsm...
  • The C# Team

    Be Aware of wincv.exe

    • 7 Comments
    When you install the .NET SDK / VS.NET, you are provided with numerous stand alone programming tools, one of which is named wincv.exe ( Windows Class Viewer ). Many developers are unaware of wincv.exe, as it is buried away under the C:\Program Files\Microsoft...
  • The C# Team

    Utilize the Server Explorer

    • 0 Comments
    Visual Studio .NET provides a very interesting view of the world named the Server Explorer (which can be activated from the View menu). While you may already be aware many of these items can be opened within VS .NET for editing (for example, opening a...
  • The C# Team

    Obtain Type Information on the Fly using typeof

    • 2 Comments
    All .NET assemblies contain vivid type information which describes the structure of every internal and external type (this can be verified by loading an assembly into ildasm.exe and clicking the ctrl-m keystroke). On a related note, many methods in the...
  • The C# Team

    Interacting with overloaded operators from overloaded operator challenged languages

    • 3 Comments
    Like the C++ language, C# allows you to overload operators for your custom types. For example, assume you have a structure named MyPoint which has overloaded the plus operator. If this is the case, you can 'add' two MyPoints as so: // Add two MyPoint...
Page 1 of 1 (15 items)