hi folks,
i'm struggling with an .net activeX i try to use in ms axapta 2009.
using this component on my local machine where it was compiled, it's working quite fine.
it can be added as activeX element on a form, the methods and events are listed in the axapta-activeX-explorer and i can interact with it without any problems.
but trying to distribute the dll to other clients isn't working as intended.
the registration of the dll via regasm /codebase /tlb works properly - getting the message, registration was successful.
the component is also listed when selecting an activeX-element to add in ax, but neither functions nor properties are listed. and launching the form results in an errormessage - activeX component CLSID ... not found on system, not installed. the classID is indeed the one, defined in .net.
strange things happen, having a look on the task-manager. the activeX-component itself is just a wrapper to interact with a com-application. when launching the ax-form with the not working and _not_installed_!! activeX-thing, the taskmanager shows a new process of the com-application, which is instanciated by the activeX :/
things i tried:
using different versions of regasm, eg \Windows\Microsoft.NET\Framework\v2.0.50727 ;
C:\Windows\Microsoft.NET\Framework64\v2.0.50727
using new GUIDs in .net, prior removing the old ones from the registry
compiling, using different versions of the .net framework
doing registration via regasm, regasm /codebase, regasm /codebase /tlb, using a visual-studio-setup
running registration via command-line as administrator
running setup as administrator
running even ax as administrator on client-machine
moving dll to a different folder followed by new registration ( windows/system32; ax/client/bin )
installing to GAC ( gacutil /i )
different project-options in visual studio ( COM-Visibility; register for COM-Interop; different targetPlatform )
hoped for the fact, that compiling in visual studio with register for COM-Interop option enabled does something more than just the regasm-registration, i used a registry-monitor-microsoft-tool for logging the registry-activity which happend during compilation.
using these logs to create all registry-entries on the target-client in addition didn't work either.
any hints or help would be so much appreciated!
this thing is blocking me for days now :(
