Prev: wxMSW-2.8.9 build errors
Next: error C2039: 'Eip' : is not a member of '_CONTEXT'
From: Igor Tandetnik on 17 Dec 2008 18:15
Ketchup <ketchup(a)ketchup.com> wrote:
> "Igor Tandetnik" <itandetnik(a)mvps.org> wrote in message
> news:%233zxxQJYJHA.1324(a)TK2MSFTNGP04.phx.gbl...
>
>> Note that you can embed the assembly manifest into the assembly, but
>> you can't embed the application manifest (client.exe.manifest file
>> in the example). This one is specific to every client app.
>
> Igor, thanks again! Regarding the above, is there another way people
> create DLL files that do not require registration?

None that I know of.

> I know that I
> have used DLL files I have downloaded from the web as COM DLLs in
> VB.NET without having to register anything.

Sounds unlikely. Somehow, they got registered and you didn't notice it.
Or, they were not actually COM DLLs but regular C-API-exporting DLLs.
--
With best wishes,
Igor Tandetnik

With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925


From: Tim Roberts on 18 Dec 2008 01:02
"Ketchup" <ketchup(a)ketchup.com> wrote:
>
>Igor, thanks again! Regarding the above, is there another way people
>create DLL files that do not require registration? I know that I have used
>DLL files I have downloaded from the web as COM DLLs in VB.NET without
>having to register anything. I simply copied the entire directory with the
>program to a destination machine and it just worked. I never had to
>create a manifest file for the client application or register a DLL.

Are you absolutely sure they were COM DLLs? COM DLLs must be registered,
one way or another, but it's certainly possible to use non-COM DLLs from
VB.NET, and those don't have to be registered.
--
Tim Roberts, timr(a)probo.com
Providenza & Boekelheide, Inc.
From: Ketchup on 18 Dec 2008 12:06
Thank you everyone for your help. I now have a working COM DLL with a
working manifest. I wanted to share a utility I found that wrote the
manifest file for me. It was not easy to write it by hand. This tool
wrote the client app and the dll manifests. It's quite incredible:

http://www.codeproject.com/KB/COM/regsvr42.aspx


"Ketchup" <ketchup(a)ketchup.com> wrote in message
news:uhqnMxHYJHA.256(a)TK2MSFTNGP06.phx.gbl...
> Hi,
>
> I wrote and ATL COM Dll that I am using in VB.NET. I used ATL with
> static linking. I am not using MFC. The Dll works on my laptop where all
> the development was done. How many times have you heard that? :) On
> other machines, the Dll is not working properly, triggering an exception
> because it is not registered. While I can regsrvr32 the Dll on other
> machines, I would prefer not to do that. How do I get this Dll to just
> run from the same folder as the host application, without having to
> register it first? VB.NET does the annoying thing where it carves out the
> Dll and copies to the executable folder with an Interop. prefix. The Dll
> file it copies is much smaller then the original used as a reference.
>
> I am working in Visual Studio 2002. (I know it's buggy).
>
> Thnanks!
>


First  |  Prev  | 
Pages: 1 2
Prev: wxMSW-2.8.9 build errors
Next: error C2039: 'Eip' : is not a member of '_CONTEXT'