AutoLoader Creator of AutoCAD .NET Addin Wizard (AcadNetAddinWizard)

The build #0.7.0.0 of AutoCAD .Net Addin Wizard (AcadNetAddinWizard) has been rolled out and provided a few new features. The AutoLoader Creator item wizard is one of them.

 
It can help create the AutoCAD AutoLoader (AppPlugins) files automatically for the current Visual Studio AutoCAD .NET project including application information and command definitions both global or local without any edit or just a few.

 
Here is the Components Collection window.

 
The Commands (Command Group) window may look like:

 
The Command window may look like:

 
If the above options are chosen, the resultant AutoLoader PackageContentsX.xml file may look like the following:

<?xml version="1.0" encoding="utf-8"?>
<ApplicationPackage xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" HelpFile="./Contents/UsersGuide.chm" OnlineDocumentation="spiderinnet1.typepad.com" Name="AcadNetAddinCS4" Description="" Icon="./Resources/app.ico" Author="Spiderinnet1">
  <CompanyDetails Name="NSS" Url="spiderinnet1.typepad.com" Email="[email protected]" />
  <Components>
    <RuntimeRequirements OS="Win64" Platform="AutoCAD" SeriesMin="R18.0" SeriesMax="R18.2" />
    <ComponentEntry ModuleName="C:\Temp\AcadNetAddinCS4\bin\Debug\AcadNetAddinCS4.dll" LoadOnAutoCADStartup="true" LoadOnCommandInvocation="false" AppDescription="" AppName="AcadNetAddinCS4" AppType=".NET">
      <Commands GroupName="">
        <Command Global="RootCommand1" />
      </Commands>
      <Commands GroupName="CmdGroup1">
        <Command Local="null" Global="Command1" />
      </Commands>
    </ComponentEntry>
  </Components>
</ApplicationPackage>
 
The better part is that the AutoLoader PackageContentsX.xml file will be added into the current Visual Studio project as contents. The file can be put into the right AutoLoader proper registration folder so that the .NET assembly can be loaded as needed for debugging purpose in the development environment or can be embedded into a setup or installer project to serve for the purpose of the .Net assembly deployment and auto-load in the end user environment.

The leading edge AutoCAD .NET Addin Wizard (AcadNetAddinWizard) provides various project wizards, item wizards, coders to help program AutoCAD .NET addins.

Comments

[JeffH]

Thanks again!!!!

[Spiderinnet1]

Jeff, you are welcome.

[Sebastian Mery]

Hi,
is there any source of information if the wizard does not show in VS2010?

[Spiderinnet1]

Sebastian, may we know details of the behavior? We'd like to look into it.

[Alberto T. (2aCAD)]

By adding "AutoLoader Creator" I get this error:

"The language specified is not compatible with any of installed packages"

And I canceled the inclusion of this component.

Visual Studio 2010 in Spanish.

*********************************************************

Al añadir "AutoLoader Creator" recibo este error:

"El idioma especificado no es compatible con ninguno de los paquetes instalados"

Y me anula la inserción de este componente.

Visual Studio 2010 en Español.

[Spiderinnet1]

Alberto T. (2aCAD), was it a C# or VB.NET project? Was the project compiling and building well? Which build of AcadNetAddinWizard was it?

The information is necessary for our trouble shooting the issue. By the way, the Spanish Visual Studio should not matter.

[Alberto T. (2aCAD)]

I'm developing in VB.NET. The project compiles without errors (Net Framework 4)

Windows 7 Professional x64
8 Gb RAM
VS2010

[Spiderinnet1]

Alberto T., thanks for the info. Tried creating a VB.NET project from scratch with AutoCAD 2014 specified and using AutoLoader Creator for it. Succeeded in creating the autoloader package into the project.

We used the latest AcadNetAddinWizard with build #0.9.8.1. Could you check which version are you using? The version info can be found from the About button of either AutoCAD .NET Addin Coder or AutoCAD .NET Addin Widget.

[Alberto T. (2aCAD)]

Yes. The version is #0.9.8.1

[Spiderinnet1]

Alberto T, thanks again for the info. Then there might be something to do with the autoloader package content and the language of the Visual Studio or even Windows. Currently, we don't have a Spanish Visual Studio installed or Windows deployed, but we are going to find some different from English and try the AutoLoader Creator there. Meanwhile, if anybody else experienced similar problems with it, please feel free to jump in.