mvc – 0 vote against What is the step by step to leave the globalization in the design of identily?

I have found this question Translate the validations of Asp.Net Identity users did not talk step by step of how to change the identization globalization.

I am using ASP.NET Identity to control the authentications in my application, the validations possible with DataAnnotation I am already doing but all the validations are in the standard in English and I would like to be able to translate them. For example, in the following code, when I try to create a user and it already exists in the bank, it returns the validation "Name xxxx is already taken." How can I proceed? I can give an override in the CreateAsync method too, but I do not know the behavior of the method.

If, EN 2.2.1 5.2.3 3.1.
I placed the globalization in webconfig and it did not work.

I'm putting the controller code, to understand a little what I mean and the method I'm using. On the occasion after creating the login you are automatically performing the login in the application. as follows:

private ApplicationSignInManager _signInManager;
private ApplicationUserManager _userManager;



public async Task Register (RegistrarViewModel model)
var user = new ApplicationUser {UserName = model.UserName};
var result = waitit _userManager.CreateAsync (user, model.Password);
if (result.Succeeded)
wait _signInManager.SignInAsync (user, isPersistent: true, rememberBrowser: false);

return View ("Login", "Account");
foreach (var error in result.Errors)
ModelState.AddModelError ("", error);
return View (model);
Edition 7/03 at 19:42

Vainer Cesario
Galera was an error of mine, I'm using a DDD architecture and isolei my Identity layer in CrossCutting. Effective globalization must be in the Identity project and not the UI.