Commit updates done to investigate https://rdotnet.codeplex.com/workitem/89 (resolved as not an issue)
Merge latest BMC repo master, and create a branch to work on
Commit before (re?)merging BMC master.
Commit before (re?)merging BMC master.
Intermediary commit, getting the nuget dependencies on track
Merge remote-tracking branch 'bmc_master/master' into rdotnet_1.5.11

Conflicts:
	tests/Test.RProvider/packages.config
Get RProvider to compile against R.NET 1.5.11 and Rdn.Fs 0.1.4
Update year
Merge branch 'master' of https://github.com/BlueMountainCapital/FSharpRProvider into rdotnet_1.5.11
Merge branch 'master' of github.com:BlueMountainCapital/FSharpRProvider
Add  type provider for reading RData files (close #59, replace #85)

This implements `RData` type provider that can be used for reading RData
files in a statically typed way. The provider infers the types of the fields
by using the default conversion (if there is one available). More details
are available in the newly added documentation file.

Aside from the RData provider, I also updated F# Formatting (and the default
templates), added generated API reference (and tweaked a few things so that
it looks nice) and also updated F# Data reference to keep things up-to-date.
Adopt latest R.Net for concurrency fixes

The latest R.Net 1.5.12 and RDotNet.FSharp 0.1.5 include concurrency
fixes that resolve issue #64. They might also resolve RInteropServer
disconnection issues that have been seen, though this will take some
further testing to verify.
Use nuget packages for R.NET 1.5.12
Merge branch 'feature/new-RDotNet' of https://github.com/dcharbon/FSharpRProvider into rdotnet_1.5.11

Conflicts:
	nuget/RProvider.nuspec
Remove superseded R.NET references
Add tests for RData reading and writing
Register InteropServer as a well-known singleton

Issue #86 is caused by the server object being gc'd at the server. This
can be prevented by registering the server object as a
WellKnownServiceTypeEntry and specifying that the service be provided as
a singleton. This guarantees that the lifetime of the server object will
be the lifetime of the server process.
Merge pull request #90 from dcharbon/feature/prevent-disconnection

Register InteropServer as a well-known singleton
Adopt latest R.Net for concurrency fixes

The latest R.Net 1.5.12 and RDotNet.FSharp 0.1.5 include concurrency
fixes that resolve issue #64. They might also resolve RInteropServer
disconnection issues that have been seen, though this will take some
further testing to verify.
Incorporate feedback from @tpetricek

Removed locking from RInteropServer. Removed all references to
C_StackSize since the RDotNet default is what is needed. Fixed
RWrapperGenerator.fsproj so that it doesn't use elements not supported
on Mono. Remove unnecessary reference to DesignTime assembly in Tests.
Improve exception forwarding for RInteropServer

When an exception is thrown during the execution of a method in
RInteropServer that exception cannot be returned to the client unless it
is serializable. All methods now wrap their behavior in a try statement
that catches all exceptions and grabs the message from non-serializable
exceptions to re-raise as a serializable exception.