After a bit more searching it looks like the easiest thing to do may be to create a managed wrapper using Managed C++. The install method was wrapped here [1], but I want an enumeration of the assemblied and then the query info on each.

A knowledge base article [2] does document the interface for [3]. The code at the bottom of the article can be copied and pasted to a fusion.idl file. tlbimp.exe can be used to wrap a COM component in .NET given the type library. No type library ships with the fusion.dll, but shouldn't we be able to create one from fusion.idl? It tried this, but can't find the fusion.tbl that I thought it would create:

D:\tmp>midl fusion.idl /tlb fusion.tlb
Microsoft (R) 32b/64b MIDL Compiler Version 7.00.0500
Copyright (c) Microsoft Corporation 1991-2006. All rights reserved.
Processing .\fusion.idl
fusion.idl
Processing C:\Program Files\Microsoft Visual Studio\VC98\include\objidl.idl
objidl.idl
Processing C:\Program Files\Microsoft Visual Studio\VC98\include\unknwn.idl
unknwn.idl
Processing C:\Program Files\Microsoft Visual Studio\VC98\include\wtypes.idl
wtypes.idl

D:\tmp>dir fusion*
Volume in drive D is BACKUP
Volume Serial Number is 2C9E-58FB

Directory of D:\tmp

06/18/2008 07:09 PM 31,304 fusion.h
06/18/2008 06:50 PM 14,205 fusion.idl
06/18/2008 07:09 PM 2,291 fusion_i.c
06/18/2008 07:09 PM 6,084 fusion_p.c
4 File(s) 53,884 bytes

Isn't that supposed to create a fusion.tlb that I can use with tlbimp.exe? Why did it create fusion.h, fusion_i.c, and fusion_p.c? Confused.

[1] [link:www.codeguru.com]
[2] [link:support.microsoft.com]
[3] C:\WINNT\Microsoft.NET\Framework\v2.0.50727\fusion.dll

cheers,
Cameron

By on 6/18/2008 7:10 PM ()

will this help?

[link:blogs.msdn.com]

//Huusom

By on 6/18/2008 11:59 PM ()
IntelliFactory Offices Copyright (c) 2011-2012 IntelliFactory. All rights reserved.
Home | Products | Consulting | Trainings | Blogs | Jobs | Contact Us | Terms of Use | Privacy Policy | Cookie Policy
Built with WebSharper