Dotnet 3.5 support

[akmad]

Hello,

I recently discovered the MvcMiniProfiler and love it but then noticed that it is .Net 4.0 only. Here is a simple attempt to remedy that. My goal was to have as minimal an impact on the existing code as possible and thus I centralized most of the changes into the DotNet35Support.cs file.

The major changes are:

1. Created two new project configurations, NET35-Debug and NET35-Release, that target .Net 3.5 for the MvcMiniProfiler, MvcMiniProfiler.Wcf, and MvcMiniProfiler.Tests projects.
2. Updated the MvcMiniProfiler project file to use the correct references based on the .Net Framework target.
3. Created the IConcurrentDictionary<TKey, TValue> interface and updated the SqlProfiler type to use it rather than the ConcurrentDictionary that is only included with .Net 4.0.
4. Created the MiniConcurrentDictionary<TKey, TValue> type. This type is a very simple synchronized dictionary implementation for the 3.5 version, but should suffice for the required usage. The 4.0 version is simply a subtype of System.Collections.Concurrent.ConcurrentDictionary.

I don't think the other changes are particularly notable and should be self-explanatory. Building a version that targets the 3.5 framework is as simple as changing the configuration to NET35-Debug or NET35-Release and building normally.

Note that I did not update the EF, LinqToSql, or sample projects to support 3.5 as that was out of the scope of my needs.

I hope this is helpful!

[SamSaffron]

I am not against this in principle, just needs careful review

[akmad]

I completely understand; if I can be of any assistance please let me know. Likewise, let me know if you notice any bugs or poor design decisions and I'll fix them.

Thanks!

[RoryBecker]

I'm also really interested in seeing a 3.5 SKU of this project.

[akmad]

@RoryBecker As far I know, my personal fork works fine in 3.5; though I have not been keeping up with any changes to the core project.