Click-Once Deployment of DLLs

25 Apr 2006 2:39 PM

Curtis

I have a class library that was created in VB.net 2003 and registered as COM
object so that Visual Foxpro 7 can access the library. At this time we have
to use an MSI installer package to install on every workstation the code
resides. Is it possible to deploy this dll with click-once and have it check
for updates at this time all I see is the ability to deploy .net EXEs with
click once. Any help or examples or ideas would be greatly appreciated.

Thanks,
Curtis

25 Apr 2006 2:52 PM

Richard K Bethell

Because you are strong signing the DLL (I'm assuming) and typing it with
guids in order to expose it to COM, and because you're consuming the DLL
with COM, you'd really be better off thinking of this the way you would have
an old VB6 DLL - if you keep the signature of the DLL exactly the same, you
might be able to replace the DLL without unregistering and reregistering it
with regasm (though you'll have to close any COM applications accessing the
thing to break the file lock) - in order to avoid DLL hell you're probably
going to want to do the file management via MSI
installations/uninstallations, rather than xcopying....

Show quoteHide quote

"Curtis" <csch***@hotmail.com> wrote in message
news:OYMKaYHaGHA.4248@TK2MSFTNGP05.phx.gbl...
>I have a class library that was created in VB.net 2003 and registered as
>COM object so that Visual Foxpro 7 can access the library. At this time we
>have to use an MSI installer package to install on every workstation the
>code resides. Is it possible to deploy this dll with click-once and have it
>check for updates at this time all I see is the ability to deploy .net EXEs
>with click once. Any help or examples or ideas would be greatly
>appreciated.
>
> Thanks,
> Curtis
>

1 May 2006 7:22 PM

Curtis

Thanks for the Help Richard
Show quoteHide quote

"Richard K Bethell" <softdev@spammingisevil.bad> wrote in message
news:OeubWfHaGHA.4916@TK2MSFTNGP04.phx.gbl...
> Because you are strong signing the DLL (I'm assuming) and typing it with
> guids in order to expose it to COM, and because you're consuming the DLL
> with COM, you'd really be better off thinking of this the way you would
> have an old VB6 DLL - if you keep the signature of the DLL exactly the
> same, you might be able to replace the DLL without unregistering and
> reregistering it with regasm (though you'll have to close any COM
> applications accessing the thing to break the file lock) - in order to
> avoid DLL hell you're probably going to want to do the file management via
> MSI installations/uninstallations, rather than xcopying....
>
> "Curtis" <csch***@hotmail.com> wrote in message
> news:OYMKaYHaGHA.4248@TK2MSFTNGP05.phx.gbl...
>>I have a class library that was created in VB.net 2003 and registered as
>>COM object so that Visual Foxpro 7 can access the library. At this time we
>>have to use an MSI installer package to install on every workstation the
>>code resides. Is it possible to deploy this dll with click-once and have
>>it check for updates at this time all I see is the ability to deploy .net
>>EXEs with click once. Any help or examples or ideas would be greatly
>>appreciated.
>>
>> Thanks,
>> Curtis
>>
>
>