.net - Beginning VSTO Development -


i'm quite confused necessary tools vsto develpment. want manipulate excel 2003/2007 documents programmatically. did quite lot of vba before, if want relate answer that.

few questions have vsto:

  1. can use visual studio 2008 express edition c#/c++ this?
  2. do need have .net framework installed?
  3. does resulting vsto program need have copy of office installed in same system run?

direct links relevant tools/plugins/ide appreciated.

note: i'm totally new vsto , .net office power user. have experience com programming.

yeah, can confusing, given skip-level naming conventions, etc. essentially, you'll need:

  • full version (not express) of visual studio , .net version you're targetting.
  • one of vsto run times (vsto 2003, vsto 2005, vsto 2005 se, vsto 2008, vsto 2010). asking, vsto 2005 se best bet.
  • when distributing app, you'll need more, pias , .net version you've targetted. vsto 2010, don't need pias (just you're using packaged app automatically).

a couple of tips:

  • going vbe inside of office vsto should smooth-ish move if you've used .net extent.
  • the vsto versions of object models given program (excel, powerpoint, etc.) there may few more ways of doing things different/better in vba version of object model. example, bookmark control word in vsto 2008 not same 1 native 1 accessed via vba.
  • distributing app can pain. reason that vsto visual studio 2010 not require include full interop (pia) files package.
  • targetting different versions of office same solution not officially supported pre-vsto 2010. there ways around issue folks have talked about, won't support msft on it.

there sites should take at:

finally, save best last, book read when starting out , helpful: vsto mere mortals(tm): vba developer's guide microsoft office development using visual studio 2005 tools office


Comments

Popular posts from this blog

C#: Application without a window or taskbar item (background app) that can still use Console.WriteLine() -

c++ - Convert big endian to little endian when reading from a binary file -

openssl - Load PKCS#8 binary key into Ruby -