2017-07-31 02:36 PM - last edited on 2022-12-06 02:03 PM by Daniel Kassai
2017-09-18 09:02 AM
Cedric wrote: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.
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.
2017-09-18 01:37 PM
Akos wrote:Thank you for your answer,Cedric wrote: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.
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.
Sorry for the late answer,
Akos
2017-09-21 06:33 PM
Cedric wrote:That usually happens when you type in the developer ID, instead of copying and pasting.
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.