@@ -94,22 +94,22 @@ <h3>The Provider Demo </h3>
9494 < h3 > Interesting classes and methods</ h3 >
9595 < h4 > Relying party</ h4 >
9696 < ul >
97- < li > DotNetOpenId .RelyingParty.< b > OpenIdRelyingParty</ b > - programmatic access to everything
97+ < li > DotNetOpenAuth.OpenId .RelyingParty.< b > OpenIdRelyingParty</ b > - programmatic access to everything
9898 a relying party web site needs.</ li >
99- < li > DotNetOpenId .RelyingParty.< b > OpenIdTextBox</ b > - An ASP.NET control that is a bare-bones
99+ < li > DotNetOpenAuth.OpenId .RelyingParty.< b > OpenIdTextBox</ b > - An ASP.NET control that is a bare-bones
100100 text input box with a LogOn method that automatically does all the OpenId stuff
101101 for you.</ li >
102- < li > DotNetOpenId .RelyingParty.< b > OpenIdLogin</ b > - Like the OpenIdTextBox, but has a
102+ < li > DotNetOpenAuth.OpenId .RelyingParty.< b > OpenIdLogin</ b > - Like the OpenIdTextBox, but has a
103103 Login button and some other end user-friendly UI built-in. Drop this onto
104104 your web form and you're all done!</ li >
105105 </ ul >
106106 < h4 > Provider</ h4 >
107107 < ul >
108- < li > DotNetOpenId .Provider.< b > OpenIdProvider</ b > - programmatic access to everything
108+ < li > DotNetOpenAuth.OpenId .Provider.< b > OpenIdProvider</ b > - programmatic access to everything
109109 a provider web site needs.</ li >
110- < li > DotNetOpenId .Provider.< b > ProviderEndpoint</ b > - An ASP.NET control that you can
110+ < li > DotNetOpenAuth.OpenId .Provider.< b > ProviderEndpoint</ b > - An ASP.NET control that you can
111111 drop in and have an instant provider endpoint on your page.</ li >
112- < li > DotNetOpenId .Provider.< b > IdentityEndpoint</ b > - An ASP.NET control that you can
112+ < li > DotNetOpenAuth.OpenId .Provider.< b > IdentityEndpoint</ b > - An ASP.NET control that you can
113113 drop onto the page for your own or your customers' individual identity pages
114114 for discovery by Relying Parties.</ li >
115115 </ ul >
0 commit comments