Develop Office Client Applications using Visual Studio
In this interview, I sit down with Stephen Peters, a developer on the Office client tools team in Visual Studio. Steve shows us a couple of tricks for how you can squeeze the best performance out of Office solutions built with Visual Studio (VSTO). He also shows how to finely control the way your custom ribbons load, as well as how to eliminate references to the Utilities assembly. Check it out:
Channel 9 Interview: Office Add-in (VSTO) Performance Tips & Tricks
For more information, see his blog post: VSTO Performance: Ribbon Reflection
Enjoy, -Beth Massi, Visual Studio Community
No disrespect to your team intended, because I really appreciate your efforts in trying to explain this.
But if it's this complicated (as it clearly is even for the people who are working with it every day), how do you think the average VSTO developer feels?
I understand where you're coming from - I spent a lot of time working out how to do that in the first place. A lot of the interview was "showing my work" so that everyone could understand the "why" of what we were doing, not just the "what". I don't expect customers to dis-assemble our binaries on a regular basis :-)
That said, I am currently putting together a blog post that will more directly lay out how to remove the utilities assemblies from your 4.0 project.
Thank you. It was definitely an interesting overview but a little over my head. I'm very interested in the ribbon loading and add-in performance tips.
For the optimization to overcome the reflection lag time loading the ribbon for large assemblies, does that only apply to VSTO 3.5 and 4.0, or will it work in earlier versions (i.e., VSTO SE)?