Michael James - Developer

Recently I blogged about using DotNetOpenAuth , I got it working within my local MVC3 Web Application after fixing the dependency issue however when I came to put it into Windows Azure I was getting a random error when the compute emulator started up. --------------------------- Microsoft Visual Studio --------------------------- Windows Azure Tools for Microsoft Visual Studio There was an error attaching the debugger to the IIS worker process for URL 'http://127.255.0.0:82/' for role instance 'deployment16(174).xxxxxxxxxxx_IN_0'. Unable to start debugging on the web server. See help for common configuration errors. Running the web page outside of the debugger may provide further information. Make sure the server is operating correctly. Verify there are no syntax errors in web.config by doing a Debug.Start Without Debugging. You may also want to refer to the ASP.NET and ATL Server debugging topic in the online documentation. Nice! How confusing, the...

Today I started integrating OpenID into my latest web application. I chose to use the DotNetOpenAuth  library as a helper, it's top and makes Open ID really easy, supports Web Forms, MVC and even classic  ASP. Anyhow there are many how too guides, including one from my good friend Danny Tuppeny , so when it comes to setting it up I refer you to those. However today I found when I was using the AsActionResult extension method my web page would come back blank with just  DotNetOpenAuth.Messaging.OutgoingWebResponseActionResult written on screen. For some reason the ToString was being called and returned. Commonly it seems that the issue is caused by not having a binding redirect for older versions of the MVC assembly  however my one was set, but what I did notice was the following: <dependentAssembly>         <assemblyIdentity name="DataAnnotationsExtensions" publicKeyToken="358a5681c50fd84c" culture="neutral" /> ...