Path: utzoo!attcan!telly!lethe!torsqnt!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!odi!ed
From: ed@odi.com (Ed Schwalenberg)
Newsgroups: comp.windows.ms.programmer
Subject: Re: Having an EXE and DLL of the same name
Message-ID: <1991Feb13.151814.25905@odi.com>
Date: 13 Feb 91 15:18:14 GMT
References: <7134@hsv3.UUCP> <15097@uudell.dell.com>
Organization: Object Design, Inc.
Lines: 15
In-Reply-To: jporter@twaddle.dell.com's message of 12 Feb 91 23:44:35 GMT

In article <15097@uudell.dell.com> jporter@twaddle.dell.com (Jeff Porter) writes:
  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).

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

Oh, twaddle.  (Sorry, I couldn't resist.)
Look at PBRUSH.EXE/PBRUSH.DLL in your Windows directory with EXEHDR.
The secret is that the module name of PBRUSH.EXE is actually PBRUSHX.
Develop XYZPROG.DLL and XYZPROGX.EXE, then rename the latter to XYZPROG.EXE
before execution and you're all set.