You are correct in the fact that VB requires deeper namespace declaration in the manifest than C#, but I am developing in C#.
Here is the IExternalCommand Implementation, although this does not get impemented in the .Addin file in question.
#region Namespaces
using System;
using System.Collections.Generic;
using System.Diagnostics;
using Autodesk.Revit.ApplicationServices;
using Autodesk.Revit.Attributes;
using Autodesk.Revit.DB;
using Autodesk.Revit.UI;
using Autodesk.Revit.UI.Selection;
#endregion
namespace Spoolmatter
{
[Transaction(TransactionMode.Manual)]
public class Command : IExternalCommand
{
public Result Execute(ExternalCommandData commandData, ref string message, ElementSet elements)
{
UIApplication uiapp = commandData.Application;
UIDocument uidoc = uiapp.ActiveUIDocument;
Application app = uiapp.Application;
Document doc = uidoc.Document;
TaskDialog.Show("Test", "Hello :)");
//using (Transaction tx = new Transaction(doc))
//{
// tx.Start("Format");
// tx.Commit();
//} TEMP
return Result.Succeeded;
}
}
}
The main issue I am having is that I can't wrap my head around trying to diagnose this specific error for the .addin manifest file since it isn't really a class AFAIK.