Thursday, May 27, 2010
Web Server Return Codes
Well, I don't claim to be a web guy, but I feel like I should have known the web server return codes long ago...
Monday, May 24, 2010
COM Interop
Here is a discussion on COM Interop - I don't know if this applies to my ESRI ArcObjects issues, but it clears up some issues anyway...
Revenge of the ArcObjects
OK, so the .NET assemblies that make up the ArcObjects library are just a collection of COM wrappers - so Reflector doesn't help you figure out what a method does, or how its arguments fit into the scheme of things.
Thank goodness for ESRI's lack of documentation!
Thank goodness for ESRI's lack of documentation!
Thursday, May 20, 2010
Assembly Binding
Oh, thank you Scott Hanselman, for showing me how to troubleshoot my assembly binding issues! You have saved me hours and hours of frustration!
Here's a summary:
Before Binding - what will assembly bind to? Use Reflector
During Binding - what did I try to bind to? Use Fusion Log Viewer
After Binding - What did you actually load? Use Process Explorer.
Thank you, thank you, thank you...
Here's a summary:
Before Binding - what will assembly bind to? Use Reflector
During Binding - what did I try to bind to? Use Fusion Log Viewer
After Binding - What did you actually load? Use Process Explorer.
Thank you, thank you, thank you...
Tuesday, May 11, 2010
nServiceBus, ArcObjects
Trying to get nServiceBus working in the context of an ArcObjects application, in order to send changes to the Situs layer to the AS/400 for processing.
I changed the namespace of the project, and had to re-register it using the command:
regasm /tlb:LandfileWorkspaceExtension.tlb LandfileWorkspaceExtension.dll /codebase
That made it work again...
Some other notes to think about...
Even though the main Extension assembly (LandfileWorkspaceExtension.dll) can be debugged based on the information provided during regasm registration, all the dependent assemblies had to be copied into the ArcMap directory. Otherwise, the Extension failed Initialization without any error message because ArcMap could not resolve the dependencies.
nServiceBus has to be configured in ArcMap.exe.config because ArcMap is the host process for the nServiceBus assemblies. Forgetting the config file caused "No Endpoint Configured" errors.
See the Installation section of this page for installing NServiceBus.Host.exe as a Windows Service: http://www.nservicebus.com/GenericHost.aspx
I changed the namespace of the project, and had to re-register it using the command:
regasm /tlb:LandfileWorkspaceExtension.tlb LandfileWorkspaceExtension.dll /codebase
That made it work again...
Some other notes to think about...
Even though the main Extension assembly (LandfileWorkspaceExtension.dll) can be debugged based on the information provided during regasm registration, all the dependent assemblies had to be copied into the ArcMap directory. Otherwise, the Extension failed Initialization without any error message because ArcMap could not resolve the dependencies.
nServiceBus has to be configured in ArcMap.exe.config because ArcMap is the host process for the nServiceBus assemblies. Forgetting the config file caused "No Endpoint Configured" errors.
See the Installation section of this page for installing NServiceBus.Host.exe as a Windows Service: http://www.nservicebus.com/GenericHost.aspx
Subscribe to:
Posts (Atom)