<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.officezealot.com/utility/FeedStylesheets/atom.xsl" media="screen"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en"><title type="html">Vijay Mutalik-Desai</title><subtitle type="html" /><id>http://blogs.officezealot.com/desai/atom.aspx</id><link rel="alternate" type="text/html" href="http://blogs.officezealot.com/desai/default.aspx" /><link rel="self" type="application/atom+xml" href="http://blogs.officezealot.com/desai/atom.aspx" /><generator uri="http://communityserver.org" version="2.1.61129.2">Community Server</generator><updated>2005-12-04T19:30:00Z</updated><entry><title>Rebuilding Perfmon counters on XP</title><link rel="alternate" type="text/html" href="http://blogs.officezealot.com/desai/archive/2006/10/20/14201.aspx" /><id>http://blogs.officezealot.com/desai/archive/2006/10/20/14201.aspx</id><published>2006-10-20T23:38:00Z</published><updated>2006-10-20T23:38:00Z</updated><content type="html">
&lt;p&gt;   Perfmon is an extremely handy utility to track application performance. When tracing   the performance of .NET applications(VSTO/IBF) on the Office platform, I find the   counter counter "# of Stubs" provided by the performance object ".NET CLR Interop"   very useful. This counter displays the count of RCWs created by the CLR. &lt;/p&gt;

&lt;p&gt;   I wanted to use this counter on my XP box, but when I opened Perfmon, I could only   see a list of random numbers in the Performance Object drop down box! The fix   for this has been documented in &lt;a href="http://support.microsoft.com/?kbid=300956"&gt;KB300956&lt;/a&gt;.   However, the steps in the KB did not help me. It was &lt;a href="http://channel9.msdn.com/ShowPost.aspx?PostID=61336"&gt;this   discussion&lt;/a&gt; on the Channel9 forum that helped me restore the Perfmon counters.   I stumbled on this link after a lot of searching, so thought of posting it here for   future reference. Also, having submitted a feedback to Microsoft Support, I hope   the KB article will be updated someday! :)  &lt;/p&gt;

&lt;span&gt;
&lt;script src="http://pagead2.googlesyndication.com/pagead/show_ads.js" type="text/javascript"&gt;

&lt;/script&gt;
&lt;/span&gt;&lt;img src="http://blogs.officezealot.com/aggbug.aspx?PostID=14201" width="1" height="1"&gt;</content><author><name>desai</name><uri>http://blogs.officezealot.com/members/desai.aspx</uri></author></entry><entry><title>Outlook 2007 and CDO</title><link rel="alternate" type="text/html" href="http://blogs.officezealot.com/desai/archive/2006/10/18/14127.aspx" /><id>http://blogs.officezealot.com/desai/archive/2006/10/18/14127.aspx</id><published>2006-10-19T00:00:00Z</published><updated>2006-10-19T00:00:00Z</updated><content type="html">&lt;p&gt;   Recently I worked on an application that used CDO to open the Global Address   Book. The application worked when it ran with Outlook 2003, but failed with the   following exception when I used Outlook 2007.&lt;/p&gt;&lt;p&gt;   &lt;font face="Courier New"&gt;  System.Runtime.InteropServices.COMException was   caught&lt;br /&gt;     Message="Retrieving the COM class factory for component with CLSID {3FA7DEB3-6438-101B-ACC1-00AA00423326}   failed due to the following error: 80040154."&lt;/font&gt;&lt;/p&gt;&lt;p&gt;   It turns out that CDO library is not shipped as a part of Office 2007 setup. If you   are using CDO library to access Outlook objects and have plans to move your application   to Office 2007, please make a note of this. The fix for this exception is to download   CDO library from &lt;a href="http://www.microsoft.com/downloads/details.aspx?FamilyID=2714320d-c997-4de1-986f-24f081725d36&amp;amp;displaylang=en"&gt;here&lt;/a&gt; and   install it! &lt;/p&gt;&lt;img src="http://blogs.officezealot.com/aggbug.aspx?PostID=14127" width="1" height="1"&gt;</content><author><name>desai</name><uri>http://blogs.officezealot.com/members/desai.aspx</uri></author></entry><entry><title>Sun in Microsoft Land!! </title><link rel="alternate" type="text/html" href="http://blogs.officezealot.com/desai/archive/2006/02/10/9197.aspx" /><id>http://blogs.officezealot.com/desai/archive/2006/02/10/9197.aspx</id><published>2006-02-11T06:05:00Z</published><updated>2006-02-11T06:05:00Z</updated><content type="html">After a long time, the sun shone brightly in the Seattle skies and made its presence felt overhead. Another Sun is also making its presence felt here; if you take a ride in one of the King county Metro buses that criss-cross the Redmond campus and look at the Ad Banners overhead. 

