1. VSTO Pranav Ainavolu VSTO Developer, Conrep Solutions | Email: pranav@conrep.com

3. Latest version is VSTO 3.0 available as part of VS – 2008.

6. Latest version is VSTO 3.0 available as part of VS – 2008.

8. Roadmap v3.0 (in VS2008) Workflow & Microsoft SharePoint support Office 2007 system-specific features, file format, UI App-level add-ins for more client applications Deeper server-side programming VSTO fully integrated into Visual Studio 2008 2005 SE App-level add-ins for most popular Office apps Runtime support for key Office 2007 UI elements (Custom Taskpane, Ribbon, Outlook form regions) Runtime support enabling Office 2003 doc-level customizations to run in Office 2007 2003 2003 2007 2007 2005 Custom Document ActionsPane Host Controls on document surface Cached data in the document Server-side data processing Application-level add-ins for Outlook

9. Outlook Add-ins

11. More reliable add-in/host interaction

13. Visual Studio Setup project for Outlook add-ins

15. Deployment & Security

17. VSTO has a manifest-based deployment model

18. Application Manifest

19. Embedded in the document and describes the solution (startup assembly, dependencies, deployment manifest)

20. Deployment Manifest

21. Points to the Application Manifest and handles Application Manifest version resolution

23. Local/Network – document resides on local machine, assembly resides on network

24. Network/Network – both document and assembly reside on the network

25. This is especially useful for Template projectsNote: InfoPath deployment is slightly different Assemblies and manifest reside in an XSN XML files point to XSN

27. .NET Framework 2.0

28. VSTO 2005 Runtime

29. Office Primary Interop Assemblies (PIAs)

31. Evidence

32. Location based for documents

33. Any type of evidence for the assemblies

34. Permissions

35. Document location and code must be fully trusted

36. Levels

37. Enterprise, Machine, User, Application

38. A given permission is granted only if all policy levels agree to grant it

40. Doesn’t need to use .NET Code Access Security because assemblies can be fully trusted when

41. they are signed

43. Questions?