<?xml version="1.0" encoding="UTF-8"?><!-- generator="WordPress/2.9.2" -->
<rss version="0.92">
<channel>
	<title>Software Matters</title>
	<link>http://pseudosoft.net/blog</link>
	<description>A blog by PseudoSoft.net</description>
	<lastBuildDate>Thu, 18 Mar 2010 20:53:37 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<item>
		<title>Debugging COM with native and managed code</title>
		<description><![CDATA[I was debugging a piece of managed code that communicates with a COM object (an old native piece). I was using Visual Studio 2008.
Things moving along nicely until an exception showed up when initializing the COM object &#8211; System.AccessViolationException.
It took me quite a while to find out that the exception was solely a result of [...]]]></description>
		<link>http://pseudosoft.net/blog/2010/03/debugging-com-with-native-and-managed-code/</link>
			</item>
	<item>
		<title>UNICODE vs. MBCS in Windows</title>
		<description><![CDATA[Everyone seems to have a take on this encoding thing. Here is my 2  cents.
MBCS  has been in use long before UNICODE was born. I view UNICODE was  invented just because there are too many MBCS out there.  I mean, really too many &#8211; different languages, different revisions  within a [...]]]></description>
		<link>http://pseudosoft.net/blog/2010/03/unicode-vs-mbcs-in-windows/</link>
			</item>
</channel>
</rss>
