hey men,
hmm.. its hard to explain because i dont know your experience level....
the "normal" way to create an addin is to implement the IExtensibility2 interface.
make it com visible and register for com interop, create register/unregister methods and hope it works well.
in fact: you have to write a lot of infrastructure code to create and empty addin. moreover you have to know
a lot of small things about office developement... all the details.
the NO Tools for addins is a top-of wrapper, basicly the base class COMAddin. all common infrastructure tasks for addins is implemented here
and waiting for your command. the whole idea: inherite from COMAddin and just setup some attributes. thats all. (VSTO does basicly the same under the hood)
(of course, annotations are sweet poison, easy to use at design-time, but no control at runtime. NO Tools spend also all possible control at runtime. in this case, you have to override some virtual methods)
the super addin example is very minimalistic. please checkout one of the extended addin examples(may excel\examples\COM addin examples)
to learn more about how you create your ribbon ui or taskpane and anyone else.
a real object-based ui layer like vsto(incl. a visual designer) is planned in NetOffice 1.8 for some selected office applications(excel/outlook) and completly for all in NetOffice 2.0. This is what i currently work for.
*Sebastian
hmm.. its hard to explain because i dont know your experience level....
the "normal" way to create an addin is to implement the IExtensibility2 interface.
make it com visible and register for com interop, create register/unregister methods and hope it works well.
in fact: you have to write a lot of infrastructure code to create and empty addin. moreover you have to know
a lot of small things about office developement... all the details.
the NO Tools for addins is a top-of wrapper, basicly the base class COMAddin. all common infrastructure tasks for addins is implemented here
and waiting for your command. the whole idea: inherite from COMAddin and just setup some attributes. thats all. (VSTO does basicly the same under the hood)
(of course, annotations are sweet poison, easy to use at design-time, but no control at runtime. NO Tools spend also all possible control at runtime. in this case, you have to override some virtual methods)
the super addin example is very minimalistic. please checkout one of the extended addin examples(may excel\examples\COM addin examples)
to learn more about how you create your ribbon ui or taskpane and anyone else.
a real object-based ui layer like vsto(incl. a visual designer) is planned in NetOffice 1.8 for some selected office applications(excel/outlook) and completly for all in NetOffice 2.0. This is what i currently work for.
*Sebastian