Dylan Phillips
12/4/2002 5:11:00 AM
Issue was solved by using "ildasm.exe" to disassemble the assembly I created
with tlbimp.exe; it reference 1.0.3300.0. I then used ildasm.exe to
disassemble an assembly I created through Visual Studio, this one referenced
mscorlib 1.0.5000.0. Then I copied the external assembly reference of
mscorlib 1.0.5000.0 and overwrote the reference 1.0.3300.0 in the other IL.
I then used "ilasm.exe" to recompile the original IL which now references
mscorlib 1.0.5000.0.
I used the following article as reference material:
MSDN Library:
.NET Development/Visual Studio .NET/Articles and Columns/General
Articles/Troubleshooting .NET Interoperability
Hope this helps anyone with a similar problem.
Dylan
"Dylan Phillips" <mykoan@bellsouth.net> wrote in message
news:Ow2jFnzmCHA.1448@TK2MSFTNGP11...
> I have both VS .NET 1.0 and 1.1 installed on my development machine. When
> running tlbimp.exe against a COM ".dll", the mscorlib.dll referenced in
the
> assembly is 1.0.3300.0. The VS .NET 1.1 managed components in the IDE
> require mscorlib.dll 1.0.5000.0.
>
> The Visual Studio explains that this is an error as it cannot contain both
> versions mscorlib.dll.
>
> Does anyone know how to point tlbimp.exe to mscorlib 1.0.5000.0?
>
> Suggestions would be appreciated.
>
> Dylan Phillips
>
>