J
jemmaq99
Using Visual Studio .NET 2003 I've tried to add a COM reference
to a Windows Form project via the Add Reference dialog (specifically
the Active DS Type Library) but always get the error message:
"A reference to 'Active DS Type Library' could not be added. The
type library wrapper tool 'tlbimp' cannot be found on this system.
Please re-install Visual Studio."
This occurs regardless of the actual tlb or dll selected and happens
on Win2000 and XP with various flavors of SP's using Framework 1.1
SP1.
TlbImp.exe exists in the Framework SDK bin directory and can be
executed from the Visual Studio command-line tool with no
qualification.
I've chatted with other developers over the phone and they
add COM references with no problem. While seeking a solution I've
made clean installs of Win2000 and XP, reinstalled Framework from
my prerequistite disk, and reinstalled VS a number of times with
identical results.
On searching these groups I've found a couple others (over the last
couple years) who've had the same problem, but I've never seen a
solution.
MS has a KB article 883608 that discusses a scenario that generates
the same error message, but doesn't seem to apply in my case.
Any help?
Thanks,
--J.
to a Windows Form project via the Add Reference dialog (specifically
the Active DS Type Library) but always get the error message:
"A reference to 'Active DS Type Library' could not be added. The
type library wrapper tool 'tlbimp' cannot be found on this system.
Please re-install Visual Studio."
This occurs regardless of the actual tlb or dll selected and happens
on Win2000 and XP with various flavors of SP's using Framework 1.1
SP1.
TlbImp.exe exists in the Framework SDK bin directory and can be
executed from the Visual Studio command-line tool with no
qualification.
I've chatted with other developers over the phone and they
add COM references with no problem. While seeking a solution I've
made clean installs of Win2000 and XP, reinstalled Framework from
my prerequistite disk, and reinstalled VS a number of times with
identical results.
On searching these groups I've found a couple others (over the last
couple years) who've had the same problem, but I've never seen a
solution.
MS has a KB article 883608 that discusses a scenario that generates
the same error message, but doesn't seem to apply in my case.
Any help?
Thanks,
--J.