Revit SPF Organizer 2022 has been released. Now it supports Parameter Types and Family Categories of latest Revit versions (2022, 2021, and 2020) besides old ones such as 2019, 2018, 2017, 2016, 2015 and 2014. It supports fourteen languages, English (United States), español (España, alfabetización internacional), Deutsch (Deutschland), français (France), italiano (Italia), 中文(简体), 中文(繁體), 日本語 (日本), 한국어(대한민국), русский (Россия), čeština (Česko), polski (Polska), português (Brasil), and English (United Kingdom). All features have also been enhanced.
InventorNetAddinWizard
Inventor .NET Addin Wizards, Coders and Widgets
04/22/2022
08/21/2018
Revit|AutoCAD|Inventor|Navisworks .NET Addin Wizards 2017 have been released!
Revit|AutoCAD|Inventor|Navisworks .NET Addin Wizards 2017 have been released! They support Visual Studio 2017 now. They support the latest three versions (2019, 2018 and 2017) along with many old ones of related products, flavors and verticals of Revit|AutoCAD|Inventor|Navisworks. Many features have also been enhanced to adopt to the new versions and Visual Studio 2017.
07/17/2018
Inventor .NET Addin Wizards 2015 Has Been Updated!
Inventor .NET Addin Wizards 2015 Has Been Updated!
The latest build supports the latest three versions (2019, 2018 and 2017) of Inventor besides all those already supported old versions such as 2016, 2015, 2014, 2013, 2012, 2011 and 2010. Many features have also been enhanced. The best of all, it is still free to update!!!
It can be free downloaded below.
===============================================================================
Feature Index:
- Introduction
- Installation
- INAW2015.vsix
- Toolbars and UIs
- Project Wizards
- Item Wizards
- Coders
- Widgets
- Download More
Use Tips:
- Please Run the MSI Installer as Administrator.
- Please start Visual Studio As Administrator.
- In case the toolbars of Inventor .NET Addin Wizard 2015 still don't show up in any editions of Visual Studio 2015/2013/2012, please run the INAW2015.vsix file directly from the installation folder, which is by default as "C:\Program Files (x86)\InventorNetAddinWizard2015\".
- If the operating system is Windows 10, please following the steps as listed on VSIX Installations on Windows 10 to run the INAW2015.vsix.
- In case any authorization code cannot be properly written into the system, please start Visual Studio as Administrator and try again.
- It is strongly recommended to always start Visual Studio as Administrator.
- In case wizard project creation is intercepted by some extension such as NuGet accidentally thus some weird behavior appears such as .NET Framework being targeted as Universal Windows or something like that in the resultant project, please uninstall/disable the extension and try the project wizard again.
- In case of some other issues or comments, please feel free to contact us at [email protected].
08/30/2016
Revit Parameter Organizer 2016
In case readers also use Revit, the tool must be helpful.
Revit Parameter Organizer 2016 is an addin for Revit. It works with version 2016, 2015, 2014, 2013 and 2012 (both x64 and x86, all flavors such as Revit Architecture, Revit Structure, Revit MEP, Revit, and various Bundles).
It helps organize all kinds of Revit parameters including shared, family, project and built-in in many different and easy ways. It can help View, Edit, Remove, Add, Change, Replace, Sort, Lock/Unlock, Examine, Load, Convert, Transport, Save, Export, Import various parameters and more in either single mode or batch mode. It can operate on Revit models and files in many different forms such as opened models (of project/family/template, current or not, single or multiple), families in opened project models, opened families themselves, and all Revit files (.RVT/.RFA/.RFT/.RTE) on drive (in a single folder or many different ones, nested or not, or simply scattered around as separate files). Many options are provided to better conrol the processes either in single mode or batch.
07/13/2016
VSIX Installations on Windows 10
If still no toolbars appear in Visual Studio 2013 or 2015 after InventorNetAddinWizardPro is properly installed, MSI is run as Administrator, and tips are followed, as published before:
Feature Index of Inventor .NET Addin Wizard 2015
there should be a problem with the UAC of Windows itself especially version 10. Most likely, the VSIXInstaller.exe prevents the INAW2015.vsix and any other VSIX files (Visual Studio Extensions) from running properly, by default.
The standard double click operation over a VSIX file in the File Explorer is not installing ANY Visual Studio 2015 or 2013 extensions on Windows 10. The Visual Studio 2015 and 2013 options simply would not show up in the VSIX installation dialog, which is weird. The VSIXInstaller.exe seemed to require the administrative permissions, but was not possible to make through "install as administrator" or similar anymore on Windows 10. Not sure why they changed the behavior and made people's life a bit harder than before.
The only way to install the VSIX extensions properly is to execute the VSIXInstaller.exe as administrator and pass the VSIX file as a parameter as follows:
- Open a Command Prompt window as Administrator, better from the Visual Studio Tools shot-cut
- Go to the Common\IDE folder of the Visual Studio 2015/2013 installation, such as:
CD "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE" - Execute the VSIX installer and pass the VSIX file as a parameter, such as:
VSIXInstaller.exe "C:\Program Files (x86)\InventorNetAddinWizardPRO\INAW2015.vsix"
03/24/2016
Brand New Look of Web Site and Promoted Promotion Plan
Our web site has been totally redesigned.
Besides the totally different graphics design and web site structure, a shopping cart has been added. On the same page, software products can be downloaded and useful web pages can be launched as well.
In addition, the existing promotion plan has been promoted. That is, the Revit Parameter Organizer 2016 and the Revit Shared Parameter File Editor 2016 will have prices cut half directly by the end of March 2016, rather than the initial plan, half price rebate, as can be found out from the Shopping Cart page.
03/10/2016
if( sth.IsChecked ) or if (sth.IsChecked == true) or if (true == sth.IsChecked) in C#
Spotted an old post on web about using C# in AutoCAD .NET programming. It solely focused on a C# coding style there regarding condition checking in the 'if' statement.
It mentioned a few different coding styles about 'if' this or 'if' that, just as people discussed and favored else where, such as on the SO. It is not a bad idea at all to raise the concern and discuss about it, since in fact it's only a personal preference and nothing really correct or wrong, but the bad thing was that the author obviously laughed at those people who coded or will keep coding this way, or strongly against it:
if( sth.IsChecked == true)
Anything wrong with this? Is it really much worse that the following way that the guy looked favored so?
if( sth.IsChecked )
Compiling faster? Running faster? Less typing? More concise? More consistent? More readable maybe?
Even if all so, not that important, isn't it? Needless to say, not quite so!
If he ever had coded in WPF and the 'sth' were a WPF CheckBox, he would have known which one was the only right way to go. He seemed to have some C/C++ coding experience though, as he mentioned another coding style:
if( true == sth.IsChecked )
That might be so good a skill to be learned hard, it's not really something worth of mentioning from those people's humble point of view who coded with so many different languages many years.
Let's focus on the first two coding styles then. Once again, nothing wrong with either. The first one is becoming more and more adaptable nowadays, however, at least in the WPF world or somewhere else the nullable boolean is widely used. In addition, it would be easier for code migrations from C# to VB.NET for example. If that is a bit more concern than saving a few letter typing, the following might just look better:
if( sth.IsChecked.ToString().Equals(Boolean.TrueString))
Many people like the author there may just laugh at the above code, but the point is many looking weird things have their exact reasons (known or not to some people) to be there!
Think about it another way. Which one is better or all good it depends, more portable, or more consistent with the true comparison in the following false comparison sentences, or is the right way to go in as many as possible circumstances?
if( !sth.IsChecked )
if (sth.IsChecked == false)
if (false == sth.IsChecked)
02/26/2016
Uninstall/Install InventorNetAddinWizardPro and Deploy INAW2015.vsix From Command Line or in BAT File
Just in case a new build of InventorNetAddinWizardPro needs to be installed or because of some reason, the same build needs to be uninstalled and reinstalled, a batch file (.BAT) might be helpful. And better, if silent uninstallations or installations could be supported.
At least, we can uninstall the InventorNetAddinWizardPro silently without any UIs. Here it is:
msiexec.exe /x "InventorNetAddinWizardPRO.msi" /qn
/x indicates uninstallation; /qn indicates in quiet mode and no UIs.
The following command line will install InventorNetAddinWizardPro:
msiexec.exe /i "InventorNetAddinWizardPRO.msi"
The following command line will deploy the VSIX if the InventorNetAddinWizardPro is installed to the default folder.
VSIXInstaller.exe "C:\Program Files (x86)\InventorNetAddinWizardPRO\INAW2015.vsix"
Combining these together in a .BAT file may make uninstallation, reinstallation, and VSIX deployment happen with a single click. Of course, it depends on real situations, and some options may need to be adjusted a bit. Here they are anyway.
msiexec.exe /x "InventorNetAddinWizardPRO.msi" /qn
msiexec.exe /i "InventorNetAddinWizardPRO.msi"
VSIXInstaller.exe "C:\Program Files (x86)\InventorNetAddinWizardPRO\INAW2015.vsix"
02/19/2016
InventorNetAddinWizardPro 2015 New Build# 2.1.0.1 Was Rolled Out
A new build of Inventor .NET Addin Wizard 2015 has been worked out and posted. It addresses some issues. Please find it from the sites as usual.
02/14/2016
We Are Still Here
No posts have been made on this blog since the New Year. We have been busy with something else.
Anyway, if any topics or hot spots you'd like us to cover regarding Inventor APIs, wizards, addins, tools or something else, please feel free to let us know.
Spiderinnet2
a spider crawling mainly in the .NET of Inventor
Recent Comments