.NET4OfficeA blog by Eric CarterDeploying VSTO 2008 add-ins to all users (continued)- April 26, 2008 Misha blogs again, this time about how to install a VSTO 2008 add-in to all users on a machine. Deploying your VSTO 2008 Add-In to All Users (Part III)http://blogs.msdn.com/eric_carter/archive/2008/04/26/deploying-vsto-2008-add-ins-to-all-us... VBA and VSTO Can Be Friends (Part II)- April 25, 2008 VBA code can easily be called from VSTO.&160; Here are the basic steps. Create a document with VBA code in it. Declare a public function or subroutine in the VBA code behind the document. Figure out a trusted location to create a VSTO project from Create a new VSTO project using the document with the VBA code in it--be sure to create the project in a trusted location. From VSTO code, write the code "Me.Application.Run("MethodName", param1, param2, ...) So let's..http://blogs.msdn.com/eric_carter/archive/2008/04/25/vba-and-vsto-can-be-friends-part-ii.a... VSTO 2008 Case Studies- April 23, 2008 Slavishly copied from John Durant's blog, I hadn't seen these before so I thought I'd pass them one.&160; They are two case studies showing how CME Group and Dell used Visual Studio 2008 and the new features of VSTO in their solutions. CME Group Link to Case Study Microsoft Visual Studio Microsoft Visual Studio Team System 2008 Team Suite Microsoft Visual Studio 2005 Team Foundation Server Microsoft Server Product Portfolio Windows Server 2003...http://blogs.msdn.com/eric_carter/archive/2008/04/23/vsto-2008-case-studies.aspx Video on VSTO Power Tools- April 22, 2008 There's a nice intro video to the VSTO Power Tools we recently released on Channel 9.&160; Hopefully when i get a little more time, I'll be able to blog a bit more about these tools.&160; For now, check out the video intro: http:channel9.msdn.comShowPost.aspxPostID=397787397787http://blogs.msdn.com/eric_carter/archive/2008/04/22/video-on-vsto-power-tools.aspx VBA and VSTO Can Be Friends (Part I)- April 21, 2008 One of the cool new features of VSTO 3.0 is better support for what I would term "Extending VBA with VSTO". Our strategy here and what we recommend to customers is that we aren't going to try to migrate all your VBA code to VSTO--this is a bit of an unsolvable problem to get 100% right. Instead, what we want to enable is to allow you to take your existing VBA solutions and add to them with VSTO and .NET. Why would you want to do this Well, there are a ton of developer technologies...http://blogs.msdn.com/eric_carter/archive/2008/04/21/vba-and-vsto-can-be-friends-part-i.as... OBA Sample Application for PeopleSoft- April 18, 2008 During Kurt DelBene&8217;s keynote at Collaborate 08 the OBA Sample Application Kit for PeopleSoft&8212;a new addition to the small family of OBA Sample Application Kits&8212;was announced&160; This kit was designed for developers and architects to download the kit and learn how they can integrate Outlook 2007 and MOSS 2007 with PeopleSoft.&160; You can download the kit directly here: http:code.msdn.microsoft.comobapsftsak. You can alternatively visit our new OBA Sample Application Kits...http://blogs.msdn.com/eric_carter/archive/2008/04/18/oba-sample-application-for-peoplesoft... How Do I Get My VSTO Add-in for Office 2007 to Install for All Users- April 17, 2008 This is a common question with VSTO 3.0 add-ins.&160; Office only allows VSTO add-ins to be registered under HKCU in the registry which means they can only be installed for the user that runs your add-in setup on their account, not available to all users on a machine after you run the installer under one account. There are some reasons for this behavior--in general it is better to not install for all users unless you absolutely have to as it requires an elevation of privilege to write to HKLM..http://blogs.msdn.com/eric_carter/archive/2008/04/17/how-do-i-get-my-vsto-add-in-for-offic... ApplicationClass Needn't Be Avoided- April 16, 2008 Geoff Darst--an engineer on our team--sent this to me a while back and I think it would be good to pass it on. I still think in general people avoid using ApplicationClass because it makes your code look like the VBA and VB6 code everyone is familiar with.&160; But Geoff points out that there is no need to explicitly avoid ApplicationClass.&160; You may need to revisit the blog post he refers to in order to get the context where his comments make sense. I just stumbled on your blog post...http://blogs.msdn.com/eric_carter/archive/2008/04/16/applicationclass-needn-t-be-avoided.a... |