.net - Tips for VSTO Developers -
For Microsoft Word 2007, I have a personal project that I want to create as an add-in. I have prototyped it using VSTO with Visual Studio 2008 and working with object models was incredibly easy to find.
I'm concerned about the deployment of my add-in. I think users will need Office and .NET 3.5 (with SP1), but they will need something else? What happens when a new service pack or office version is issued?
In addition, what tips would you give to developers to start with VSTO? Do you use a third party library? Tips that make support easier?
To scan the client machine for all the essential things you need to run your VSTO solution And their response status and links to resources to fix them.
Customers will need at least the VSTO runtime (version 3.0 newest now) / primary interop assemblies.
Your solution should work in the case of higher service packs and newer versions of the office, as long as you run against it is available. It will not work with older versions, which develop against you.
One of the biggest color points seems to be code access protection (CAS), but it's really a good thing because it prevents viruses on a large scale and like with the Macro device back in the old days Your friend is here VSTO
- Some random suggestions give some random suggestions to VB an opportunity, this works better for VSTO development, then C # (at least until you use C # 4 And the named optional parameter)
- If you are trying to record a macro from the Office application by using Object Model / API Recording, you can take a look at the macro's VBS code trying.
Comments
Post a Comment