HELP - how to reference 2 different versions of the SAME DLL in a VS.NET 2005 Windows App project??

[mark_vogt]

Greetings all,

Here's an interesting problem that (oddly) has never happened to me
before:
======================================================
A. I just purchased 2 different controls from the same 3rd party
developer.

B. Each of the controls requires adding a reference to a base class
DLL called
KineticaRT.Controls.DLL.

C. Control #1 appears to demand only version 1.2.0.0 of this base
DLL;

D. Control #2 appear to demand only version 1.00.2848.5685 of this
base DLL;

E. When I add (in VS.NET2005) a reference to v1.2.0.0 of the DLL, I
get no problems for Control #1, but Control #2 still demands I "add a
reference" for v1.00.2848.5685

{here's the challenge...}

F. When I add a reference to v1.00.2848.5685 of the DLL, I get the
error message that "An assembly with that name has already been added
to your project".

:-|

Can anyone provide with any insights on how I can reference BOTH these
versions of the SAME DLL in my project, in so doing make BOTH the
controls function, and get my project to build?

TIA,
- Mark

 

[Mr. Arnold]

Can anyone provide with any insights on how I can reference BOTH these
versions of the SAME DLL in my project, in so doing make BOTH the
controls function, and get my project to build?

I don't think you're going to get a solution for that problem. You're going
to have to use one or the other. But it remains to be seen.

 

[rowe_newsgroups]

Greetings all,

Here's an interesting problem that (oddly) has never happened to me
before:
======================================================
A. I just purchased 2 different controls from the same 3rd party
developer.

B. Each of the controls requires adding a reference to a base class
DLL called
KineticaRT.Controls.DLL.

C. Control #1 appears to demand only version 1.2.0.0 of this base
DLL;

D. Control #2 appear to demand only version 1.00.2848.5685 of this
base DLL;

E. When I add (in VS.NET2005) a reference to v1.2.0.0 of the DLL, I
get no problems for Control #1, but Control #2 still demands I "add a
reference" for v1.00.2848.5685

{here's the challenge...}

F. When I add a reference to v1.00.2848.5685 of the DLL, I get the
error message that "An assembly with that name has already been added
to your project".

:-|

Can anyone provide with any insights on how I can reference BOTH these
versions of the SAME DLL in my project, in so doing make BOTH the
controls function, and get my project to build?

TIA,
- Mark

Can you rename the dll before adding it to your project, making a
MyDll1.dll and MyDll2.dll? Then when you do the import you can specify
an alias for the namespace inorder to seperate the two versions.

Also, have you contacted the vendor on this? Most vendors have some
sort of support system.

Thanks,

Seth Rowe

 

[Herfried K. Wagner [MVP]]

Can you rename the dll before adding it to your project, making a
MyDll1.dll and MyDll2.dll? Then when you do the import you can specify
an alias for the namespace inorder to seperate the two versions.

Did you test that? Renaming the DLL won't change the namespace names in the
DLL.

 

[rowe_newsgroups]

Did you test that? Renaming the DLL won't change the namespace names in the
DLL.

Won't the import alias do that? I don't have VS handy right now to
check.

Thanks,

Seth Rowe

 

[Rory Becker]

Won't the import alias do that? I don't have VS handy right now to
check.

Which of the 2 duplicate namespaces do you expect to be aliased.

You cannot specify. This should not work?

But I'm going to try anyway as I'm interested now

 

[Herfried K. Wagner [MVP]]

Won't the import alias do that? I don't have VS handy right now to
check.

I am not sure what you mean with "import alias", but you can specify an
alias for another /namespace/, not DLL.

 

[rowe_newsgroups]

Which of the 2 duplicate namespaces do you expect to be aliased.

You cannot specify. This should not work?

But I'm going to try anyway as I'm interested now

Ah, good point. Like I said I didn't have a way to check it out - but
I figured I would share just in case it might help the OP.

Thanks,

Seth Rowe