Random Thoughts

I wrote a set of directives that make validation in AngularJS a tad simpler. The directives are available at https://github.com/technovert/angular-validation I have detailed about the directives on my company website http://blog.technovert.com/2014/03/angularjs-form-validation-library-directives/ and there is also a jsfiddle to play with http://jsfiddle.net/3vxgy/1/ or

I recently blogged about some common pitfalls using AngularJS on my companies blog. Anyone interested in the details should visit my post at. http://blog.technovert.com/2014/02/common-pitfalls-angularjs/ You can also subscribe to my feed here Happy Reading :)

We recently released a Project Template for ASP.Net MVC and AngularJS here and here . I did a follow up post detailing how the project template has been setup and how to make AngularJS and MVC play well together on my company blog . If you are interested in understanding how the template works head over to my blog post and read it!

I am very exited to announce that our team at Technovert has release a Visual Studio project template for AngularJS . More details on how to install and use this template are available on the Technovert Blog   Knockout.js has been a standard library that .Net devs have been using for creating rich interactive business apps. But AngularJS from Google provides a more complete framework and is gaining a lot of dev community support. This project template can help you get up and running with AngularJS in no time and evaluate it for your future needs.

Recently Robin Ward did a comparison between AngularJS and Ember (both the post and the comments are interesting read). One of the complaint that Robin had that AngularJS does not provide any specialized model class. As described in the blog There is no standard Model base class, nor is there a component or interface in AngularJS that defines what a model is supposed to be. What that means is that anything defined on $scope can acts as model, as this sample on the blog describes For some (like me) this is the flexibility where as for others who want a more structural approach this is a nuisance.AngularJS does not even provide any definite guidelines around how the model should be actually designed to be effective with AngularJS This leads to what we call as $scope pollution. We define multitude of properties on the $scope object and managing it becomes difficult.  Looking at the code one cannot tell what is the actual model and what properties are just to support UI log

If you play around with IIS Url Rewriting rules and try to do redirects on an HTTP POST you loose your POST data. To make sure you get the post data you have to set the `redirectType` to `Temporary` within your rules. So the action configuration looks like this <action redirectType=" Temporary " type="Redirect" url="http://{HTTP_HOST}{REQUEST_URI}"> </action> You may think what scenario warrant a POST request redirect. We faced one such scenario while doing SSO with a federated Identity Provider (IP)  such as Google, Azure AD. In federated authentication scenario once the user is authenticated by the IP, it redirects back to your site with claim tokens in a POST request over secure channel (https). In our case we wanted to redirect to user back http after receiving the request. But any redirects were causing loss of token. By doing a 307 (Temporary) redirect we were able to preserve the post data.