Software And Architecture

I ran into a situation today wherein I was required to debug the Google Authentication middleware built on top of OWIN. I already had the code checked out from Katana project in CodePlex. However, when I tried to use, it was the latest bits [dev channel]. My app was using the version 2.1 and the dev version was in 3.0. Tired of searching the tag for the version 2.1, I came to know that the symbols for the various open source projects are made available from SymbolSource.org Given this piece of information, I read the steps on how to configure the symbol server in Visual studio and then upon successful source registration, I was able to step through the middlewares and do the debugging stuff. Things that I did were, Grab the public [authentication less uri access] from Symbol Source [ http://srv.symbolsource.org/pdb/Public] Go to Tools -> Options -> Debugger -> General. Uncheck “Enable Just My Code (Managed only)”. Uncheck “Enable .NET Framework source stepping”.

Glad that Microsoft announced that it pursues open source technology through https://msopentech.com. Lot of projects are developed here which enables to serve as a bridge between Microsoft and non-microsoft technology. Looking forward for some very interesting proceedings in msopentech.

The following code snippet can be used to run the IIS Express [8.0] in my case to be run from the command line. The parameters are the path to the main directory, the target libraries [dll's] should be in a folder  called as “bin” inside this given path for the IIS to pick up and run. The other parameter is the “port” which specifies which port should IIS Express listen for the incoming request. It also logs in the requests and the response status etc in the command line. Sample : c:\Program Files\IIS Express>iisexpress.exe /path:”C:\Users\Saravanan\Documents\Visual Studio 2012\Projects\console_app_in_iis\console_app_in_iis” /port:8089

This post illustrates the compatibility of OWIN with the existing technologies MVC5 requires ASP.NET/IIS but can co-exist with OWIN components. MVC is tightly coupled to ASP.NET, hence not standalone with respect to OWIN WebApi is fully OWIN compatible In order to find out where your app is loaded from, use “AppDomain.CurrentDomain.SetupInformation.ApplicationBase”  The stage markers apply to OwinHttpModule, not OwinHttpHandler

Windows AppFabric Caching Here is a collection of links that are useful for kickstarting the use of Windows AppFabric Caching, formerly known as Velocity Caching from Microsoft. Tutorials Concepts and Architecture Physical Architecture Diagram Logical Architecture Diagram AppFabric Caching Concepts Caching Admin in Windows PowerShell -- Saravanan