<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/atom.xsl" media="screen"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-US"><title type="html">Sandeep Bhatia's blog</title><subtitle type="html" /><id>http://blogs.msdn.com/sandeep_bhatia/atom.xml</id><link rel="alternate" type="text/html" href="http://blogs.msdn.com/sandeep_bhatia/default.aspx" /><link rel="self" type="application/atom+xml" href="http://blogs.msdn.com/sandeep_bhatia/atom.xml" /><generator uri="http://communityserver.org" version="2.1.61025.2">Community Server</generator><updated>2008-12-06T11:15:00Z</updated><entry><title>Hook Custom adapters to VSTA pipeline</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/sandeep_bhatia/archive/2008/12/24/hook-custom-adapters-to-vsta-pipeline.aspx" /><id>http://blogs.msdn.com/sandeep_bhatia/archive/2008/12/24/hook-custom-adapters-to-vsta-pipeline.aspx</id><published>2008-12-24T13:27:00Z</published><updated>2008-12-24T13:27:00Z</updated><content type="html">We have seen how we can use the VSTA provided pipeline to load add-ins and enable various scenarios. There may be some cases when we want to extend the existing VSTA pipeline to enable new kind of contracts, to allow any of our custom types to cross the contract boundary (if we don’t care about any of the type isolation requirements!) or just for reasons like performance where a custom adapter could give better performance than the generic VSTA mechanism. Let’s see how the existing VSTA pipeline...(&lt;a href="http://blogs.msdn.com/sandeep_bhatia/archive/2008/12/24/hook-custom-adapters-to-vsta-pipeline.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9251665" width="1" height="1"&gt;</content><author><name>sandeep bhatia</name><uri>http://blogs.msdn.com/members/sandeep+bhatia.aspx</uri></author><category term="VSTA" scheme="http://blogs.msdn.com/sandeep_bhatia/archive/tags/VSTA/default.aspx" /></entry><entry><title>IEntryPoint or IExtendedEntryPoint</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/sandeep_bhatia/archive/2008/12/21/ientrypoint-or-iextendedentrypoint.aspx" /><id>http://blogs.msdn.com/sandeep_bhatia/archive/2008/12/21/ientrypoint-or-iextendedentrypoint.aspx</id><published>2008-12-22T04:33:00Z</published><updated>2008-12-22T04:33:00Z</updated><content type="html">If you see the definition of the two interfaces defined in Microsoft.VisualStudio.Tools.Applications.Runtime.v9.0.dll you would notice that IExtendedEntryPoint is derived from IEntryPoint. In most of the host add-in applications add-in is the consumer of the host object model, IEntryPoint was derived from that perspective and it could be used in most of the scenarios where add-in is the consumer of the host object model. But for the scenarios where host also needs to know the add-in object model....(&lt;a href="http://blogs.msdn.com/sandeep_bhatia/archive/2008/12/21/ientrypoint-or-iextendedentrypoint.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9246090" width="1" height="1"&gt;</content><author><name>sandeep bhatia</name><uri>http://blogs.msdn.com/members/sandeep+bhatia.aspx</uri></author></entry><entry><title>Details of Integration</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/sandeep_bhatia/archive/2008/12/21/details-of-integration.aspx" /><id>http://blogs.msdn.com/sandeep_bhatia/archive/2008/12/21/details-of-integration.aspx</id><published>2008-12-21T13:32:00Z</published><updated>2008-12-21T13:32:00Z</updated><content type="html">We saw in the earlier posts how simple it is to enable an application to load add-ins and enjoy all the benefits that come with loosely coupled usage of the host object model. CLR Add-In framework is the base for implementation of VSTA 2.0. Refer to blogs.msdn.com/clraddins for details around the Add-In framework. To keep it simple and straightforward lets dive into the details of the integration code that was provided in the earlier post so that we could understand the workings of VSTA in a better...(&lt;a href="http://blogs.msdn.com/sandeep_bhatia/archive/2008/12/21/details-of-integration.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9245429" width="1" height="1"&gt;</content><author><name>sandeep bhatia</name><uri>http://blogs.msdn.com/members/sandeep+bhatia.aspx</uri></author><category term="VSTA" scheme="http://blogs.msdn.com/sandeep_bhatia/archive/tags/VSTA/default.aspx" /></entry><entry><title>Exposing a service through an Add-In</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/sandeep_bhatia/archive/2008/12/06/exposing-a-service-through-an-add-in.aspx" /><id>http://blogs.msdn.com/sandeep_bhatia/archive/2008/12/06/exposing-a-service-through-an-add-in.aspx</id><published>2008-12-06T23:06:00Z</published><updated>2008-12-06T23:06:00Z</updated><content type="html">In the previous post we did a walkthrough on how to do simple runtime integration with VSTA 2.0. In this post we would see if how the sample can be modified to support a scenario where an Add-In exposes a service and another Add-In consumes it. I modified our simple OM in the previous blog to add two methods one that accepts new service registrations and other that returns the service when queried by the caller (In this case our Add-In). How these methods are implemented and exposed are just host...(&lt;a href="http://blogs.msdn.com/sandeep_bhatia/archive/2008/12/06/exposing-a-service-through-an-add-in.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9181454" width="1" height="1"&gt;</content><author><name>sandeep bhatia</name><uri>http://blogs.msdn.com/members/sandeep+bhatia.aspx</uri></author></entry><entry><title>A simple VSTA 2.0 runtime integration</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/sandeep_bhatia/archive/2008/12/06/a-simple-vsta-2-0-runtime-integration.aspx" /><id>http://blogs.msdn.com/sandeep_bhatia/archive/2008/12/06/a-simple-vsta-2-0-runtime-integration.aspx</id><published>2008-12-06T22:25:00Z</published><updated>2008-12-06T22:25:00Z</updated><content type="html">VSTA 2.0 is quick and easy way to build and deploy add-ins for host applications. You could refer to summit website to see how you could get your own copy of VSTA 2.0 SDK. http://www.summsoft.com Going forward I assume you have the latest bits of VSTA 2.0 SDK installed on your machine and are ready to dive into creation of add-ins for your custom host. Usually end users and VSTA 2.0 integrators or amateur developers who want to integrate VSTA or just want to play around with the same end up getting...(&lt;a href="http://blogs.msdn.com/sandeep_bhatia/archive/2008/12/06/a-simple-vsta-2-0-runtime-integration.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9181440" width="1" height="1"&gt;</content><author><name>sandeep bhatia</name><uri>http://blogs.msdn.com/members/sandeep+bhatia.aspx</uri></author><category term="VSTA" scheme="http://blogs.msdn.com/sandeep_bhatia/archive/tags/VSTA/default.aspx" /></entry><entry><title>The Start!</title><link rel="alternate" type="text/html" href="http://blogs.msdn.com/sandeep_bhatia/archive/2008/12/06/the-start.aspx" /><id>http://blogs.msdn.com/sandeep_bhatia/archive/2008/12/06/the-start.aspx</id><published>2008-12-06T22:15:00Z</published><updated>2008-12-06T22:15:00Z</updated><content type="html">Welcome to the blog!! I am a dev on VSTA team (Visual Studio Tools For Applications). I would not only try to use this blog as a instrument to share my insights about VSTA but also try to share any other useful information that could solve a problem out there!...(&lt;a href="http://blogs.msdn.com/sandeep_bhatia/archive/2008/12/06/the-start.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=9181434" width="1" height="1"&gt;</content><author><name>sandeep bhatia</name><uri>http://blogs.msdn.com/members/sandeep+bhatia.aspx</uri></author></entry></feed>