<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Problem with Aspose.word: System.AccessViolationException</title>
	<atom:link href="http://www.coderetard.com/2008/03/19/problem-with-asposeword-systemaccessviolationexception/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.coderetard.com/2008/03/19/problem-with-asposeword-systemaccessviolationexception/</link>
	<description>Anything Geeky Goes!</description>
	<lastBuildDate>Sun, 21 Mar 2010 21:45:05 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: romank</title>
		<link>http://www.coderetard.com/2008/03/19/problem-with-asposeword-systemaccessviolationexception/#comment-87</link>
		<dc:creator>romank</dc:creator>
		<pubDate>Wed, 02 Apr 2008 02:10:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.coderetard.com/2008/03/19/problem-with-asposeword-systemaccessviolationexception/#comment-87</guid>
		<description>Aspose.Words 5.1 is now out that definitely does not have this problem.

Basically a third party obfuscation tool was at fault. It would produce some builds that would run on 64bit and some that would fail.

When we&#039;ve released 5.0.2 we didn&#039;t test the release on 64bit (like we did with 5.0 and now with 5.1). Now we have resolved the obfuscation problem and will also run every release on 64bit too.

This is the 5.1 release post  http://www.aspose.com/community/blogs/aspose.words/archive/2008/03/28/aspose-words-5-1-0-released.aspx</description>
		<content:encoded><![CDATA[<p>Aspose.Words 5.1 is now out that definitely does not have this problem.</p>
<p>Basically a third party obfuscation tool was at fault. It would produce some builds that would run on 64bit and some that would fail.</p>
<p>When we&#8217;ve released 5.0.2 we didn&#8217;t test the release on 64bit (like we did with 5.0 and now with 5.1). Now we have resolved the obfuscation problem and will also run every release on 64bit too.</p>
<p>This is the 5.1 release post  <a href="http://www.aspose.com/community/blogs/aspose.words/archive/2008/03/28/aspose-words-5-1-0-released.aspx" rel="nofollow">http://www.aspose.com/community/blogs/aspose.words/archive/2008/03/28/aspose-words-5-1-0-released.aspx</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
