Virtual app directory hosted sites will now get the right realm to allow easy RP discovery.
See Google Code Issue 86.
...so that strong-name signed versions of this assembly still work under partial trust environments. See Google Code Issue 14.
Fixes Google Code issue 86.
…n the query string but don't provide a value for it.
This required a small fix to Util.NameValueCollectionToDictionary. Fixes Google Code Issue 81. Thanks to richertech for the report and suggested fix.
Fixes Google Code issue 56. Conflicts: src/DotNetOpenId.TestWeb/ProviderEndpoint.aspx.cs Removed the whitelist reference that broke the build.
For some reason the xml membership provider must be mentioned as default even though the aspnetsql one didn't.
…provider. This ends the problems where MDF/LDF file updates from SQL, even when the database didn't change, would keep locking up the revision control system.
Fixes Google Code Issue 78.
Conflicts: (version number difference between branches left out of merge) src/DotNetOpenId.Test/Properties/AssemblyInfo.cs src/DotNetOpenId/Properties/AssemblyInfo.cs
Lesson learned: Uri.ToString() and Uri.AbsoluteUri are NOT the same thing. Uri.ToString() decodes the URL to make it easier to read. Uri.AbsoluteUri leaves the encodings alone, which is important if you're doing anything with the Uri.
… tested against domain.com. Also added several new wildcard tests.
As described in Google Code Issue 71, some other OpenID implementations have issues when a return_to implies a port and realm explicitly gives the same one, or vice versa. This change addresses the issue by attempting to be consistent across return_to and realm URLs by always implying ports that may be implied rather than explicitly specifying them sometimes.