Let's keep this on the list, so others who might be stuck in COMville can benefit as well.
> Ashish Mittal <[EMAIL PROTECTED]> wrote: > Hi, > Thanks for your response > As you mentioned that "If the DLLs you are referencing are registered, > then the VB6 compiler should be able to find them no matter where they > are on the file system, using the GUID from the project file to search > in the registry". > > Exactly this is the problem it is referring to some old registered > dll from the registry and I am creating the new dll during run time > and I > want to refer the newly created dll not the old registered dll. NAntContrib has the <comregister /> task that will unregister your old DLL and register the new one (though the VB6 compiler will register it when it compiles it. Here's what we do (bearing in mind that we have a common location for all of our common dlls). Leave out the registration steps for any DLLs that aren't registerable. - unregister any copy of the dll in the build directory - delete any copy of the dll in the build directory - unregister and delete any copy of the dll in the common dll directory - build the dll - unregister the dll in the build directory - copy the dll to the common dll directory - register the new verison in that location A bit verbose, but we're phasing out the use of COM dlls anyway, so it's not that much of a hassle, especially since it's already done. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ NAnt-users mailing list NAnt-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
