I need to write a dll in C#, usable by a "old" Win32 application.
What would be the best / secondbest approach to this?
View Complete Post
I am having problems with a user control. I want my solution to have a separate project for holding my user controls.
The main project can get a reference to this user control project and can import this user control dll into my main project.
Thanks in advance,
In this month's installment, learn how to achieve the most important outcome of all UI design: ensuring that your software is useful, useable, and desirable.
Dr. Charles B. Kreitzberg and Ambrose Little
MSDN Magazine May 2009
This month Paul DiLascia discusses how to find windows with GetLastChild and outputting HTML with a C++ procedure equivalent to document.write.
MSDN Magazine August 2003
MSDN Magazine July 2003
The Win32 Portable Executable File Format (PE) was designed to be a standard executable format for use on all versions of the operating systems on all supported processors. Since its introduction, the PE format has undergone incremental changes, and the introduction of 64-bit Windows has required a few more. Part 1 of this series presented an overview and covered RVAs, the data directory, and the headers. This month in Part 2 the various sections of the executable are explored. The discussion includes the exports section, export forwarding, binding, and delayloading. The debug directory, thread local storage, and the resources sections are also covered.
MSDN Magazine March 2002
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.
MSDN Magazine February 2002
Getting global cursor information is useful when developing software that drives or gathers information about other UI-based applications, including information about a remote machine. This article describes a way to programmatically identify the current cursor's ID and bitmap at any point in time. The first technique described is based on polling for information and shows how to get the handle of the current global cursor. This handle will then allow you to get information about the cursor. You can also monitor WinEvents for changes to the global cursor.
MSDN Magazine October 2001
MSDN Magazine July 2000
MSDN Magazine April 2000