How create installer for vba project for AutoCad

How create installer for vba project for AutoCad

taras_zelensky
Contributor Contributor
1,908 Views
4 Replies
Message 1 of 5

How create installer for vba project for AutoCad

taras_zelensky
Contributor
Contributor

Hello all

Unfortunately, I did not find information on the network about creating an installer for the VBA project, for AutoCad.
It is unclear which development environment to use to create the installer (InstallShield, Wise Installation System or others).

Безымянный.jpg

The project has a dvb extension. It contains the procedure for creating a toolbar with buttons.


How to add, with the help of the installer, to the AutoCad startup macro that creates a menu?
Thanks in advance for the answer.

Accepted solutions (1)
1,909 Views
4 Replies
  • VBA
Replies (4)
Message 2 of 5

taras_zelensky
Contributor
Contributor

The contents of the Acad.lsp file:

 

(defun S :: STARTUP ()
(command "_VBALOAD" "MyProject.dvb")
(command "_VBARUN" "MyProject.dvb! ThisDrawing.CreateToolbar")
)

 

1. The VBA plugin installer in the main AutoCad directory should find the Acad.lsp file
2. If it is not, create it. And add the above code to download.
3. If there is, open it. Check for added lines of plugin download code.

 

The path to the dvb file must be specified "C: \ Users \ name_user \ AppData \ Roaming \ Autodesk \ ApplicationPlugins \"

Message 3 of 5

taras_zelensky
Contributor
Contributor

https://adndevblog.typepad.com/autocad/2015/05/autocad-2016-trusted-paths-and-autoloader.html

In AutoCAD 2014, we introduced Trusted Locations (TRUSTEDPATHS).   “Trusted Paths” are in concept a “white list” of locations that the CAD manager can audit and maintain for add-ins and customizations loaded into AutoCAD.  AutoCAD allows signed files to be loaded from outside of this “whitelist” without SECURELOAD warnings, with the exception that AutoCAD 2016 will check if the publisher of the signed app is in the users trusted publisher certificate store.  The “best practice” is to ensure the “trusted locations” are only writable with Administrator permissions.

Applications utilizing the "autoloader" functionality within AutoCAD have the options to install to the following locations:

%APPDATA%\Autodesk\ApplicationPlugins
%ALLUSERSPROFILE%\Autodesk\ApplicationPlugins
%ProgramFiles%\Autodesk\ApplicationPlugins
%ProgramFiles(x86)%\Autodesk\ApplicationPlugins (In 64-bit OS)

In AutoCAD 2014 & 2015 - %ALLUSERSPROFILE%\Autodesk\ApplicationPlugins and %Appdata%\Autodesk\ApplicationPlugins – are by default trusted paths.

With AutoCAD 2016, only the Program files folder (C:\Program Files\Autodesk\ApplicationPlugins and C:\Program Files (x86)\Autodesk\ApplicationPlugins ) is trusted by default.
This means, when you try to load an unsigned add-in from any location outside of the "trusted locations" you will get a warning message like the one shown below. Note that in AutoCAD 2016 the user can choose to “always trust this app” – if they do, the warning will not be triggered again.
0 Likes
Message 4 of 5

Ed__Jobe
Mentor
Mentor

You don't really need an installer for a dvb or a lisp. Just copy it to a folder in the search file path. Additionally, you can create a acad.dvb with public AcadStartup method in a public module that will run on startup so you can initialize vba routines, like loading other dvb's.

Ed


Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
How to post your code.

EESignature

Message 5 of 5

taras_zelensky
Contributor
Contributor
Accepted solution

Before installing the VBA plugin, the user must read the "Publisher Privacy Policy":

https://apps.autodesk.com/en/eula

Publisher Privacy Policy

Please note there is a new field 'Publisher Privacy Policy' which has been added in the publisher workflow.
Each App must include a link to the applicable privacy policy in this field and within the App in an easily accessible manner.

The privacy policy must clearly and expressly do the following:

1. Identify and describe the data, if any, that the App collects, how that data is collected, and all uses of that data.

2. Confirm that any third party with whom an App shares that data will provide the same protection of that data as stated in the App’s privacy policy. Examples of such third parties are analytics tools, advertising networks and third-party SDKs, as well as legal affiliates of the Publisher (parent, subsidiary, related entities).

3. Explain Publisher’s data retention and deletion policies.

4. Describe how end users can revoke consent and/or request deletion of their data.

 

That's why I need an installer.