Debugging in Visual Studio .NET & Understanding PE

“A powerful feature of Visual Studio .NET is its ability to debug across languages that target the common language runtime, and across execution environments. For example, if you write a Visual Basic .NET component that is called by a C# component that is in turn called by COBOL code (that targets the runtime), you can seamlessly step between languages when debugging. You can also see a single callstack that shows the different functions called in the languages you just stepped through.” Read the rest of the article at MSDN. “A good understanding of the Portable Executable (PE) file format leads to a good understanding of the operating system. If you know what’s in your DLLs and EXEs, you’ll be a more knowledgeable programmer. This article, the first of a two-part series, looks at the changes to the PE format that have occurred over the last few years, along with an overview of the format itself. After this update, the author discusses how the PE format fits into applications written for .NET, PE file sections, RVAs, the DataDirectory, and the importing of functions. An appendix includes lists of the relevant image header structures and their descriptions.” Read the rest of the article at MSDN.


  1. 2002-02-01 4:32 pm
  2. 2002-02-01 5:27 pm
  3. 2002-02-01 5:37 pm
  4. 2002-02-01 5:42 pm
  5. 2002-02-01 7:30 pm
  6. 2002-02-01 9:08 pm
  7. 2002-02-02 12:58 am
  8. 2002-02-02 1:31 am