Here are the links from my ignite speech at Agila Sverige.

http://vimeo.com/32447325
http://www.infoq.com/presentations/Leaner-Programmer-Anarchy
http://www.slideshare.net/fredgeorge/programmer-anarchy-chinese

This link was talked about a lot and I think it should have be in there from the start.

http://schacon.github.com/ddd/#1

I got asked to write a post comparing NancyFx and FubuMvc. They are
both great frameworks pushing the .net stack to be even better.

They have many things in common. Both are behavior driven with full control of the pipeline, from request to response, and both are built around an IoC container .

The technical maturity of the projects varies in different areas but both aims to support Mono, Owin and as many IoC and View engines as possible.

I prefer to use both framework. Both have their purpose.

Nancy - Small and simple

NancyFx is built around the “Super-duper-happy-path” and is a simple framework where a route defines what’s going to happen.

Check out NancyFx here: http://www.nancyfx.org

When to use:
Smaller and isolated services/APIs, restfull or html.
Stand alone application or embedded in an application.

Pros
+ Simple. Few moving parts, yet easy to customize.
+ Clear what route leads where. Makes it easy to open a file and see everything that will happen.
+ Easy go get started with. Hello world fits in one tweet (140 chars)

Cons
- When the solution grows complexity will be harder to maintain.
- The use of input and output models is a bit verbose. A trade of due to clear routing.

FubuMVC - Conventions, conventions, conventions

FubuMVC is build to compete with the ASP.NET framework and have been designed to tackle more complex solutions. Routes are built by conventions around handler, input and output models.

Check out FubuMVC here: http://mvc.fubu-project.org/

When to use it:
Complex and medium to large websites.
Complex and large services/APIs. (In this case I would recommend splitting and going with a bunch of instances with NancyFx)

Pros:
+ Build the conventions that fits your needs. This will help you tackle complexity when your solution grows.
+ Tight coupling between font-end and back-end through convention. Makes it clear what in the back end fits together with the backend and vice versa. Ideal for front-end work.


Cons:
- It take a while to get started. You need to understand the how all the conventions fit together.
- To get the full power of the framework you need to learn how to setup conventions to fit your needs.

Conclusion

Both are great frameworks.
The setup I’m working with right now I use FubuMVC for facing the end-users calling down to small and separated NancyFx services.

Were doing an automated restore for running integration tests in a project I’m working on. To make the script easy to use we only wanted to use database name and path to file. Here is the script we ended up with.

Just replace MyDatabase and C:\backups\MyDatabase.bak. Here is the script we ended up with.

IF EXISTS (SELECT * FROM sys.databases WHERE NAME='MyDatabase')
BEGIN
ALTER DATABASE MyDatabase SET SINGLE_USER WITH ROLLBACK IMMEDIATE;
END

declare @logicalName nvarchar(128)
declare @logLogicalName nvarchar(128)


declare @fileListTable table
(
LogicalName nvarchar(128),
PhysicalName nvarchar(260),
[Type] char(1),
FileGroupName nvarchar(128),
Size numeric(20,0),
MaxSize numeric(20,0),
FileID bigint,
CreateLSN numeric(25,0),
DropLSN numeric(25,0),
UniqueID uniqueidentifier,
ReadOnlyLSN numeric(25,0),
ReadWriteLSN numeric(25,0),
BackupSizeInBytes bigint,
SourceBlockSize int,
FileGroupID int,
LogGroupGUID uniqueidentifier,
DifferentialBaseLSN numeric(25,0),
DifferentialBaseGUID uniqueidentifier,
IsReadOnl bit,
IsPresent bit,
TDEThumbprint varbinary(32)
)
insert into @fileListTable exec('RESTORE FILELISTONLY FROM DISK= N''C:\backups\MyDatabase.bak''')

select @logLogicalName = LogicalName from @fileListTable WHERE Type = 'L'
select @logicalName = LogicalName from @fileListTable WHERE Type = 'D'

declare @query varchar(max)
select @query =
'RESTORE DATABASE [MyDatabase]
FROM DISK = N''C:\backups\MyDatabase.bak'' WITH FILE = 1,
MOVE N''' + @logicalName + ''' TO N''C:\localdata\MyDatabase.mdf'',
MOVE N''' + @logLogicalName + ''' TO N''C:\localdata\MyDatabase.ldf'',
NOUNLOAD,
REPLACE,
STATS = 10'

exec (@query)

ALTER DATABASE MyDatabase SET MULTI_USER