&lt;p&gt;
Sun Microsystems has come up with creative ads promoting OpenOffice. The ad shows people dressed in T-shirts that have witty one-liners printed on them. 
&lt;/p&gt;

&lt;p&gt;
Here are a few ones that caught my attention. 
&lt;li&gt; Stop giving a bully your lunch money. &lt;/li&gt;
&lt;li&gt; By the people, for the people. &lt;/li&gt;
&lt;li&gt; Compatible with expensive, closed and memory loving software. &lt;/li&gt;
&lt;li&gt; Pick a vendor. Any Vendor. &lt;/li&gt;
&lt;li&gt; Tired of being taken for a ride. &lt;/li&gt;
&lt;li&gt; US-opoly. &lt;/li&gt;
&lt;li&gt; We do windows, too. &lt;/li&gt;
&lt;li&gt; Pre-historic reptilians welcome. &lt;/li&gt; 
&lt;/p&gt;

&lt;p&gt;
The ads also have been put up very strategically. This is for the first time that I have seen software being advertised in a public transit system!! I wonder if Microsoft will ever do this. It is good to see this new trend in advertising and promoting a software product. 
&lt;/p&gt;

&lt;p&gt;
I for sure, feel tempted to check out the latest offering from OpenOffice after seeing these well-thought of ads!! 
&lt;/p&gt;
&lt;img src="http://blogs.officezealot.com/aggbug.aspx?PostID=9197" width="1" height="1"&gt;</content><author><name>desai</name><uri>http://blogs.officezealot.com/members/desai.aspx</uri></author></entry><entry><title>Tip for COM - .NET Interop developers</title><link rel="alternate" type="text/html" href="http://blogs.officezealot.com/desai/archive/2005/12/27/8874.aspx" /><id>http://blogs.officezealot.com/desai/archive/2005/12/27/8874.aspx</id><published>2005-12-27T16:09:00Z</published><updated>2005-12-27T16:09:00Z</updated><content type="html">I was trying my hands at creating a .NET 2.0 component that can be consumed by a COM application. 

&lt;br/&gt;
One of the errors I got in the process of registering the .NET assembly was 
 
&lt;br/&gt;
RegAsm : warning RA0000 : No types were registered.

&lt;p&gt;
This was baffling!! I had done everything right and spent quite some time figuring out what could have gone wrong... until I had a look at the AssemblyInfo.cs. The ComVisible property for the assembly was set to false!! To access types in a .NET assembly from COM, this property should be set to true. Once I did it, I was able to successfully register the .NET assembly and consume it in my COM component.  Be sure to remember this when developing COM - .NET interop applications!! 
&lt;/p&gt;
 &lt;img src="http://blogs.officezealot.com/aggbug.aspx?PostID=8874" width="1" height="1"&gt;</content><author><name>desai</name><uri>http://blogs.officezealot.com/members/desai.aspx</uri></author></entry><entry><title>Editing Office Document properties without Office</title><link rel="alternate" type="text/html" href="http://blogs.officezealot.com/desai/archive/2005/12/04/8707.aspx" /><id>http://blogs.officezealot.com/desai/archive/2005/12/04/8707.aspx</id><published>2005-12-05T03:30:00Z</published><updated>2005-12-05T03:30:00Z</updated><content type="html">I wanted to access the properties of an Office document without using the Office Interops. 

This &lt;a href="http://support.microsoft.com/?kbid=224351"&gt;KB article&lt;/a&gt; describes exactly how to do that using VB.Net.  On searching more, I came across this &lt;a href="http://www.codeproject.com/csharp/DSOFileDemo.asp"&gt;article&lt;/a&gt; on Code Project demonstrating how to do it in C#. 

&lt;img src="http://blogs.officezealot.com/aggbug.aspx?PostID=8707" width="1" height="1"&gt;</content><author><name>desai</name><uri>http://blogs.officezealot.com/members/desai.aspx</uri></author></entry></feed>