Hi Dave,
This is in response to your EXEC_ADD_IN query - Simon will get back re customizing code templates.
Sounds like you're roughly on the right track with the add-in. Couple of points :
1. You probably don't need to make your add-in an MDG add-in (at least not at this stage). Being an MDG add-in has some advantages, but there's also other baggage you need to deal with ... so return an empty string in your EA_Connect function.
2. Make sure EA is actually talking to your add-in. (If it's not, you will be prompted when starting up EA). The following sample functions should be enough to test with. It includes a dummy menu option just so you know things are working. Other than that, I used the same EXEC_ADD_IN call from the template that you did and got the intended result...
Function EA_Connect(Repository As EA.Repository) As String
EA_Connect = ""
End Function
Function EA_GetMenuItems(Repository As EA.Repository, Location As String, MenuName As String) As Variant
EA_GetMenuItems = "Hello"
End Function
Sub EA_GetMenuState(Repository As EA.Repository, MenuLocation As String, MenuName As String, ItemName As String, IsEnabled As Boolean, IsChecked As Boolean)
IsEnabled = True
End Sub
Sub EA_MenuClick(Repository As EA.Repository, MenuLocation As String, MenuName As String, ItemName As String)
MsgBox "Hello World!", vbInformation
End Sub
Function MyTest(Repository As EA.Repository, Args As Variant) As String
Dim arg As String
arg = Args(LBound(Args))
MyTest = "ReturnString"
End Function
Having done the above, are you at least able to see your add-in from the add-ins menu? Let me know if it still isn't working for you...
One other note : Body code for methods is only inserted on initial forward generation - ie. when you generate/overwrite the file initially, or forward synch a new method into your existing code.
I hope this helps
Regards,
Ben