Skip to main content

Posts

Showing posts from September, 2013

Speed up your delivery

Tools & Technology for Quality and fast Development, Code Documentation and Testing  Resharper 8(Licensed) 1.    Analyze code quality-On-the-fly code quality analysis in C#, VB.NET, XAML, ASP.NET, ASP.NET MVC, JavaScript, CSS, HTML, and XML. ReSharper tells you right away if your code contains errors or can be improved. 2.    Code editing helpers-Multiple code editing helpers including extended IntelliSense, hundreds of instant code transformations, auto-importing namespaces, rearranging code and displaying documentation. 3.    Eliminate errors and code smells- Instant fixes to eliminate errors and code smells. Not only does ReSharper warn you when there's a problem in your code but it provides quick-fixes to solve them automatically. 4.    Comply to coding standards- Code formatting and cleanup functionality is at your disposal to get rid of unused code and ensure compliance to coding standards. 5.    Code Generati...

Client side(Jquery/Javascript/CSS) coding convention and best practices

Type Standard / Convention Example Linting Use JSHint to detect errors and potential problems.   Recommended to have nodejs (with npm). Install node-jshint from the command line for automatic linting. node-jshint automatically discovers the closest .jshintrc file and uses it. Or http://jshint.com/ (may produce different results due to absence of jshintrc settings)   Whitespace This will help to enforce to follow particuler coding convention     Blank lines separate one block of logically related code from another.   One space on both sides of binary operators and assignment operators.   Keywords followed by a " ( " (left parenthesis) must be separated by one space.   There should be no space between the function name and left parenthesis of the argument list. This gives visual distinction between keywords and function invocations.   Clos...

Claim Based Identity - My findings......

Claims - Benefits  Why we should go forClaim based Identity(defining identity+authorization+authentication), let's have look on couple of noted points which very known: • Claims-based authentication is not just white (authenticated) or black (unauthenticated). It allows for a whole level of shades of gray. This is where claims augmentation comes into play where, depending upon the level of access you need, you can provide additional claims. • Claims can be stacked on top of each other. What this means is multiple users with different kinds of authentication can participate on the same web application. • Claims are Internet ready. Because they use algorithms such as RSA, they are extremely secure and trustable even when you cannot talk to the IP-STS directly. • Claims do not care about the platform. They are an open standard that everyone understands. • Finally, there is a complexity surrounding many different kinds of authentications. For instance, if our SharePoint s...