<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Writing an Outlook Add-in with C# (Epilogue)</title>
	<link>http://www.midniteblog.com/2007/04/18/writing-an-outlook-add-in-with-c-epilogue/</link>
	<description>Ruminations and ramblings about the world of coding for a living</description>
	<pubDate>Thu, 28 Aug 2008 20:30:32 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1.3</generator>

	<item>
		<title>By: helloween</title>
		<link>http://www.midniteblog.com/2007/04/18/writing-an-outlook-add-in-with-c-epilogue/#comment-6</link>
		<author>helloween</author>
		<pubDate>Sun, 29 Jul 2007 16:58:07 +0000</pubDate>
		<guid>http://www.midniteblog.com/2007/04/18/writing-an-outlook-add-in-with-c-epilogue/#comment-6</guid>
					<description>Hi, First, big Thanks for your blog.
It gave me a lot of information on outlook plugins.

I think I have the answer for "why we can't redistribute this extensibility.dll?"

I am programming my outlook plugin with visual express edition, it works perfect on my development PC, but when I want to deploy it on test machine, naturally this DLL is missing and outlook won't load the plugin until you copy this extensibility.dll.

I went to download this sdk package to get the extensibilityMSM.msi and as I expected, when I tried to install it: "visual studio 2005 not found!".


"With visual express, you have no license limitation for commercial application !! " For sure yeah, you can't redistribute them.

So basically, I have no idea how I am going to get this plugin working on client machine, since I am a student and can't afford any professional version. For the moment I am just disgusted of .NET, it is great to program and have fun with but it is more than a PAIN to deploy.
If you have any news about this situation ... :(</description>
		<content:encoded><![CDATA[<p>Hi, First, big Thanks for your blog.<br />
It gave me a lot of information on outlook plugins.</p>
<p>I think I have the answer for &#8220;why we can&#8217;t redistribute this extensibility.dll?&#8221;</p>
<p>I am programming my outlook plugin with visual express edition, it works perfect on my development PC, but when I want to deploy it on test machine, naturally this DLL is missing and outlook won&#8217;t load the plugin until you copy this extensibility.dll.</p>
<p>I went to download this sdk package to get the extensibilityMSM.msi and as I expected, when I tried to install it: &#8220;visual studio 2005 not found!&#8221;.</p>
<p>&#8220;With visual express, you have no license limitation for commercial application !! &#8221; For sure yeah, you can&#8217;t redistribute them.</p>
<p>So basically, I have no idea how I am going to get this plugin working on client machine, since I am a student and can&#8217;t afford any professional version. For the moment I am just disgusted of .NET, it is great to program and have fun with but it is more than a PAIN to deploy.<br />
If you have any news about this situation &#8230; <img src='http://www.midniteblog.com/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /></p>
]]></content:encoded>
				</item>
	<item>
		<title>By: MidniteBlogger</title>
		<link>http://www.midniteblog.com/2007/04/18/writing-an-outlook-add-in-with-c-epilogue/#comment-7</link>
		<author>MidniteBlogger</author>
		<pubDate>Sun, 29 Jul 2007 19:16:22 +0000</pubDate>
		<guid>http://www.midniteblog.com/2007/04/18/writing-an-outlook-add-in-with-c-epilogue/#comment-7</guid>
					<description>I think this problem is addressed in my section above titled:
The Answer:
How to redistribute Extensibility.dll
The firm where I work has decided to deploy commercially based on the MSFT KB fix (VS2005-KB908002-ENU-x86.EXE), so I suspect they would know by now if it didn't work. If this is not the case I will be sure to post here.  
I would encourage helloween in his dilemma to try the extensibilityMSM.msi install on a "clean" machine and see if that makes any difference.  
midniteblogger.</description>
		<content:encoded><![CDATA[<p>I think this problem is addressed in my section above titled:<br />
The Answer:<br />
How to redistribute Extensibility.dll<br />
The firm where I work has decided to deploy commercially based on the MSFT KB fix (VS2005-KB908002-ENU-x86.EXE), so I suspect they would know by now if it didn&#8217;t work. If this is not the case I will be sure to post here.<br />
I would encourage helloween in his dilemma to try the extensibilityMSM.msi install on a &#8220;clean&#8221; machine and see if that makes any difference.<br />
midniteblogger.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: helloween</title>
		<link>http://www.midniteblog.com/2007/04/18/writing-an-outlook-add-in-with-c-epilogue/#comment-8</link>
		<author>helloween</author>
		<pubDate>Sun, 29 Jul 2007 23:46:36 +0000</pubDate>
		<guid>http://www.midniteblog.com/2007/04/18/writing-an-outlook-add-in-with-c-epilogue/#comment-8</guid>
					<description>Thanks for your answer,

But as I tried to explain, I can't install the MSFT KB fix, because it asks for a professional version of Visual studio which I dont have (I have only the express edition), so I can't have this extensibilityMSM.msi file :(.

I have been looking everywhere to get only the extensibilityMSM.msi file and did not find anything. And I know that my clean machine only needs this extensibility.dll (a simple copy paste of the file from my development machine to the client and the plugin works !)

Do you have any idea if this is done on purpose to not permit express edition users to release plugins ?

Cheers.</description>
		<content:encoded><![CDATA[<p>Thanks for your answer,</p>
<p>But as I tried to explain, I can&#8217;t install the MSFT KB fix, because it asks for a professional version of Visual studio which I dont have (I have only the express edition), so I can&#8217;t have this extensibilityMSM.msi file :(.</p>
<p>I have been looking everywhere to get only the extensibilityMSM.msi file and did not find anything. And I know that my clean machine only needs this extensibility.dll (a simple copy paste of the file from my development machine to the client and the plugin works !)</p>
<p>Do you have any idea if this is done on purpose to not permit express edition users to release plugins ?</p>
<p>Cheers.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: helloween</title>
		<link>http://www.midniteblog.com/2007/04/18/writing-an-outlook-add-in-with-c-epilogue/#comment-9</link>
		<author>helloween</author>
		<pubDate>Mon, 30 Jul 2007 00:35:29 +0000</pubDate>
		<guid>http://www.midniteblog.com/2007/04/18/writing-an-outlook-add-in-with-c-epilogue/#comment-9</guid>
					<description>Ok, I have finally manage to install this fix, I don't know why the first time I tried it could not find my express edition but it finally found it and I have now this msi package!!
Thanks a lot.</description>
		<content:encoded><![CDATA[<p>Ok, I have finally manage to install this fix, I don&#8217;t know why the first time I tried it could not find my express edition but it finally found it and I have now this msi package!!<br />
Thanks a lot.</p>
]]></content:encoded>
				</item>
</channel>
</rss>
