Does ANYONE have any insight on this problem? Please... I thought about setting project specific variables that have a name equal to the reference name and a value of the dll name. That could serve as a mapping mechanism but it doesn't seem flexible or generic enough to be reused throughout an organization.
Thoughts? Anyone? Beuller? Beuller?
Evan A. Bonnett
Reynolds and Reynolds, IT
-----Original Message-----
From: Bonnett, Evan A
Sent: Wednesday, August 11, 2004 1:42 PM
To: Nant-Users (E-mail)
Subject: XSLT Generated Build File with COM references
I am strong naming my assemblies now. What is the process to deal with COM and ActiveX components? I am running the csproj file through an XSLT to generate the Nant build file. Does anyone have a step by step on when to do what with these components?
One problem I am running into is that the actual dll file name is not what the attribute name is in the csproj file. Here is an example:
<Reference
Name = "SHDocVw"
Guid = "{EAB22AC0-30C1-11CF-A7EB-0000C05BAE0B}"
VersionMajor = "1"
VersionMinor = "1"
Lcid = "0"
WrapperTool = "tlbimp"
/>
<Reference
Name = "AxSHDocVw"
Guid = "{EAB22AC0-30C1-11CF-A7EB-0000C05BAE0B}"
VersionMajor = "1"
VersionMinor = "1"
Lcid = "0"
WrapperTool = "aximp"
/>
But the actual dll names are AxInterop.SHDocVw.dll and Interop.SHDocVw.dll. Anyone have a simple way to map the names? Also, how do you resolve the location of these dll's? I am having trouble pulling these into the bin folder when I build. Is there a very flexible and generic way to resolve the locations based on the GUID? I am looking for a solution that can be reused throughout the organization so it can't be project specific.
Thanks a bunch,
Evan A. Bonnett
Reynolds and Reynolds, IT
