Edit Question - KnowledgeHub

Title Body

I have some .NET code I use from VB6 code. I have always developed this on an XP machine by creating a VB6.exe.manifest file that listed the dependent .NET assemblies. For example, say my 2 .NET assemblies are Some.Assembly.A.dll and Some.Assembly.B.dll, here is what VB6.EXE.manifest looks like (I use version=1.1.0.0 below because that is the version I set on the .NET AssemblyVersion in AssemblyInfo.cs): <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0"> <assemblyIdentity type = "win32" name = "client" version = "1.1.0.0" /> <dependency> <dependentAssembly> <assemblyIdentity type="win32" name="Some.Assembly.A" version="1.1.0.0" /> </dependentAssembly> </dependency> <dependency> <dependentAssembly> <assemblyIdentity type="win32" name="Some.Assembly.B" version="1.1.0.0" /> </dependentAssembly> </dependency> </assembly> Then, along with the DLLs in the same directory, I have the assemblies and their own manifest files. Here is an example "Some.Assembly.A.dll.manifest": <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0"> <assemblyIdentity type="win32" name="Some.Assembly.A" version="1.1.0.0" /> <clrClass clsid="{F1234567-1234-1234-1234-123456789012}" progid="Some.Assembly.A.Class1" threadingModel="Both" name="Some.Assembly.A.Class1" > </clrClass> <file name = "Some.Assembly.A.dll" /> </assembly> I also run tlbexp on referenced DLLs to create TLB files, and th

Tags (comma-separated) Cancel