The method I use for my vb6 projects is a little different.
I will take a look at the thoughworks page to see if some
of their vb6 tools could help me. My method only builds the
.dll's once.
Binary Compatibility:
Each vb6 project has a subfolder called "compat". This
folder holds the current
On 4/26/06, Foster, Richard - PAL <[EMAIL PROTECTED]> wrote:
> Ah... Perhaps I was a bit unclear. Are you still trying to do this in
> Nant? If so, I meant in VB6!
No problem; your advice gave me enough to figure out how to fix this!
> I also forgot another step:
>
> 2a) In your VB projects, you
Oooh! Thanks for the pointer John/Rik. I hadn't seen any reference to
those scripts on the CCNet list.
I may finally have to get the legacy apps under CCNet too! (I've been
promising myself that I would for over a year now, but simply haven't
had the time to get the build scripts into a form where
On 4/26/06, John Cole <[EMAIL PROTECTED]> wrote:
> Rick,
> Take a look at
> http://confluence.public.thoughtworks.org/display/CCNETCOMM/Tools+for+VB6
>
> These are the NAnt/NAntContrib scripts we use to build our VB6 projects.
> It includes tasks to fix VBP's when class id's change and to auto-
Ah... Perhaps I was a bit unclear. Are you still trying to do this in
Nant? If so, I meant in VB6!
I also forgot another step:
2a) In your VB projects, you need to (temporarily) set the reference to
the in-IDE project, not the built version of the library.
Having two VB-built components with the
On 4/26/06, Rik Hemsley <[EMAIL PROTECTED]> wrote:
> Does anyone know of a GUID extraction tool? My google skills don't
> seem up to the job of finding one, if it exists.
I found an easy way:
In VB6, add a reference to "TypeLib Information" and use:
TLI.TypeLibInfoFromFile(Path).Guid
Rik
> Perhaps there is a built copy of AnotherProjectX.DLL somewhere on this
> system, with the correct GUID, but not of TransportX.DLL. This is
> quite possible.
I used OLE/COM object viewer to look for registered DLLs and found
that indeed there is a AnotherProjectX.DLL registered with the GUID
that
> 1) Open each of the projects (or a solution containing all the
> projects).
> 2) Set the project(s) to "project" compatibility.
I set each project to 'project' compatibility, but still got the
"Unable to set version compatible component" complaint. I adjusted my
script so that it removes the "Co
