<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>DotBert &#187; .NET</title>
	<atom:link href="http://dotbert.loedeman.nl/category/net/feed" rel="self" type="application/rss+xml" />
	<link>http://dotbert.loedeman.nl</link>
	<description>.NET thoughts by Bert Loedeman</description>
	<lastBuildDate>Wed, 19 Oct 2011 07:57:01 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>How to find public key token for a .NET DLL or assembly</title>
		<link>http://dotbert.loedeman.nl/how-to-find-public-key-token-for-a-net-dll-or-assembly</link>
		<comments>http://dotbert.loedeman.nl/how-to-find-public-key-token-for-a-net-dll-or-assembly#comments</comments>
		<pubDate>Tue, 22 Mar 2011 09:16:45 +0000</pubDate>
		<dc:creator>Bert Loedeman</dc:creator>
				<category><![CDATA[.NET]]></category>
		<category><![CDATA[tip]]></category>

		<guid isPermaLink="false">http://dotbert.loedeman.nl/?p=250</guid>
		<description><![CDATA[I had to find the public key token for a strongly named assembly in .NET. Searching for a solution, I came along Wriju&#8217;s Blog. It appears the answer is very simple: use the .NET Framework tool &#8216;sn.exe&#8217;. Since I do not want to forget about this one, here it is: Open the Visual Studio &#60;version reflecting DLL [...]]]></description>
			<content:encoded><![CDATA[<p>I had to find the public key token for a strongly named assembly in .NET. Searching for a solution, I came along <a title="Wriju's BLOG" href="http://blogs.msdn.com/b/wriju/archive/2008/07/01/how-to-find-public-key-token-for-a-net-dll-or-assembly.aspx" target="_blank">Wriju&#8217;s Blog</a>. It appears the answer is very simple: use the .NET Framework tool &#8216;sn.exe&#8217;. Since I do not want to forget about this one, here it is:</p>
<ol>
<li>Open the Visual Studio &lt;version reflecting DLL creator/signer&gt; Command Prompt</li>
<li>Point to the dll’s folder you want to get the public key</li>
<li>Use the following command: <strong>sn –T myDLL.dll</strong></li>
</ol>
<p><a href="http://dotbert1.loedeman.nl/wp-content/uploads/2011/03/sn_exe_in_action.jpg" rel="shadowbox[sbpost-250];player=img;"><img class="aligncenter size-full wp-image-251" title="sn.exe in action" src="http://dotbert1.loedeman.nl/wp-content/uploads/2011/03/sn_exe_in_action.jpg" alt="How to find public key token for a .NET DLL or assembly sn exe in action" width="677" height="342" /></a></p>
<p>This will give you the public key token. Of course this only works if the assembly is strongly signed <img src='http://dotbert.loedeman.nl/wp-includes/images/smilies/icon_smile.gif' alt="How to find public key token for a .NET DLL or assembly icon smile" class='wp-smiley' title="How to find public key token for a .NET DLL or assembly" />  .</p>
]]></content:encoded>
			<wfw:commentRss>http://dotbert.loedeman.nl/how-to-find-public-key-token-for-a-net-dll-or-assembly/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ILMerge and .NET 4.0 projects &#8211; Unresolved assembly reference not allowed&#8230;</title>
		<link>http://dotbert.loedeman.nl/ilmege-unresoled-assembly-reference-not-allowed-framework-issu</link>
		<comments>http://dotbert.loedeman.nl/ilmege-unresoled-assembly-reference-not-allowed-framework-issu#comments</comments>
		<pubDate>Wed, 16 Feb 2011 22:21:29 +0000</pubDate>
		<dc:creator>Bert Loedeman</dc:creator>
				<category><![CDATA[.NET]]></category>
		<category><![CDATA[ilmerge]]></category>
		<category><![CDATA[visual studio 2010]]></category>

		<guid isPermaLink="false">http://dotbert.loedeman.nl/?p=241</guid>
		<description><![CDATA[For plugin development on an ASP.NET website (using  MEF), I am trying to use ILMerge to merge all .NET assemblies in one assembly. I used a blog post from Scott Hanselman on ILMerge for a starter, but although I followed every step in his post, I ran into the following exception: Unresolved assembly reference not allowed: System.&#60;WhatSoEver&#62;. After  a little [...]]]></description>
			<content:encoded><![CDATA[<div>
<p>For plugin development on an ASP.NET website (using  MEF), I am trying to use <a href="http://www.microsoft.com/downloads/details.aspx?familyid=22914587-b4ad-4eae-87cf-b14ae6a939b0&amp;displaylang=en" target="_blank">ILMerge</a> to merge all .NET assemblies in one assembly. I used a <a href="http://www.hanselman.com/blog/MixingLanguagesInASingleAssemblyInVisualStudioSeamlesslyWithILMergeAndMSBuild.aspx">blog post from Scott Hanselman</a> on ILMerge for a starter, but although I followed every step in his post, I ran into the following exception: Unresolved assembly reference not allowed: System.&lt;WhatSoEver&gt;. After  a little investigation, I discovered that ILMerge by default does not understand how to merge projects using the .NET 4.0 framework.</p>
<p>Adding an ILMerge.exe.config file with the following piece of code in it solved my problems:</p>
<pre class="brush: xml; title: ; notranslate">
&lt;configuration&gt;
  &lt;startup useLegacyV2RuntimeActivationPolicy=&quot;true&quot;&gt;
    &lt;requiredRuntime safemode=&quot;true&quot; imageVersion=&quot;v4.0.30319&quot; version=&quot;v4.0.30319&quot;/&gt;
  &lt;/startup&gt;
&lt;/configuration&gt;
</pre>
<p></code></p>
<p>This was able to successfully resolve my issue.</p>
</div>
]]></content:encoded>
			<wfw:commentRss>http://dotbert.loedeman.nl/ilmege-unresoled-assembly-reference-not-allowed-framework-issu/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Threading in C# &#8211; complete reference</title>
		<link>http://dotbert.loedeman.nl/csharp-threading-complete-reference</link>
		<comments>http://dotbert.loedeman.nl/csharp-threading-complete-reference#comments</comments>
		<pubDate>Mon, 14 Feb 2011 09:08:35 +0000</pubDate>
		<dc:creator>Bert Loedeman</dc:creator>
				<category><![CDATA[.NET]]></category>
		<category><![CDATA[threading]]></category>

		<guid isPermaLink="false">http://dotbert.loedeman.nl/?p=238</guid>
		<description><![CDATA[A colleague of mine just showed a great complete reference for threaded programming in C#. Since the article is great, I would like to share this one with the world. Here it is: http://www.albahari.com/threading/. Cheers!]]></description>
			<content:encoded><![CDATA[<p>A colleague of mine just showed a great complete reference for threaded programming in C#. Since the article is great, I would like to share this one with the world. Here it is: <a href="http://www.albahari.com/threading/">http://www.albahari.com/threading/</a>.</p>
<p>Cheers!</p>
]]></content:encoded>
			<wfw:commentRss>http://dotbert.loedeman.nl/csharp-threading-complete-reference/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Red-Gate&#8217;s Reflector to be paid for &#8211; free alternatives?</title>
		<link>http://dotbert.loedeman.nl/red-gate-reflector-paid-free-alternative</link>
		<comments>http://dotbert.loedeman.nl/red-gate-reflector-paid-free-alternative#comments</comments>
		<pubDate>Mon, 14 Feb 2011 07:50:21 +0000</pubDate>
		<dc:creator>Bert Loedeman</dc:creator>
				<category><![CDATA[.NET]]></category>
		<category><![CDATA[disassembler]]></category>
		<category><![CDATA[open source]]></category>
		<category><![CDATA[reflection]]></category>
		<category><![CDATA[visual studio 2010]]></category>
		<category><![CDATA[wpf]]></category>

		<guid isPermaLink="false">http://dotbert.loedeman.nl/?p=233</guid>
		<description><![CDATA[Hi folks, I recently discoverd that by the end of February 2011 Red-Gate stops providing Reflector for free. Although their reason sounds obvious (they cannot work for free), I think many developers still rather prefer a free IL deassembler tool. Luckily, Scott Hanselman twittered about free open source alternatives. Those open source alternative IL deassembler [...]]]></description>
			<content:encoded><![CDATA[<p>Hi folks,</p>
<p>I recently discoverd that by the end of February 2011 Red-Gate stops providing Reflector for free. Although their reason sounds obvious (<a title="Red-Gate cannot work for free..." href="http://www.red-gate.com/products/dotnet-development/reflector/announcement" target="_blank">they cannot work for free</a>), I think many developers still rather prefer a free IL deassembler tool. Luckily, Scott Hanselman twittered about free open source alternatives. Those open source alternative IL deassembler projects are both based on the Mono Cecil project.</p>
<p>I would hereby like to share them with you:</p>
<ul>
<li><a href="https://github.com/jcdickinson/Monoflector">Monoflector (WPF)</a></li>
<li><a href="http://wiki.sharpdevelop.net/ilspy.ashx">ILSpy</a></li>
</ul>
<p>Happy coding! Cheers!</p>
<p>PS. Of course I am very much interested in other free alternatives. Please post your comments if any <img src='http://dotbert.loedeman.nl/wp-includes/images/smilies/icon_wink.gif' alt="Red Gates Reflector to be paid for   free alternatives? icon wink" class='wp-smiley' title="Red Gates Reflector to be paid for   free alternatives?" />  &#8230;</p>
<p>UPDATE 04/27/2011: On Twitter I heard @dotnetreflector say to @haacked that they are releasing Reflector v6 with no expiry date for existing users in May 2011! <a href="http://bit.ly/eW3D7O">http://bit.ly/eW3D7O</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://dotbert.loedeman.nl/red-gate-reflector-paid-free-alternative/feed</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>WIX 3.5 &#8211; error LGHT0001: Unable to load DLL &#8216;winterop.dll&#8217;</title>
		<link>http://dotbert.loedeman.nl/wix-3-5-error-lght0001-unable-to-load-dll-winterop-dll</link>
		<comments>http://dotbert.loedeman.nl/wix-3-5-error-lght0001-unable-to-load-dll-winterop-dll#comments</comments>
		<pubDate>Wed, 25 Aug 2010 06:08:53 +0000</pubDate>
		<dc:creator>Bert Loedeman</dc:creator>
				<category><![CDATA[.NET]]></category>
		<category><![CDATA[bug]]></category>
		<category><![CDATA[tip]]></category>
		<category><![CDATA[visual studio]]></category>
		<category><![CDATA[WIX]]></category>

		<guid isPermaLink="false">http://dotbert.loedeman.nl/?p=219</guid>
		<description><![CDATA[It has been a while, but here I am again &#8230; I am currently working on an old Visual Studio 2005 solution. This bugger used to be built by a build server, but that one died about a year ago. Since some bugs really needed fixing, I decided that I would build the project myself for the [...]]]></description>
			<content:encoded><![CDATA[<p>It has been a while, but here I am again <img src='http://dotbert.loedeman.nl/wp-includes/images/smilies/icon_wink.gif' alt="WIX 3.5   error LGHT0001: Unable to load DLL winterop.dll icon wink" class='wp-smiley' title="WIX 3.5   error LGHT0001: Unable to load DLL winterop.dll" />  &#8230; I am currently working on an old Visual Studio 2005 solution. This bugger used to be built by a build server, but that one died about a year ago. Since some bugs really needed fixing, I decided that I would build the project myself for the moment.</p>
<p>Problem was that the solution uses WIX 3.0, and I have WIX 3.5 installed on my machine. After converting the WIX projects I expected the project to build without any problems. Unfortunately, however, WIX crashes with the following error: error LGHT0001: Unable to load DLL &#8216;winterop.dll&#8217;: The specified module could not be found. (Exception from HRESULT: 0x8007007E).</p>
<p>After some searching on the web I found <a href="http://stackoverflow.com/questions/3508239/wix-3-5-fails-under-nant-but-not-under-vs2010">a post</a> (not entirely my problem) with the searched solution: add the installation path of WIX to the Path variable. After this workaround everything works like a charm. Hope this helps you too <img src='http://dotbert.loedeman.nl/wp-includes/images/smilies/icon_wink.gif' alt="WIX 3.5   error LGHT0001: Unable to load DLL winterop.dll icon wink" class='wp-smiley' title="WIX 3.5   error LGHT0001: Unable to load DLL winterop.dll" />  !</p>
<p>Happy coding!</p>
]]></content:encoded>
			<wfw:commentRss>http://dotbert.loedeman.nl/wix-3-5-error-lght0001-unable-to-load-dll-winterop-dll/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

