topic Re: AppAutoload in 2013 LoadOnCommandInvocation seems broken in .NET Forum

AppAutoload in 2013 LoadOnCommandInvocation seems broken

tyronebk — Sun, 09 Sep 2012 08:19:00 GMT

I have searched but have been unable to find anything related to this. This is not strictly a .net issue.

Is LoadOnCommandInvocation="True" broken in 2013? It used to work fine in 2012 but in 2013 all .DLL and lisp files are simply being loaded at launch?

Even the simple DOTNETTEST2 bundle (made available by the APN Dev guys last year) show the same behaviour.

Is there something I'm missing?

Here's the PackageContents.xml from the DOTNETTEST2:

<?xml version="1.0" encoding="utf-8" ?>

</Commands>

</ComponentEntry>

</Components>

</ApplicationPackage>

I searched through the now redacted SP 1 release notes and saw no mention of this problem.

Re: AppAutoload in 2013 LoadOnCommandInvocation seems broken

fenton_webb — Wed, 12 Sep 2012 15:42:52 GMT

Can you send your test bundle please?

Also, a .NET DLL that ran in 2012 won't run in 2013... The DLL needs to be built against the 2013 ObjectARX SDK because 2013 is a binary break release. You can include both 2012 and 2013 DLL's in the same bundle, but you have to separate the Components by using the RuntimeRequirements tag... e.g.

<?xml version="1.0" encoding="utf-8"?>
<ApplicationPackage SchemaVersion="1.0" Name="DOTNETTEST2" Description="DOTNETTEST2" AutodeskProduct="AutoCAD" AppVersion="1.0.0" ProductType="Application" >

<RuntimeRequirements OS="Win32|Win64" Platform="AutoCAD|AutoCAD*" SeriesMin="R18.2|R19.0" SeriesMax="R18.2|R19.0" />
<Components>

<RuntimeRequirements OS="Win32|Win64" Platform="AutoCAD|AutoCAD*" SeriesMin="R18.2" SeriesMax="R18.2" />
    <ComponentEntry AppName="DOTNETTEST2" ModuleName="./Contents/2012/AutoloaderDotNetSample2.dll" LoadOnCommandInvocation="True">
      <Commands GroupName="DevDays2010">
        <Command Local="DOTNETTEST2" Global="DOTNETTEST2" Description="A test command" />
      </Commands>
    </ComponentEntry>
</Components>
<Components>

Re: AppAutoload in 2013 LoadOnCommandInvocation seems broken

tyronebk — Fri, 14 Sep 2012 04:47:37 GMT

Hi Fenton -- thanks for your reply.

I am aware of all the versioning attributes and that coding/recompiling is necessary for 2013. I excluded all of that for brevity and simplicity. I also thought that maybe the version attributes were causing the issue so I went with the simplest plug-ins I could find, the DotNetTest bundles.

I've attached the recompiled 2013 versions of the DotNetTest bundles. These bundles both are being loaded at launch. The 2012 versions (not included) launch when expected.

I also included a sample "universal" bundle (DotNetTestsAllInOne.bundle) that supports both 2012 and 2013. Regardless, the result is the same: 2012 loads AutoloaderDotNetSample1.dll at launch and AutoloaderDotNetSample2.dll on command invocation, 2013 loads both at launch.

I reset all of my settings but that has made no difference. I have vanilla AutoCAD and Civil 3D installed and both show the same behaviour.

The bundles are being recognized properly as the Applications registry entries show (in both 2012 and 2013):

DOTNETTEST1: LOADCTRLS = 2
DOTNETTEST2: LOADCTRLS = 4

All custom plug-ins and plug-ins acquired from the Exchange store show the same behaviour. As I mentioned initially, this is not specific to DLLs as LSP/VLX/FAS files are also being loaded at launch.

Thanks for your time and any insights.

Edit: I've just installed and tested SP1.1 but the result is the same.

Re: AppAutoload in 2013 LoadOnCommandInvocation seems broken

fenton_webb — Fri, 14 Sep 2012 21:38:40 GMT

I'm just looking into it for you...

Re: AppAutoload in 2013 LoadOnCommandInvocation seems broken

fenton_webb — Mon, 24 Sep 2012 23:13:33 GMT

Just to let you know that I have reproduced the same issue on my machine and I've reported it to engineering. I'll push to get this fixed for you.

Re: AppAutoload in 2013 LoadOnCommandInvocation seems broken

tyronebk — Tue, 25 Sep 2012 14:44:02 GMT

Thanks for confirming it Fenton.

Re: AppAutoload in 2013 LoadOnCommandInvocation seems broken

StephenThomasGrace — Thu, 18 Apr 2013 15:26:46 GMT

Has there been any solution to this?

It appears to be broken in AutoCAD 2014

I can only get my apps to load with LoadOnAutoCADStartup="True"

Funny it works with AutoCAD 2013 now. Maybe SP 1.1 fixed it there?

I'm trying to get an app ready for posting to the exchange store and it would be nice to be able to follow the recommended "LoadonCommandInvocation" method.

-steve

Re: AppAutoload in 2013 LoadOnCommandInvocation seems broken

DiningPhilosopher — Thu, 18 Apr 2013 15:50:39 GMT

You might expect it to be fixed in a service pack, but these days, waiting for service packs is considered a thing of the past, and no longer acceptable, not to mention a bit of an oxymoron in the case of a vendor that seems to be into cloud-washing to the extent these folk are.

The thing that puzzles me, is how these types of glaringly-obvious bugs find their way into shipping products, and worse, survive to the next release.

