Yes you can execute sprocs with EF Fluent API Code Only

OK let’s make this clear. You can totally call SQL Functions, SQL SPROCS, or any other raw SQL statement and use it in EF Code Only. What you don’t get is automatic or fluent API configuration statements that perform this mapping work for you and by default, no tracking occurs on the materialized objects (though…

1

Yes, you CAN use "firm" XAML Services in AppFabric

First of all, I don’t actually have a better term for tradtional use of XAML compiled as part of an assembly (BAML format) other than to coin the term “firm” XAML in response to the now common term, “loose xaml” (.xamlx files). If you have a better term, come tell me, OK? So the purpose…


Map private properties with EF Fluent API

So until we get EF 4.2 and the support for enumerations as first class citizens those of us needing support have resigned ourselves to the simple fact that we are forced to expose a property for the integer value for EF to use and wrap that value with a convenience property that casts it as…

3

Specifying Specific Dependencies with Windsor Fluent Registration

So it’s become apparent that the documentation (actually concrete examples in my personal opinion) for Windsor Container are a little lacking in the area of showing people how to indicate a specific component instance registration for depenency injection. At least once a week I get an email on the topic asking my “how-to” knowledge. After…


SQL Tip of the Day

HAd this passed to me from the SQL Tips DL here at the ‘soft and decided to repost it here to 1. remember about it and 2. share the tidbit INSERT MULTIPLE RECORDS WITH TABLE VALUE CONSTRUCTOR Author: Saleem Hakani (Microsoft Corporation)   Wouldn’t it be nice to have the ability to insert multiple rows…

2

Windsor Container Series

It’s no secret that I am a fan of Windsor Container. Here’s a really great series of Advanced Windsor Container Tricks posts that I am linking here for reference Registering Delegates  & A Delegate Factory Facility Auto registration How to resolve arrays How to register and use decorators The Startable Facility The EventWiring Facility How…


Silverlight, Faults, and HTTP Status Codes

So plenty has been written about the mismatch in between the Silverlight browser plug-in and WCF messaging with fault use cases over HTTP. For those of you that didn’t know about this then here’s your chance to catchup: According to the documentation, SOAP faults are not supported in the WCF client implementation for Silverlight (even…


Using reflection to determine if an event is static

So if you happen to have an EventInfo class and need to determine if the event is static or instance, it isn’t actually immeidately clear if this is supported. Most of the MemberInfo basic types expose a property named IsStatic that indicates if this member is static or not. If you’ve ever worked with the…


Interested in POCO Entity Framework 4?

Editorial note: EF 4.1 was released as part of the .Net 4 Platform Update 1 release. You should use the information at http://blogs.msdn.com/b/adonet/archive/2011/04/11/ef-4-1-released.aspx for training now. For those of you interested in POCO In EF4, here’s a list of links that you should read to grok: http://blogs.msdn.com/b/adonet/archive/2009/05/21/poco-in-the-entity-framework-part-1-the-experience.aspx http://blogs.msdn.com/b/adonet/archive/2009/05/28/poco-in-the-entity-framework-part-2-complex-types-deferred-loading-and-explicit-loading.aspx http://blogs.msdn.com/b/adonet/archive/2009/06/10/poco-in-the-entity-framework-part-3-change-tracking-with-poco.aspx http://blogs.msdn.com/b/adonet/archive/2009/06/16/using-repository-and-unit-of-work-patterns-with-entity-framework-4-0.aspx http://blogs.msdn.com/b/adonet/archive/2009/06/22/feature-ctp-walkthrough-code-only-for-the-entity-framework.aspx http://blogs.msdn.com/b/efdesign/archive/2009/08/03/code-only-enhancements.aspx http://blogs.msdn.com/b/efdesign/archive/2009/10/12/code-only-further-enhancements.aspx And if you are…


Making exception messages meaningful

Now that’s a great exception message. I think we all can take a clue from the Castle team when it comes to making exceptions meaningful. Instead of next time effectively saying “something went wrong” with our exceptions, really spell out exactly why it went bad and if possible, how to correct it.   Big ups to…