Brendan Cassidy

@StudioLE @WaynePatrickDalton Have a look at the about window in the following branch i have created in my fork it will create the about window as per the below image...

@StudioLE No worries, though it is probably one of the more simple examples of WPF windows.

The dynamo player is possibly loading dynamo without the "UI" (DynamoView), therefore it does not load a "ViewExtension". You would need to switch anything that is part of your extension...

I can help add a way to create a config file to help reduce the burden on you @johnpierson

Within the RibbonUtils.AddItems method you add a way to tell if a button is to be stackable, then this is added to a stackable button model in a similar way...

@EwanOpie How did you get around the common bug when using FileSystemWatcher because it does sometimes fire two change events off.

@EwanOpie Maybe revit is stopping a secondary load of dynamo, so it is not becoming apparent. I have noticed in a test i did that the event that fires up...

I would suggest splitting this into packages and Toolbar then into Revit versions. Just in case any toolbar scripts need to have a folder called packages then things wont get...

This could be tough to implement with the required fail safes, though as long as it is within the dynamics of what is allowed in a revit addon then it...

The version checking could apply on the About Window, i have quickly implemented it into my fork at the following files: AboutView.xaml - https://github.com/brencass/MonocleForDynamo/blob/VersionChecker/src/Monocle/About/AboutView.xaml AboutView.xaml.cs - https://github.com/brencass/MonocleForDynamo/blob/VersionChecker/src/Monocle/About/AboutView.xaml.cs Utilities.cs - https://github.com/brencass/MonocleForDynamo/blob/VersionChecker/src/Monocle/Utilities/Utilities.cs