Re: AppAutoload in 2013 LoadOnCommandInvocation seems broken

fenton_webb — Thu, 18 Apr 2013 16:31:40 GMT

Sorry for the trouble... Just be sure to setup the OnCommandInvocation settings for when the issue is fixed.

Re: AppAutoload in 2013 LoadOnCommandInvocation seems broken

StephenThomasGrace — Thu, 18 Apr 2013 18:26:20 GMT

So, knowing that it is an issue, do you have any expectations for when a fix will be released?

I'd rather not release my app while it throws an "Unknown Command" error.

Re: AppAutoload in 2013 LoadOnCommandInvocation seems broken

Anonymous — Tue, 05 Nov 2013 16:04:02 GMT

I'm wondering if there is any progress in this. Fenton wrote a white paper early this year (01/02/2013) in Autocad DevBlog, but didn't mention there was any issues. Is this fixed in 2014?

Re: AppAutoload in 2013 LoadOnCommandInvocation seems broken

Balaji_Ram — Fri, 08 Nov 2013 12:02:26 GMT

Hi Vincent,

Yes, the "LoadOnCommandInvocation" should work ok in AutoCAD 2014.

Regards,

Re: AppAutoload in 2013 LoadOnCommandInvocation seems broken

Anonymous — Thu, 27 Feb 2014 10:17:30 GMT

AutoCAD 2014 SP1 LoadOnCommandInvocation does not work, AutoCAD 2015 beta2 (build 497) LoadOnCommandInvocation does not work.

Re: AppAutoload in 2013 LoadOnCommandInvocation seems broken

dgorsman — Thu, 27 Feb 2014 16:59:30 GMT

It is INAPPROPRIATE to post comments on BETA-releases in this forum. You agreed to a non-disclosure agreement (NDA) in order to participate, and it should not be taken lightly.

Re: AppAutoload in 2013 LoadOnCommandInvocation seems broken

Anonymous — Fri, 28 Feb 2014 08:19:38 GMT

Apologies, I only intended to report an issue with AutoCAD 2014 SP1, please disregard my comment regarding the beta.

Re: AppAutoload in 2013 LoadOnCommandInvocation seems broken

StephenPreston — Fri, 28 Feb 2014 16:36:02 GMT

Hi osvaldest,

I have AutoCAD 2014 sp1, and LoadOnCommandInvocation seems to work fine for me. Could you attach a (simple) sample PackageContents.xml that doesn't work for you, so I can take a look. One common problem with LoadOnCommandInvocation is not specifying a group name in your CommandMethod attribute and/or not using exactly the same string in the Group parameter of the <Commands/> element.

Re: AppAutoload in 2013 LoadOnCommandInvocation seems broken

Anonymous — Fri, 28 Feb 2014 21:14:10 GMT

Hi Stephen,

Please find Hello world bundle attached, with two writeline messages of Hello World on initialise and on HW_HelloWorld command execution (source code included in contents folder). The attachment uses simple PackageContents.xml which works great on AutoCAD 2013 SP2. AutoCAD 2014 SP1's intellisense lists command, but fails to execute it (Unknown command). If I change LoadOnCommandInvocation="True" attribute with LoadOnAutoCADStartup="True", it works great.

Thank you very for looking at this issue.

PackageContents.xml content:

<?xml version="1.0" encoding="utf-8" ?>
<ApplicationPackage SchemaVersion="1.0" AppVersion="1.2.3.4"
Name="Hello World">
<CompanyDetails
Name="Hello World Engineering"
Email="support@hello.world"
/>
<Components>
<RuntimeRequirements
SupportPath="./Contents"
Platform="Civil3D"
OS="Win64"
SeriesMin="R19.0"
SeriesMax="R19.2" />

<ComponentEntry AppName="Hello_World"
ModuleName="./Contents/HelloWorldAutoLoader.dll"
LoadOnCommandInvocation="True">
<Commands GroupName="HW_Group">
<Command Local="HW_HelloWorld" Global="HW_HelloWorld" />
</Commands>
</ComponentEntry>

</Components>
</ApplicationPackage>

Re: AppAutoload in 2013 LoadOnCommandInvocation seems broken

StephenPreston — Sat, 01 Mar 2014 00:47:40 GMT

Hmm. That looks ok. Could you also paste the CommandMethod attribute for the HW_HelloWorld command, and tell me the value of your APPAUTOLOAD sysvar?

Re: AppAutoload in 2013 LoadOnCommandInvocation seems broken

Anonymous — Mon, 03 Mar 2014 10:58:59 GMT

Hi Stephen,

APPAUTOLOAD sysvar value is set to 14.

My command method attribute looks like this: [CommandMethod("HW_HelloWorld")]. Please find the testing calss bellow:

public class Class1 : IExtensionApplication
{
[CommandMethod("HW_HelloWorld")]
public void HelloWorld()
{
Application.DocumentManager.MdiActiveDocument.Editor.WriteMessage("\nHello World");
}

public void Initialize()
{
Application.DocumentManager.MdiActiveDocument.Editor.WriteMessage("\nInitialising Hello World Application");
}

public void Terminate()
{
}
}

Thanks

Re: AppAutoload in 2013 LoadOnCommandInvocation seems broken

StephenPreston — Mon, 03 Mar 2014 21:17:59 GMT

You haven't specified a Groupname in your CommandMethod attribute. This is the potential problem I mentioned in an earlier reply.

In your code, try replacing

[CommandMethod("HW_HelloWorld")]

with

[CommandMethod("HW_Group", "HW_HelloWorld", CommandFlags.Modal)]