Get Addin info Pro 3.0

[AbelPerez]

At Pro 2.9 there was this great helper class that got info for your own addin. https://github.com/Esri/arcgis-pro-sdk-community-samples/tree/master/Content/AddInInfoManager

It bombs at 3.0 and I have not been able to locate an alternative API or other form of getting the info programmatically.

I tweaked the function and it turns out the the code is returning zero guid attributes:

        public static string GetAddInGuid()
        {
            // get the GUID that identifies the current add-in
            Assembly exAssembly = Assembly.GetExecutingAssembly();
            //GuidAttribute gAttribute = (GuidAttribute)exAssembly.GetCustomAttributes(typeof(GuidAttribute), true)[0];
            object[] custAtts = exAssembly.GetCustomAttributes(typeof(GuidAttribute), true);
            if (custAtts.Length == 0)
            {
                throw new Exception("No custom attributes.");
            }
            GuidAttribute gAttribute = (GuidAttribute)custAtts[0];

            // guid={903288ab-2c9c-4e49-8a3d-0321f68425c1}
            return string.Format("{{{0}}}", gAttribute.Value);
        }

Anyone know an alternative to programmatically get info for your own addin or just the GUID?

[StephenRhea]

Haven't tried this with 3.0, but for 2.9 you need to pass false to GetCustomAttributes instead of true.

// ...
var idAttribute = Assembly.GetExecutingAssembly().GetCustomAttributes(false).OfType<GuidAttribute>().FirstOrDefault();
if (idAttribute == null) return string.Empty;

var id = idAttribute.Value;
if (!Guid.TryParse(id, out var guid)) return string.Empty;
// ...

[AbelPerez]

I looked up the documentation and it seems that parameter for isInherit is required in the call but ultimately ignored in GetCustomAttributes .

[AbelPerez]

So tried your code and I'm getting a null on line 3. I also tried just the plain jane GetCustomAttributes() and that also returns zero elements.

[Wolf]

@AbelPerez , it appears that the AddinInfoManager sample was missing when we published the 3.0 community samples.  Sorry about that, but i added a 3.0 version of the sample and it appeared to work for me.  arcgis-pro-sdk-community-samples/Content/AddInInfoManager at master · Esri/arcgis-pro-sdk-community-...

[AbelPerez]

@Wolf that is still a no-go for me. The line where it crashes is same as before

var attribute = (GuidAttribute)assembly.GetCustomAttributes(typeof(GuidAttribute), true)[0];

When I run string guidStr = AddIn.GetAddInId(); it seems that the function GetCustomAttributes returns an empty collection.

Rather odd since I started this project from scratch and used the guide here https://developers.arcgis.com/documentation/arcgis-add-ins-and-automation/arcgis-pro/tutorials/build.... I did however go to the Project Properties and change some stuff there. Mainly default namespace and assembly version. Mainly in the Package section.

[GKmieliauskas]

Hi,

Have you tried GetConfigDamlAddInInfo method from @Wolf suggested sample? Returning AddIn class has Id property and it must contain Guid you are looking. It works on 2.9

[AbelPerez]

Yes I did and it works IF you know the file path of the addin. To know the path of the Addin you need the guid. So to get the guid, you need the guid.

// 1. get the filename of this .esriAddinX file
var fileName = AddIn.GetAddInId();
// 2. get the config.daml content from the esriAddinX file
var versionTuple = AddIn.GetConfigDamlAddInInfo(fileName);
MessageBox.Show($@"Version: {versionTuple.Version} desktopVersion: {versionTuple.DesktopVersion} Id: {Module1.Id}");

But again this fails for me on line 2.

[AbelPerez]

Ok this is very odd. I thought I had changed something that broke it. But I just created a brand new Addin with the VS template, added a button, added the Addin and Extensions classes. It still bombs at the same line.

My guess is that a project migration from Framework to Core keeps some properties while a brand new project based on Core doesn't have them. Idk.

[StephenRhea_NV5]

I was wondering that as well. It seems like the way the Config.daml attributes are written to the assembly is different between .NET Framework 4.8 and .NET 6, assuming your daml file is the same in both, of course.