Register .NET component for use in Navision

elwin68elwin68 Member Posts: 153
edited 2006-03-28 in Navision Attain
I have made a .NET component which I want to use in Navision 4.0 SP1.
On my own computer everything is working fine.
Now I want to register the dll on an other computer.
What are the exact steps to follow?

I tried to use regsrv32, but an error occured (dllRegisterServer entry point not found).
I tried to use regasm, but an error occured (failed to load ...dll because it is no valid .NET assmebly).

On my own computer version 2 of Framework is installed. On the other computer version 1.1 of Framework is installed (the standard when installing Navision).
When using regasm of framework 2 no error occures.
When using regasm of framework 1.1 the error above occures.

What am I doing wrong? ](*,)

Answers

  • SteveOSteveO Member Posts: 164
    You need to register the assembly with regasm from .NET framework 2.0
    because your assembly was presumably written with .NET 2.0

    So the computer on which you are trying to register your assembly will have to have version 2.0 of the framework installed, because this is the version of the framework you chose to base your assembly on.
    This isn't a signature, I type this at the bottom of every message
  • elwin68elwin68 Member Posts: 153
    Thanks for your answer. It sounds logical.

    I have installed version 2 on the other computer and regasm is working now.
    When running a codeunit from within Navision, which calls the vb-functions, an error occures (Could not create an instance of the OLE control or automation server .....).

    I think I missed a step.

    I'd like to have a simple solution to make the custom dll active on other computers. It is not desirable to install Framework 2 on every computer and then register the dll.
    Does anyone has a suggestion?

    This is my first time I try to make a custom dll in vb.NET and make it work in Navision. I hope someone can explane to me how I can make it work.
  • elwin68elwin68 Member Posts: 153
    I have already found the solution to get the custom vb-dll running on an other computer manually. \:D/

    This can be made automatically by using setup project in vb and will be my next challenge.
Sign In or Register to comment.