I have the need to pick up the MVP pattern for my job, so that means a lot of the new HardwawreArmory features are going to be designed using that pattern.

I can only think of one task, currently, that will be "Hello World" easy and that will be the creation of new computers (and accessories) since it is mostly data->form->data and doesn't require too much fanciness.

The only challenge I see is that the IHardware interface that all of the Hardware components use as a contract are going not going to be easy to integrate as they don't really work as a View the way they are designed.

There are a few benefits to this pattern:

1. Test Driven Development makes more sense. No code is written until I have created my tests. I could do this now, but it doesn't fit my current development flow.
2. Seriously separated concerns. UI is nothing but UI (Model). View is nothing but functionality (View). And the Presenter is the object handed between the two (Presenter).
3. I will learn this pattern which should be a good feeder into MCV (or just upgrading to a framework designed to assist MVP like Castle).

I think that I am going to start to put code snippets in here.

I worked all night long and was finally able to get the site up and running with SqlMembershipProvider instead of my home-grown solution.

Why?

1. It integrates really well with a lot of available applications written in .Net.
2. It is a well-received standard.
3. The heavy lifting is handled by the time-tested framework.
4. It is just THAT MUCH less code that I have to maintain.
5. I really like the administration (roles, specifically) interface that it gives me.

Now that I am starting to expose my WCF services to the world, I wanted to make sure that my login interface uses a standard of some kind. I will probably also upgrade to OpenID or something similar in the very near future as a secondary option to creating an account on my page.

Another cool benefit to my using SqlMembershipProvider is that it gave me a chance to re-evaluate how I was handling accounts in general. Previously, I was requiring lots of information to create an account. I simplified that down to simply take the email, username, password. I may have to integrate a CAPTCHA once people really start using the site to keep things spam free, but am at a stopping point for the login engine as of now.

I am going to use this blog to keep everyone (who cares) up to date with the features that are currently in brainstorm, development and beta.

I don't expect that I will want to spend the time required to truly get every feature documented via blog, but I will try to capture the majority of the features I feel are important.