Index to the series on DLL imports and exports

Date:	July 27, 2006 / year-entry #253
Tags:	other
Orig Link:	https://blogs.msdn.microsoft.com/oldnewthing/20060727-04/?p=30333
Comments:	9
Summary:	How were DLL functions exported in 16-bit Windows? How were DLL functions imported in 16-bit Windows? How are DLL functions exported in 32-bit Windows? Exported functions that are really forwarders Rethinking the way DLL exports are resolved for 32-bit Windows Calling an imported function, the naive way How a less naive compiler calls an imported...

Comments (9)

GregM says:

July 27, 2006 at 3:45 pm

Do you have any articles (written or planned) on exporting and importing variables?

[No. -Raymond]
GregM says:

July 27, 2006 at 4:06 pm

Oh well. I always thought it would be nice to know why sometimes importing a variable works fine (all modules work on the same variable), and other times it blows up in your face (different modules get different copies of the variable). I try to avoid exporting variables now for that reason.

[Sometimes I wonder why I bother having a Suggestion Box since nobody uses it. -Raymond]
Brian says:

July 27, 2006 at 4:26 pm

Your suggestion box is actually very difficult to find, especially if you don’t know about it.

[It’s on the navigation bar, what more do you want? Do I have to include a link to the suggestion box to every article? If you have concrete suggestions on how to address this, you can post them to the suggestion box. -Raymond]
Nathan says:

July 27, 2006 at 8:07 pm

Shift the ‘Basics’ box to the top and make the font a bit larger. Does anyone actually use the calendar?

[Those elements are provided by the blog server software; the only thing I can do is add links to the bottom. -Raymond]
Nobody says:

July 27, 2006 at 10:54 pm

Sometimes I wonder why I bother having a

> Suggestion Box since nobody uses it.

Wow, I’m why! Yup, I use it.

> It’s on the navigation bar

That was before it went bar hopping. Now it’s on basics.

> If you have concrete suggestions on how to

> address this

Well, you can ask every module and get a different concrete suggestion on how to address it.
Jim Dodd says:

July 28, 2006 at 8:32 am

This reminds me of the time when our company was small (10 people, we’re over 130 now) and we all did customer support. I took a call and answered a question and the customer complained that, since this was such an important point (to him at least), it should be in the manual. I told him is WAS in the manual. He said it should be in the the table of contents and the index then. I told him it WAS in the table of contents and the index. He paused while he looked it up and then said he couldn’t see it. I pointed out to him where it was found but he wouldn’t be beat. He insisted it should have been in bold face. He had me there. But if we put everything everyone thought was important in bold face, half the manual would have been in bold face.
A programming bug says:

November 21, 2006 at 7:27 am

DLL的导出/导入机制到底是怎么实现的呢？本文通过引用大量的文章和对实际汇编代码的深入分析，理论联系实际，深入剖析了大量隐藏在背后的秘密。
wishfly says:

May 9, 2007 at 8:40 pm

透过汇编另眼看世界之DLL导出函数调用
La billeterie » Blog Archive » Creer une dll stub/proxy says:

April 6, 2009 at 2:00 pm

PingBack from http://jmdesp.free.fr/billeterie/?p=25

Comments are closed.

*DISCLAIMER: I DO NOT OWN THIS CONTENT. If you are the owner and would like it removed, please contact me. The content herein is an archived reproduction of entries from Raymond Chen's "Old New Thing" Blog (most recent link is here). It may have slight formatting modifications for consistency and to improve readability.

WHY DID I DUPLICATE THIS CONTENT HERE? Let me first say this site has never had anything to sell and has never shown ads of any kind. I have nothing monetarily to gain by duplicating content here. Because I had made my own local copy of this content throughout the years, for ease of using tools like grep, I decided to put it online after I discovered some of the original content previously and publicly available, had disappeared approximately early to mid 2019. At the same time, I present the content in an easily accessible theme-agnostic way.

The information provided by Raymond's blog is, for all practical purposes, more authoritative on Windows Development than Microsoft's own MSDN documentation and should be considered supplemental reading to that documentation. The wealth of missing details provided by this blog that Microsoft could not or did not document about Windows over the years is vital enough, many would agree an online "backup" of these details is a necessary endeavor. Specifics include:

A "redesign" after 2019 erased thousands of user's comments from previous years. As many have stated, the comments are nearly as important as the postings themselves. The archived copies of the postings contained here retain the original comments.
The blog has changed domains many times and the urls have otherwise been under constant change since 2003. Even when proper redirection has been set up for those links, redirection only works for a limited period of time. For example, all of the internal blog links that were valid in early 2019, were broken by 2020 without proper redirection.
The blog has been under constant re-design and re-theming since its inception. It is downright irritating to deal with a bogged-down site experience as the result of the latest visual themes designed for cell-phone browsers. As of this writing, it is cumbersome to navigate titles with only 10 entries per page. While it is nice that the official site has a search feature, searching using this index (with all titles on a single page) is much quicker (CTRL-F in most browsers).

<-- Back to Old New Thing Archive Index