Silverlight 4 has some new ways for validate input values (some new approaches to implement validation in your application). First approach is DataAnnotation. In this case you should describe validation rules with attributes. Two other ways (both of them is came with Silverlight 4) – you should implement one of interfaces for your ViewModel: IDataErrorInfo or INotifyDataErrorInfo. I want to talk about all of these approaches, about pros and cons of using each of them. Goal of this article to get a best way to implement validation of input values in my and your applications. This part of article about DataAnnotations.

Background
I have example. I want to describe all of these approaches on simple control “change password”.




Read more: outcoldman

Links to this post

Tags: Security, Silverlight

• Cognitive application awareness
• Visual insight into the interaction between your database and application code.
• Analysis and detection of common pitfalls when using NHibernate.
• Analysis is delivered via perfectly styled SQL and linkable code execution.
• Supports NHibernate 1.2.x, 2.0.x and 2.1.x

Introduction

NHibernate Profiler is a real-time visual debugger allowing a development team to gain valuable insight and perspective into their usage of NHibernate. The product is architected with input coming from many top industry leaders within the NHibernate community. Alerts are presented in a concise code-review manner indicating patterns of misuse by your application. To streamline your efforts to correct the misuse, we provide links to the problematic code section that triggered the alert.
Within the Learn section we will demonstrate how simple it is to set up your application profiling within NHibernate Profiler for the first time.
We are providing a 30 day trial to download and see for yourself, the value you will receive with your purchase of NHibernate Profiler.

Read more: NHibernate Profiler

Links to this post

Tags: NHibernate

• Cognitive application awareness
• Visual insight into the interaction between your database and application code.
• Analysis and detection of common pitfalls when using LLBLGen Pro.
• Analysis is delivered via perfectly styled SQL and linkable code execution.
• Supports .Net 3.5 and .Net 4.0

Introduction
LLBLGen Profiler is a real-time visual debugger allowing a development team to gain valuable insight and perspective into their usage of LLBLGen. The product is architected with input coming from many top industry leaders within the OR/M community. Alerts are presented in a concise code-review manner indicating patterns of misuse by your application. To streamline your efforts to correct the misuse, we provide links to the problematic code section that triggered the alert.
Within the Learn section we will demonstrate how simple it is to set up your application profiling within LLBLGen Profiler for the first time.
We provide a 30 day trial to download and see for yourself, the value you will receive with your purchase of LLBLGen Profiler.

Read more: LLBLGen Profiler

Links to this post

Tags: Programming

Converting SVN to Mercurial, while keeping all the commit history, might sound like a hard thing to do, but in fact it isn't! This functionality is already built into Mercurial, it’s just not enabled by default.
I will be using BitBucket as the Mercurial repository host for this example. You will also need the latest version of TortoiseHg.
Conversion is done using the command hg convert, however the Convert extension is not enabled by default. To enable it, locate the file Mercurial.ini, typically located in your %UserProfile% drectory (C:\Users\<username> in Windows 7). Open it in Notepad, and locate the following section:
[extensions]
Add it, if it doesn’t exist. Directly below the section name add the following line:
hgext.convert=
Save the file, and open a command prompt. Type hg convert, and if the output shows usage for the convert options, it means that the extension was enabled successfully.
To begin converting, simply type:
hg convert C:\YourProject
Where YourProject is the SVN root of your project. Mercurial will create a new directory, appending the suffix –hg (e.g. YourProject-hg), and will use it as a destination. Please note that this may take a long time, depending on the size of your SVN repository.

Read more: Typemock