Recently I have been studying the ASP.Net MVC 3, EF and MVC Scaffolding.

I have been having fun getting these to install on the VS 2010 Web Express Edition.
I started with the ASP.Net MVC 3 installer. This worked.
It includes NuGet (although as I later found out this is v1.2).
I used NuGet to add MVC Scaffolding. This failed to install corrected declaring a dependency upon NuGet 1.4
Eventually I found that if you uninstalled NuGet, downloaded the latest version and installed it as an administrator then it worked.

I also found some other details about the NuGet Package management console. It is simple an embedded version of PowerShell that has full access to your machine.
This means that any unknown command will attempt to use any exe’s on your path.

I was also caught out when I used an empty MVC project as a starting point. I kept on getting resource not found for my main page. I had neglected to add an HomeIndex.

// StoryQ demo

This is a basic demo of using StoryQ.
You need to implement the void methods with wrappers around the system functionality under test.

Note this uses the Given/When/Then pattern as opposed to the normal NUnit Assemble, Action, Assert.

using System;
using NUnit.Framework;

using StoryQ;

namespace Experiments
{

[TestFixture]
public class FirstTest
{

[Test]
public void SunshinePath()
{
new Story(“User Management”).InOrderTo(“Add User”)
.AsA(“Admin”).IWant(“To Add a User to the system”)
.WithScenario(“HappyPath”)
.Given(IHaveEnteredUserName)
.When(IPressSave)
.Then(UserIsAdded)
.And(IAmReturnedToTheMainWindow)
.WithScenario(“UserExists”)
.Given(IHaveEnteredUserName)
.When(IPressSave)
.And(UserAlreadyExists)
.Then(IAmShownErrorMessage)
.ExecuteWithReport();
}

private void IHaveEnteredUserName()
{
throw new NotImplementedException();
}

private void IPressSave()
{
throw new NotImplementedException();
}

private void UserIsAdded()
{
throw new NotImplementedException();
}

private void IAmReturnedToTheMainWindow()
{
throw new NotImplementedException();
}

private void UserAlreadyExists()
{
throw new NotImplementedException();
}

private void IAmShownErrorMessage()

{

throw new NotImplementedException();

}

}

}

NuGet is microsoft’s attempt at a package manager.
It works well for adding open source code to a visual studio project.
You can even host your own local server.

The basic nuget command-line download goes back to the home server to get the latest NuGet.exe which can then be used to obtain other components – even outside of visual studio.

To get the list of items (with a minimal description) you can use:

nuget list -verbose

Some of the projects are a little vague (or personal demos). Most look very interesting.

http://blog.stevensanderson.com/2011/01/13/scaffold-your-aspnet-mvc-3-project-with-the-mvcscaffolding-package/

This looks like an updated version of the castle projects generator project.
This one is powershell and t4 based which is a powerful combination.
Not quite a production “code generation” tool but it’s getting close.

Finally the microsoft camp has caught up with the linux package management tools.
NuGet is a pwershell wrapper around a lot of dependent projects.
You can even have a local NuGet cache.

http://karlshifflett.wordpress.com/xaml-power-toys/

It seems like the ASP.Net MVC people are really making their life easier with scaffolding.
Why don’t the MVVM people in WPF think along the same lines?

It can just be because the ruby on rails people have had scaffolding for years.

var myMock = MockRepository.GenerateMock();
Console.WriteLine(myMock.Execute(“Hello”) ?? “”);

MockRepository mocks = new MockRepository();

var myMock2 = mocks.Stub();
using (mocks.Record())
{
SetupResult.For(myMock2.Execute(“Hello”)).Return(“World”);
}
Console.WriteLine(myMock2.Execute(“Hello”) ?? “”);

I still wonder why mocking frameworks are so popular. Handcrafted mocks seem to do the job quite well and are easy to implement as:

Stub – Ignore inputs and return as little as possible (I frequently return 42 as an integer result)
Spy – Record and log callers.
Saboteur – fail in a controlled fashion (i.e. a stream that will fail with an exception upon the fifth byte read).

If your interfaces are too big then you are not following SOLID properly. If changing the interface causes too many problems then you have not isolated the tests from the code enough (factories and helper methods).

nodejs.com a js server.

This could be useful to ensure abstraction of a service from a technology stack.

james.padolsey.com/jquery