c# - Building .NET COMInterop project without first registering the COM service -


I am creating a C # UI for interacting with a COM service (.exe) The VS 2005 com project produces a valid typelist (TLB), which is referred to by the C # project. However, the VS 2005 C # project says that the service can be registered to create a C # project, even if Typelib is fully valid during testing of the open object viewer.

We will not register the service instead of the build server, if possible, the debug build can not register a COM object as a service, because it normally does debugging, and Especially the startup code is more difficult (F5 - debugging can not be started).

What should I look for to get this job done? Do I Just Need To Register TypeLib? If so, why would it be said for emphasizing the service or TLB registration to build COMInterop properly (and, is it a command line tool with VS 2005 on Win2003)?

At one time I created a C # web service that refers to the Win2003 firewall COM object, but we do not recommend it Win2000 (which is not such a thing) only by reference to the TLB file with a registration Made, so I can not understand that it should be a problem now.

You must create an interop assembly using the tool. And add the reference to this assembly in your project instead of Tipelub. In this case the building will not require a registered com server.

If you do not want to move yet another assembly ship, you can extract the interface details from the generated interop assembly and include them as source files in the project.


Comments

Popular posts from this blog

c++ - Linux and clipboard -

What is expire header and how to achive them in ASP.NET and PHP? -

sql server - How can I determine which of my SQL 2005 statistics are unused? -