Annotating Entity Framework classes

A golden oldie which I seem to need to lookup everytime I use it: the MetadataTypeAttribute.

When using entity framework to generate POCO classes for my applications I frequently run into the problem that I want to annotate the fields in order to utilize MVC Client-Side validations. The POCO classes are generated so they cannot be modified with loosing the changes upon a refresh of the generated code. The MetadataTypeAtribute offers a solution. Since all generated classes are partial classes we can add a partial class and adorn it with the MetadataTypeAttribute. The attribute points to a new class which mimics the EF class and provides data annotation to describe the rules and properties of each property.



Example IsJsonRequest()

While doing some ASP.NET MVC Json programming today I discovered there is still no standard extension method for checking whether a request specifically wants a Json result.

I wanted to support both the mime type as well as a ‘format’ parameter in the url.

Here is the extension method I wrote:

public static class JsonRequestExtensions
    private const string format = "format";
    private const string json = "json";
    private const string jsonMime = "application/json";

    public static bool IsJsonRequest( this HttpRequestBase request )

        bool isJsonRequest = ( IsRequestedFormatJson( request ) == true
                               IsRequestedMimeTypeJson( request ) == true );

        return isJsonRequest;

    private static bool IsRequestedMimeTypeJson( HttpRequestBase request )
        if ( request.AcceptTypes != null )
            return request.AcceptTypes.Any( t => t.Equals( jsonMime, StringComparison.OrdinalIgnoreCase ) );
        return false;

    private static bool IsRequestedFormatJson( HttpRequestBase request )
        return String.Equals( request[format], json, StringComparison.OrdinalIgnoreCase );

What version of SQL Server are you running?

I needed to know the exact version of our SQL Server installation (in order to determine if test and production were the same). Turns out there is a superb script posted on TechNet to do just that.

You can download it here:

It generates output like this:

--//Your current Microsoft SQL Server information:
Product Version:          12.0.2269.0
Product Name:             SQL Server 2014
Product Level:            RTM + Security update(GDR)
Product Edition:          Developer Edition (64-bit)
Note, if you want to know information about CU, you need to intall
SQL Server 2014 RTM Cumulative Update 10. CU10, <>
                                                  – see KB3094220 to get the Cumulative Update 10
Support Lifecycle stage: Mainstream Support Phase. For additional information refer to, and Q6, Q18
in the FAQ section of Support Lifecycle page at:
Full information:
Microsoft SQL Server 2014 - 12.0.2269.0 (X64) 
	Jun 10 2015 03:35:45 
	Copyright (c) Microsoft Corporation
	Developer Edition (64-bit) on Windows NT 6.3  (Build 10586: ) (Hypervisor)

--//Recommended updates: 
--### RTM -> QFE or GDR
--### SP  -> QFE or GDR
--### QFE -> QFE
--### GDR -> GDR or QFE
Install the latest service pack:              SP1, <>
Install the latest Cumulative Update (CU) of SP1:  CU6, <>
###### QFE branch updates
12.0.2548 (SQL Server 2014 RTM QFE)
###### GDR branch updates
12.0.2254 (SQL Server 2014 RTM GDR)
12.0.2269 (SQL Server 2014 RTM GDR)
12.0.4213 (SQL Server 2014 SP1 GDR)
Note, if you don’t want to upgrade to latest service pack right now, we recommend you install the latest
Cumulative Update CU13 of SQL Server 2014 RTM.
Install the latest Cumulative Update (CU) of RTM: CU13, <>

--//You can upgrade to any of the following product(s):
SQL Server 2016 Enterprise
SQL Server 2016 Business Intelligence
SQL Server 2016 Standard
SQL Server 2016 Web
SQL Server 2016 Developer

For additional information about supported version and edition upgrades refer to:

(1 row(s) affected)


What does CSV stand for?

Just had someone ask me why I was calling a file a CSV file. My reply: It is a comma separated file. Which made us wonder: why the V and not an F.

Turns out the V is for the Values in the file 🙂
CSV is a simple file format used to store tabular data, such as a spreadsheet or database. Files in the CSV format can be imported to and exported from programs that store data in tables, such as Microsoft Excel or OpenOffice Calc. CSV stands for “comma-separated values“.