Hi Kevin, there isn't really an equivalent to GetMap in the current project - though it seems like a big omission.
As a quick fix you could do something along the lines of what FObermaier suggested - though you may need to lock the bitmap while reading and writing and also return a clone rather than the original bitmap.
The DrawToBitmap method should be fine.
We are trying to refactor the v2 tree to be more useful in a whole range of rendering scenarios both interactive and not, so we should be able to get equivalent functionality to GetMap in the long run.
As a rule all the providers work in the same way - some expose the Oid type as a generic type param and the MsSqlServer2008 provider is one such;
so if your database table has an oid(primary key) of type bigint you would use MsSqlServer2008Provider<Int64>. The constructor arguments are fairly self explanatory and you can get an instance of an IGeometryFactory from the GeometryServices utility.
The DefaultProviderProperties property is a hack to enable you to force the usage of particular db indexes as the query planner can get things terribly wrong at times
The provider will work much quicker if the database has a few things such as a Geometry_Columns table, envelope columns and spatial indexes on the spatial table.
There are static utility methods on the MsSqlServer2008Provider class to aid in the creation of these but far easier is to use the FormatConverter project to load the data in the first place.
(make sure the project has been built a couple of times as various dlls need to be copied around as part of the build process)
The 0.9 code you posted above looks like it came from a web type project; the equivalent in v2 is to subclass SharpMap.Presentation.AspNet.Handlers.[Async]MapHandlerBase or SharpMap.Presentation.AspNet.WmsServer.Async.WmsHandlerBase
see SharpMap.Presentation.AspNet.Demo.NoCache.DemoMapHandler as an example of what needs to be overriden for a non-wms handler. A combination of IMapRequestConfig and the associated IMapRequestConfigFactory are used to set
like the output image size and map extents from parameters in the querystring/ database or wherever.
Unfortunately with all things web, you run the risk of being severely bitten by the GDI renderer which breaks under any sort of load, hence the intended change to agg. There are also a couple of fixes in the desktop which haven't made it into the web
yet (todo with view matrix transformations).
Got to go and get back to a 4 day old baby ;) but I will try and help where I can cheers jd