To summarize the official documentation, there are 4 main types of objects: engines, app bundles, activities, and work items:Įngine refers to the actual application that will process your tasks, for example, Revit or Inventor,Īpp bundle represents a collection of files (typically plugin binaries) used to perform a specific task using one of the available engines,Īctivity is basically a task template, defining types of inputs, outputs, and the app bundle that will process them,Īnd finally, work item is an instance of a task with specific inputs and outputs (typically URLs for files to be downloaded from or uploaded to) Phase 2: Design automation pipelineīefore jumping to the individual Design Automation APIs, let's discuss some of the basic concepts used by this service. We are going to use those when setting up the Design Automation pipeline. You should now be able to build the project, generating a couple of files in the bin/Debug subfolder. These will make sure that our plugin DLL is properly signed and that it's accompanied by the corresponding addin file. Mt.exe -manifest "$(ProjectDir)InventorThumbnailAddin.X.manifest" -outputresource:"$(TargetPath)" Next, locate the Inventor addin file ( ), and replace its contents with the following XML, once again using your own GUID: Īddin for generating thumbnail images from Inventor part files.įinally, open the properties of the project, navigate to Build Events, and replace the Post-build commands with the following: call "%VS140COMNTOOLS%vsvars32" x86 Public void ExecuteCommand(int commandID) M_server = addInSiteObject.InventorServer Public void Activate(Inventor.ApplicationAddInSite addInSiteObject, bool firstTime) Public class StandardAddInServer : Inventor.ApplicationAddInServer In StandardAddInServer.cs file (which should be already created by the Visual Studio project template), change the implementation of the StandardAddInServer class (but keep the GUID that was created for you): using System Public void RunWithArguments(Document document, NameValueMap args) If (document.DocumentType = DocumentTypeEnum.kPartDocumentObject)Ĭamera camera = m_() Ĭamera.SceneObject = (document as PartDocument).ComponentDefinition Ĭamera.ViewOrientationType = ViewOrientationTypeEnum.kIsoTopRightViewOrientation Ĭamera.SaveAsBitmap(imageFilename, 256, 256, Type.Missing, Type.Missing) String imageFilename = System.IO.Path.Combine(documentFolder, "thumbnail.bmp") String documentFolder = System.IO.Path.GetDirectoryName(document.FullFileName) We're going to call it InventorThumbnailAddin:Ĭreate a new file in the project, Automation.cs, and use it to define an Automation class with the following implementation: using System With Inventor SDKs installed, open Visual Studio and create a new Autodesk Inventor AddIn project.
#Autodesk inventor plugins zip file
If you have problems with this part, or simply want to skip the creation of an Inventor plugin, here's a zip file with our plugin's source code and binaries: InventorThumbnailAddin.zip.Įdit: there's now a Visual Studio Project Template that you can use to bootstrap your Inventor plugin solution. If you prefer working with GUI, note that all the cURL examples in this article can be imported into postman HTTP client for configuring our pipeline using the new APIs Visual Studio Community Edition will suffice See Inventor docs for more details on where the SDK is available in your Inventor installation Inventor SDK and Visual Studio 2017 to build our Inventor plugin
0 kommentar(er)
