Register it first: http://msdn.microsoft.com/en-us/library/tt0cf3sx(v=vs.100).aspx
Actually, you need to register the .tlb file with this tool, rather than .dll. you need to register the .dll file with regsvr32. Sorry for missleading.
You can see the usage:
tlbimp tlbFile [options]
the first argument is absolutely a .tlb file. So please try it again.
Call me ghost for short, Thanks
To get the better anwser, it should be a better question.Monday, March 19, 2012 9:24 AM
Regasm what? the COM dlls? They are obviously already registered since the app which uses them runs fine. AIUI, regasm registers net dlls for com use? (Just in case, I did try regasm-ing my dll and it failed with "not a valid /net assembly")
STuesday, March 27, 2012 9:42 AM
Thx very much again, Ghost
I have updated the original with a bit more info. I have been running ProcMon when trying to register the com component in vs. It looks like it is looking for the reference (and other references not related to my own com components) in the current user part of the registry but if I check the registry, there are no registrations for the com component there but only on the local machine area. I'm not quite sure what is going on since I am running VS as administrator. Other work colleagues seem to be able to run this same setup (Win7SP1,VS2010SP1 etc) and successfully reference the COM dlls. I too can reference the com dlls from a VS2010 setup on an XP vm machine I have, so it is looking to me like a corruption of some sort - but I'm not sure where and I have already tried a complete uninstall/re-install of VS.
Thx again for your time
1 eg C:\Program Files\Microsoft Visual Studio 10.0\Common7\Packages\fpeditax.dll\1Wednesday, March 28, 2012 11:50 AM