So you need the Application, not the Command. Please forgive me, I misunderstood you. Personally, this feature with enabling and disabling applications in AddinManager has never worked for me. That's partly why I'm trying to create my own AddinManager right now.
namespace em_Mark
{
[Transaction(TransactionMode.Manual)]
public class MarkerCommand : IExternalCommand
{
public Result Execute(ExternalCommandData commandData, ref string message, ElementSet elements)
{
string dllPath = @"R:\em_API\MyLibrary\MyLibrary.dll";
string nameClass = "MyLibrary.MyClass";
string nameMethod = "Execute";
try
{
byte[] dllBytes = File.ReadAllBytes(dllPath);
Assembly assembly = Assembly.Load(dllBytes);
Type myClassType = assembly.GetType(nameClass);
object myClassInstance = Activator.CreateInstance(myClassType);
MethodInfo executeMethod = myClassType.GetMethod(nameMethod);
object[] parameters = { commandData, message, elements };
Result result = (Result)executeMethod.Invoke(myClassInstance, parameters);
message = (string)parameters[1];
}
catch (Exception e)
{
TaskDialog.Show( $"{nameClass}.{nameMethod}", e.Message);
return Result.Failed;
}
return Result.Succeeded;
}
}
}
This code finds the .dll file, reads bytes from it and instantly releases the file (unlike AddinManager, which simply copies the dll used to the address "User\AppData\Local\Temp\RevitAddins\" with the addition of the current time to the file name), which makes it possible to recompile the original one.the dll is right in the process of executing the program. Then it finds a class and a method in it, and calls it, and then accepts the response.
Maybe I'll make a separate post about it, in some foreseeable future.
