<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://www.softec.org/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Migrating to 64-bit Windows: Getting Your Executables and Services to Run 32-bit Components</title><link>http://www.softec.org/blogs/central_coast_code/archive/2010/01/18/migrating-to-64-bit-windows-getting-your-executables-and-services-to-run-32-bit-components.aspx</link><description>When migrating to a 64-bit Windows Server, one of the things a developer has to consider is how to continue to use any 32-bit COM components that they might have referenced in their applications. A common example would be any file uploaders or data encryption</description><dc:language>en</dc:language><generator>CommunityServer 2008.5 SP2 (Build: 40407.4157)</generator></channel></rss>