Hello Marco,

VERY interesting and helpful article. It is very difficult to find online resources about ASP.NET Identity and IoC/Ninject.

One question please about Phase 4, can you make ApplicationSignInManager and ApplicationUserManager private variables?

Also, can you mock ApplicationSignInManager and ApplicationUserManager using Moq for Unit Testing? If yes, what is your approach? Do you use something like this:

var store = new Mock<IUserStore<ApplicationUser>>(MockBehavior.Strict);

and then create an instance of the Controller like this var controller = new AccountController(new UserManager<ApplicationUser>(store.Object));

You Used the term ' constructor injection' is it the same as 'dependency injection'?

PS: You can write in Italian as I understand it perfectly. I just am ot very good in writing it.

Thank you for the very prompt reply!

Point 1 and 3 are clear but point 2 is killing me from the inside :)

To give you an idea I wish to implement some Unit Test like the answer provided in the link http://forums.asp.net/t/1993211.aspx?Mocking+the+IUserStore+UserManager+and+MOQ and yet keep ApplicationUserManager as my UserManager class. Any Ideas or suggestions how can I mock ApplicationUserManger?

Do I need to implement IApplicationUserManger? Or do I make the Controller use UserManager<ApplicationUser> in the constructor instead of ApplicationUserManager? If yes, can you provide examples? (Still a bit green in IoC and Mocking)

Continuing with my last post ... Since ApplicationUserManager also requires IdentityFactoryOptions can I just use

new IdentityFactoryOptions<ApplicationUserManager>()
{
DataProtectionProvider = Startup.DataProtectionProvider
});

in my test project?

I will try out and leave a comment once I manage to implement a solution. Who knows maybe it help others too!

Thanks a lot for your kind assistance for now! :)