DISQUS

If I can get the thing to launch again to get repro steps, I'll definitely file a bug. Thanks.

That's really cool, you guys have come a long way! I tried out MonoDevelop on the Mac earlier tonight and it's (as you mentioned) a bit flaky. What I saw looked pretty good though.

1) in your screenshot I see the menu in the OS X Menu bar, but when I run it it's embedded within the window itself, is this a setting?
2) when rearranging my toolbar panels (I only like 1 level, if that) I got into a state where the mouse couldn't drag one of the items up. The drag position was offset about 400 pixels from the mouse position...

I'm still doing some .NET development with VMWare Fusion / Win XP / Visual Studio 2008, but I am interested in trying out a pure-mac environment to see if I can even do it. Looks like we're not far away from that :)

You gonna convince the main office to do a nice, cool, BigVisibleCruise project for these? ;)

I was able to generate my tables at runtime like this:

protected void Application_BeginRequest()
{
TableStorage.CreateTablesFromModel(typeof(Models.BlogContext));
}

You can't do it in Application_Start because some stuff must not be loaded in time. In App_BeginRequest you can do it, and subsequent calls will be ignored (it won't erase your data).

You can sometimes do away with the overloads if they become too cumbersome by applying the parameter object pattern.

GetGroupMembers( new GetGroupMemberOptions { GroupId = 52, Page=1, PageSize=20 });

it does affect readability, but you can use that to give you optional parameters & generally more control over the method signature.

Sweet! Mine is here:

<img src="http://avatar.xboxlive.com/avatar/subdigital/avatar-body.png" />

Very cool! I generally abstract out my email service behind an interface and use a FileBasedEmailService for testing, but this looks like a really good way to test actual SMTP.

+1

The project template is only part of the solution. I'm thinking of extending the wizard that exists today.

Re: ViewEngine - When I said "you shouldn't" I didn't mean you can do it the way I suggested. I meant you should poke the team and ask them if they can add this. :)

I think this is a great first step. It's opinionated, which is fine, and it allows people to hit the ground running, which is really powerful.

I share the notion that entities should _probably_ be in a separate dll, which enforces things like persistence ignorance. Also for my apps, we have many web applications share a common set of libraries, which you have baked in here. "90% of web apps" seems way too high to me (though I do agree with you in principal... most apps are too complicated).

In the future I'd like to see the File->New Project wizard go something like this:

-Name of project
-Create Test Project?
-nunit/mbunit/mstest (I think these templates should ship w/ the product)
-Which View engine?
- webforms
-nvelocity
-brails
-nhaml (again, these should ship)
-Entities/services/data access included? if not create separate projects, prompt for names
-DI framework
-StructureMap
-Windsor
-Ninject
-Spring
-Logging? (great idea)
NLog / log4net / EntLib


Another point of feedback... you shouldn't have to create your own view engine implementation if you just want to change the folder structure. You should be able to set those properties on whatever current view engine is in place.

Opinionated is good, but ultimately you'll get flamed for the choices you make :) I'm also thinking that this "uber-wizard" would probably be annoying and confusing to the beginner.

Maybe an MVC Template Generator where you decide these things once and it packages it up into a project template?

The Database comparison tools in DB Pro really aren't migrations. If you're looking for that, check out my post comparing some .NET Migrations here:
.NET Database Migration Tool Roundup

The Schema Comparison tool cannot help you when you are deploying a volatile change, such as adding a new NOT NULL column to a table that has existing data. You have to customize the script. It doesn't handle refactorings where you change the datatype of a column. Again you have to futz with the script.

Migrations capture the evolution of the database and applies these changes safely and in order.

Also I'd like to plug RedGate's SQL Compare, which is far better than DB Pro's Schema Comparison. It does cost money, but then again so does DB Pro.