COM and .NET - Links to documents and tutorials: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 8: | Line 8: | ||
===Merge all dependencies into one .NET COM component=== | ===Merge all dependencies into one .NET COM component=== | ||
* [http://research.microsoft.com/en-us/people/mbarnett/ilmerge.aspx ILMerge] | * [http://research.microsoft.com/en-us/people/mbarnett/ilmerge.aspx ILMerge] | ||
* [http://www.microsoft.com/downloads/details.aspx?FamilyID=22914587-b4ad-4eae-87cf-b14ae6a939b0&displaylang=en ILMerge download] | |||
* [http://www.codeproject.com/KB/dotnet/mergingassemblies.aspx Merging .NET assemblies using ILMerge] | * [http://www.codeproject.com/KB/dotnet/mergingassemblies.aspx Merging .NET assemblies using ILMerge] | ||
==General links about COM how it works and how to register components== | ==General links about COM how it works and how to register components== | ||
* [http://msdn.microsoft.com/en-us/library/ms862119.aspx COM and DCOM Registry Settings for CE 5.0] | * [http://msdn.microsoft.com/en-us/library/ms862119.aspx COM and DCOM Registry Settings for CE 5.0] | ||
Revision as of 12:31, 18 February 2009
<google>ENGELSK</google>
Making C# .NET COM Servers
- Exposing .NET Components to COM - A method of calling .NET functions from a COM enabled non .NET environment through a COM callable wrapper
- Building COM Servers in .NET - Learn the fundamental principles of building COM DLL and EXE Servers using a .NET language
- Build and Deploy a .NET COM Assembly
Merge all dependencies into one .NET COM component
General links about COM how it works and how to register components
Component Object Model (General)
- DCOM Architecture
- Creating and Registering COM Components with LocalService
- Inside Distributed COM: Type Libraries and Language Integration
Trouble shooting
If it won't work and you get strange errors like
- CreateObject (-2146233079 automation error).
- 80010002 "Call was canceled by the message filter"
- 80131522
Try putting try/catch handlers in your .NET code (especially the constructor) with tracing...
Use Trace.WriteLine(e); and Sysinternals Dbgview.exe to trace what is happening