Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!chinacat!uudell!twaddle.dell.com!jporter
From: jporter@twaddle.dell.com (Jeff Porter)
Newsgroups: comp.windows.ms.programmer
Subject: Re: Having an EXE and DLL of the same name
Message-ID: <15097@uudell.dell.com>
Date: 12 Feb 91 23:44:35 GMT
References: <7134@hsv3.UUCP>
Sender: news@uudell.dell.com
Reply-To: jporter@twaddle.dell.com (Jeff Porter)
Organization: Dell Computer Corp.
Lines: 14

In article <7134@hsv3.UUCP>, jls@hsv3.UUCP (James Seidman) writes:
|> 
|> I'm probably missing something really obvious here.  I have a program
|> which requires a DLL to go along with it.   I'd like to have them named
|> the same (e.g. XYZPROG.EXE and XYZPROG.DLL).  The problem is that when
|> I try to declare an import function from the DLL in the DEF for the EXE,
|> link complains about a "self-import," thinking the EXE is trying to import
|> from itself.
|> 

Windows only allows either a DLL or EXE with a given name.  It's a
documented feature in the SDK manuals.

Jeff Porter