We found a discrepancy about the VB.NET Root Namespace in Visual Studio 2010 and 2008 years ago, and addressed it in an old post:
VB.NET Root Namespace vs. C# Default Namespace
We had to leave the Root Namespace of VB.NET projects that were automatically generated by our wizards as blank so as to keep the behavior consistent and avoid loading problems by Revit, as it uses the fully qualified class name as the external application identity.
It was obvious that Visual Studio realized the problem and fixed it in later versions, 2015, 2013 and 2012. So, now the VB.NET Root Namespace behaves the same as the C# Default Namespace. That makes things return to normal, but leaves the VB.NET projects, which were generated by using the old versions of our project wizards inside the new Visual Studio IDEs, not loadable directly by Revit. Of course, it can be easily tweaked manually, i.e. adding the Root Namespace to the VB.NET projects.
We sorted it out and fixed it during the recent major upgrade and intensive retesting. Please try the latest Revit .NET Addin Wizard 2015 and see. All projects (VB.NET, C# and CLI/C++) automatically generated by the project wizards should be loaded just fine by the designated Revit flavor or version.
Recent Comments