Split into more granular `cef.sdk` e.g `cef.sdk.vs201x`

[jornh]

Copied over to a new issue here from #4 (comment):

I think this one is actually quite hard. It's not that easy, not at all. Ideally, I would want it to work like this (and no, this is NOT a short-term goal):

• CefSharp and CefSharp.Core being compiled for Any CPU.
• Depending on the current bitness of the process being run, it would load the CEF binaries dynamically (i.e. no normal reference, but rather by means of LoadLibrary or similar).

The user (of CefSharp) would then not have to care about what bitness they are using. CefSharp would just be smart enough to load the right (unmanaged) binaries as needed.

Wouldn't that be quite cool? If you agree, make this an issue on the CefSharp repo please, and we can then plan it for some future release. It's definitely doable.

So, whatever steps we take here should preferably align with that future roadmap, if possible. I guess that means one single package, or CefSharp depending on both the x86 and x64 packages. But hey - should we perhaps take it even one step further and split depending on VS version...? I mean, to have cef.sdk.vs2010.x86, cef.sdk.vs2013.x64 and so forth? It gives us a lot of packages, but the individual packages becomes much more manageable. It also has the advantage of people like you and @brock8503 being able to contribute/build a package for your specific VS version, and I can then add the VS2010 and VS2012 bits... for example.

Food for thought. What do you think? The difficulty then would just be of course to make the CefSharp dependencies be correct...