Hi Jay,
I've added a link to one designer tool for the ribbon xml - there are a few. You can also use the VSTO ribbon designer and export the ribbon customUI xml from there (particularly if you have an existing add-in). Basically all the tools end up making the
same ribbon xml that you need for the Excel-DNA add-in, and it doesn't matter how you make the xml.
How difficult it is to port a VSTO add-in will depend on how much you use of the extensions that VSTO adds on top of the object model. The main aspects that I can think of are:
* Table / ListObject extensions
* the data binding support
* the ribbon implementation helpers, allowing you to write myButton.Enabled = false. The implementation of this is actually a local variable storing the desired 'enabled' setting, a getEnabled callback on the ribbon class, and some code that invalidates
the control when the setting changes, triggering the callback again.
All of these VSTO extensions are implemented on top of the object model, so can be implemented by your add-in too. But it can be a lot of work.
On the other hand, anything in that is just regular COM object model use (not in the Microsoft.Office.Tools.XXX namespace) will work as-is in your Excel-DNA add-in.
I hope that gives you a bit more information to get started, and please post back if you run into specific issues.
Regards,
Govert