<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://weblogs.asp.net/utility/FeedStylesheets/atom.xsl" media="screen"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en"><title type="html">Lance Olson</title><subtitle type="html">Building distributed/network apps with .NET</subtitle><id>http://weblogs.asp.net/lanceo/atom.aspx</id><link rel="alternate" type="text/html" href="http://weblogs.asp.net/lanceo/default.aspx" /><link rel="self" type="application/atom+xml" href="http://weblogs.asp.net/lanceo/atom.aspx" /><generator uri="http://communityserver.org" version="3.0.20510.895">Community Server</generator><updated>2004-02-20T10:33:00Z</updated><entry><title>How does .NET use the certificate store when working with client certificates?</title><link rel="alternate" type="text/html" href="http://weblogs.asp.net/lanceo/archive/2004/02/20/77186.aspx" /><id>http://weblogs.asp.net/lanceo/archive/2004/02/20/77186.aspx</id><published>2004-02-20T18:33:00Z</published><updated>2004-02-20T18:33:00Z</updated><content type="html">&lt;P&gt;We occasionally see questions around how to best use client certificates from middle-tier ASP.NET or Windows service applications.&amp;nbsp; I added a &lt;A href="http://weblogs.asp.net/lanceo/articles/77182.aspx"&gt;certificate store article &lt;/A&gt;today which describes&amp;nbsp;how Web services, .NET Remoting, and System.Net.HttpWebRequest interact with the various certificate stores on the machine.&lt;/P&gt;&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=77186" width="1" height="1"&gt;</content><author><name>LanceO</name><uri>http://weblogs.asp.net/members/LanceO.aspx</uri></author></entry></feed>