Windows Identity Framework Signing out

When using claims based security and you implement the sign out functionality do not forget to delete the sessions cookie... otherwise when playing around with the back button you are able to sign in again... this is something you don't want...

	public class AuthenticationController : Controller
	{
	ILogger _Logger = NullLogger.Instance;
	public AuthenticationController(ILoggerFactory loggerfactory) {
	loggerfactory.Create(Loggers.Security);
	}
	[AllowAnonymous]
	public ActionResult Index()
	{
	return View();
	}
	//To trigger redirect to login
	[Authorize]
	public ActionResult SignIn()
	{
	return RedirectToAction("Index", "Home");
	}
	public void SignOut()
	{
	WsFederationConfiguration fc = FederatedAuthentication.FederationConfiguration.WsFederationConfiguration;
	string request = System.Web.HttpContext.Current.Request.Url.ToString();
	string wreply = request.Substring(0, request.Length - 7);
	SignOutRequestMessage soMessage = new SignOutRequestMessage(new Uri(fc.Issuer), wreply);
	soMessage.SetParameter("wtrealm", fc.Realm);
	SessionAuthenticationModule sam = FederatedAuthentication.SessionAuthenticationModule;
	if (sam != null) {
	_Logger.Debug("Calling SessionAuthenticationModule signout");
	sam.SignOut();
	sam.DeleteSessionTokenCookie();
	}
	WSFederationAuthenticationModule fam = FederatedAuthentication.WSFederationAuthenticationModule;
	if (fam != null) {
	_Logger.Debug("Calling WSFederationAuthenticationModule.Signout()");
	fam.SignOut();
	}
	_Logger.InfoFormat("Signed out. Redirecting...");
	Response.Redirect(soMessage.WriteQueryString());
	}
	}

view raw AuthenticationController.cs hosted with ❤ by GitHub

Loading ....

MVC: Intellisense for custom HtmlHelpers or if you want to avoid @using to import namespaces

If you write custom HtmlHelpers its quite tedious to have to add @using your.namespace.to.your.htmlHelpers on top of each page. To be able to use your newly written htmlhelpers

to avoid this just find the web.config in your views folder and locate the following section:
<system.web.webPages.razor>
        <host factoryType="System.Web.Mvc.MvcWebRazorHostFactory, System.Web.Mvc, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
        <pages pageBaseType="System.Web.Mvc.WebViewPage">
            <namespaces>
                <add namespace="System.Web.Mvc" />
                <add namespace="System.Web.Mvc.Ajax" />
                <add namespace="System.Web.Mvc.Html" />
                <add namespace="System.Web.Optimization"/>
                <add namespace="System.Web.Routing" />
                <add namespace="SharpSolutions..MvcApplication.Helpers.BootStrap"/>
                <add namespace="SharpSolutions.MvcApplication.Helpers"/>
            </namespaces>
        </pages>
    </system.web.webPages.razor>

and add your custom namespace to it.

After you have done this reload your mvc project (or close Visual Studio and reopen it).

Windows Azure Logging not working Trace.TraceError throws: Not running in a hosted service or the Development Fabric.

I had the following line in my web.config:

<system.diagnostics>
    <trace>
      <listeners>
    <add type="Microsoft.WindowsAzure.Diagnostics.DiagnosticMonitorTraceListener, Microsoft.WindowsAzure.Diagnostics, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
   name="AzureDiagnostics">
     <filter type="" />
    </add>
      </listeners>
    </trace>
  </system.diagnostics>

After removing this: it created WAWSAppLogTable as expected.
More info can be found here: www.windowsazure.com


for local debugging I left the line untouched... I created a new config transformation where I added:

<system.diagnostics>
  <trace>
   <listeners>
    <add name="AzureDiagnostics" xdt:Locator="Match(name)" xdt:Transform="Remove" />
   </listeners>
  </trace>
 </system.diagnostics>

Which is quite logic since Azure websites is not hosted in the AppFabrik

Team Foundation 2012: Run xUnit unit tests

Currently I am using https://tfs.visualstudio.com/ and writing my unit tests with xUnit. To enable this follow the steps outlined on MSDN.


You can find the binaries in the packages folder in your solution directory