The issue is versioning and other resource info in an automated environment. Currently our build system does use tlbimp, then builds another binary containing the file version/company name/product name (intended for the interop assembly), and then copies that resource block into the interop assembly so it has the required attributes. It would be more convenient if we could generate C# source (instead of an assembly) and just put the generated cs file into a standard build project combined with an existing assemblyinfo.cs that we already use for standard projects. If tlbimp had options to add file version, assembly version, company name, product name, trademarks then we wouldn't have the issue. There are legal and technical reasons for these to be in any code we ship.
The type libraries are generated by Midl. Phil Wilson -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of J. Merrill Sent: Tuesday, March 20, 2007 9:26 PM To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM Subject: Re: [ADVANCED-DOTNET] TypeLibrary to Source Why do you need source? Doesn't .Net's command-line program tlbimp.exe (that builds an actual interop assembly) do what you need? If it doesn't, you could always use Reflector to take the resulting assembly and get back to source from that. At 02:10 PM 3/20/2007, Wilson, Phil wrote >Is anyone aware of a tool that takes a type library and builds C# >source for the interop assembly? I know of Aurigma's ComToNet (now >free), but I'm hoping to find source for the tool also. > >Thanks > >Phil Wilson J. Merrill / Analytical Software Corp =================================== This list is hosted by DevelopMentor(r) http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
