bondsbw

Great job!

Any chance this will lead to Mercurial integration?  It would seem easy to do given the similarities with git.

I was about to make the same comment as contextfree`.  I might go one step further and automatically save as I go.

I also feel that JamesB's comment was insightful.  I think your data entry forms have the appropriate information density, but that the "summary" views and other read-only views should be more information rich.  The result is more clicks and more pages, which in medium or large LOB apps would cause the user to lose context and get lost.  It's almost too much even in this small app.

The app is boring.  I feel that many Windows 8 apps are this way.  I suppose that developers fear what Microsoft would think if they used more than two colors.  And I don't like the inconsistency in the color scheme.  The summary screens use a light overall background, and dark tiles with light text.  Then, data entry screens use a light background with dark text.  I would make the summary screens have a darker background, and then use that with light text for data entry.  (Or, do the inverse if you would rather have dark text on light backgrounds.)

Agreed... very nice, short and sweet.  Channel 9... seriously... do this MORE!

Nice!  Now, if you could convince the C#/CLR guys to add this to the next release, so that the DLL generation was unnecessary...

In other words, I would like it if you could change the syntax of that added line of code to something like:

override get DateTime.Now = () => new DateTime(2000, 1, 1);

Agreed with sokhaty.  As it stands, how exactly is this different from a counting semaphore?

Click-to-Run?  Sounds awfully similar to the Click 'N Run service from Linspire.

Come on Microsoft... first you sue because Lindows sounds too much like Windows, then you turn around and do the same to them.

Thanks Glenn.

Do you (or anyone) know if there is work on a custom ExportProvider for CommonServiceLocator containers?  I've found this:  http://commonservicelocator.codeplex.com/Wiki/View.aspx?title=MEF%20Adapter.  But it looks to only expose MEF's container as a CSL.

Thanks again!

Brandon

I may have missed something at some point, but when did the ability to hook into another IoC container get added?  This has been a hot topic for MEF, and I didn't see anything about it in the release notes.

Regardless, does this mean that I can use (for instance) Windsor as the back-end container for MEF, and it would give Windsor the ability to discover plugins and compose based on the Import and Export attributes in MEF?  If so, this is great news!  We had just decided to drop MEF in favor of rolling our own plugin discovery with Windsor... maybe we don't have to anymore.

The one thing Microsoft doesn't quite seem to get: simplicity.

A search page also needs to:

• Be fast
• Get out of the way
• Not look like something from MySpace