Refactoring into core, web & winrt projects. Unfinished

A core project for common messaging and sending, and two separate
projects, one to implement sending http exceptions (as current) and the
other for sending WinRT exceptions (without using System.Web). Currently
a broken w.i.p
Moved back into two projects, using preprocessor macros

to keep the unsupported stuff out of the WinRT project. This will result
in two libraries for the user to choose from with the core + web code in
the main project
WinRT library now POSTs exception correctly

Both class libraries now coexist, are built correctly (using json.net)
and the output binaries can be used in both wpf and winrt projects. The
MessageDetails that contain the RaygunRequestMessage are still used and
sent with the wpf/winforms/asp.net library, but the WinRT lib doesn't
send anything for this.

I think we might need another object to convey information when the
exception is sent from a desktop project, as opposed to the web stuff in
RaygunRequestMessage?
Tidying up
Ensured WinRT UnhandledExceptions are posted; added Wrap methods

so users don't have to place try-catch blocks around everything, instead
they pass their code to those Wrap methods which executes it and sends
exception + throws if their method fails
Added RaygunEnvironmentMessage, sends system data

From a desktop-like environment. Confirmed works from WPF projects,
presumably WinForms and console apps too. Partial WinRT implementation,
more to come
Added CPU architecture info for WinRT msgs
Merge pull request #22 from MindscapeHQ/core-web-winrt

Core web winrt