Re: Size of EXE

From: Ken Halter (Ken_Halter_at_Use_Sparingly_Hotmail.com)
Date: 12/03/04 

Date: Fri, 3 Dec 2004 12:09:07 -0800

"YYZ" <d> wrote in message news:e4l$pLX2EHA.3236@TK2MSFTNGP15.phx.gbl...
>
> I think you are right. I've never taken the time myself to see if I have
> to
> reregister dlls when I compile new versions, or if copying over works
> fine.

As long as you maintain Binary Compatibility, you can just copy over the old
DLL. If you add public interfaces/classes then you'll need to re-register.
If you remove public interfaces/classes (aka Break Compatibility) then
you'll have to rebuild any exe's that use the dll, unregister the old and
register the new version.

> It's also more difficult to test because you can't do it on your
> development
> machine to make sure, because when you compile, I THINK VB automatically
> re-registers it for you. Or maybe not, but again, test on a blank
> machine.

VB does auto-register any ActiveX components you compile. That really
doesn't stop you from having several versions stored in several folders. You
can test the replacement of the dlls by unregistering the newly compiled
version and attempting to run the app. The app should complain (since the
dll it's looking for isn't registered). Then, register one of the oldies,
run the app and watch for complaints. If there are none, copy the newly
compiled version over the version you've registered and test.

> Much easier to just put it all in one big honkin' executable.

arghhh <g>

> Matt 

-- 
Ken Halter - MS-MVP-VB - http://www.vbsight.com
Please keep all discussions in the groups..
Loading