topic Re: Can't test add-ons with AddOn Management (API DevKit 18) in Archicad C++ API

[SOLVED] Can't test add-ons with AddOn Management

Anonymous — Tue, 06 Dec 2022 13:03:00 GMT

Hello,
When I try to test (on addOn Management) my addon built with Visual Studio 10, it doesn't appear in the list on AddOn Management. However, when I check with another addon found on the website, it appears on the list. In this way, I can't use it on Archicad 18.
I think there is a problem with my addon; probably something I missed...
Does someone have an idea on this problem ?
Regards.

Re: Can't test add-ons with AddOn Management (API DevKit 18)

Akos Somorjai — Mon, 18 Sep 2017 07:02:47 GMT

Cedric wrote:
Hello,
When I try to test (on addOn Management) my addon built with Visual Studio 10, it doesn't appear in the list on AddOn Management. However, when I check with another addon found on the website, it appears on the list. In this way, I can't use it on Archicad 18.
I think there is a problem with my addon; probably something I missed...
Does someone have an idea on this problem ?
Regards.

That usually means that the MDID resource is not valid. Open your add-on as a resource file in Visual Studio, and see if it contains an MDID resource at all, and the values in there are not 'dummies'. You can create a valid local ID for your add-on with your developer ID and the AddOnAdmin tool in the devkit.

Sorry for the late answer,

Akos

Re: Can't test add-ons with AddOn Management (API DevKit 18)

Anonymous — Mon, 18 Sep 2017 11:37:41 GMT

Akos wrote:
Cedric wrote:
Hello,
When I try to test (on addOn Management) my addon built with Visual Studio 10, it doesn't appear in the list on AddOn Management. However, when I check with another addon found on the website, it appears on the list. In this way, I can't use it on Archicad 18.
I think there is a problem with my addon; probably something I missed...
Does someone have an idea on this problem ?
Regards.
That usually means that the MDID resource is not valid. Open your add-on as a resource file in Visual Studio, and see if it contains an MDID resource at all, and the values in there are not 'dummies'. You can create a valid local ID for your add-on with your developer ID and the AddOnAdmin tool in the devkit.

Sorry for the late answer,

Akos

Thank you for your answer,
I get through this problem but I don't know what it was. I started the process again and it works. I just have failed when I put the keys.
Regards.

Re: Can't test add-ons with AddOn Management (API DevKit 18)

Akos Somorjai — Thu, 21 Sep 2017 16:33:21 GMT

Cedric wrote:
Thank you for your answer,
I get through this problem but I don't know what it was. I started the process again and it works. I just have failed when I put the keys.
Regards.

That usually happens when you type in the developer ID, instead of copying and pasting.

Best, Akos