Why are the SpatialToolStrip and SpatialStatusStrip obsolete_

Not only are the SpatialToolStrip and SpatialStatusStrip obsolete, they haven't been supported since the first official release v1.0. They was left in version 1 only to help those that had used a prerelease version migrate to the first official release. They will be removed in v2.0.

Because these controls were a significant part of the prerelease versions, there are, naturally, questions that have arisen.

Why Was SpatialStatusStrip Replaced?

SpatialStatusStrip implemented IProgressHandler, which allows the framework to communicate progress updates to the user. Unfortunately, it required the developer to perform quite a bit of setup, such as adding a label control and progress bar control. It was also somewhat difficult to use if more than one label control was desired (for example, to display coordinates). Instead of overhauling this control, a new arrangement was made, using the extension framework.

Why Was SpatialToolStrip Replaced?

SpatialToolStrip provided a menu and toolbar system. Since some applications used it and others used a ribbon control, pages of code were required for extensions to add menu items. IHeaderControl was added to provide additional flexibility and improve conciseness of code.

I want to drop a control on my form (I don't want to add a dll)

If the built-in functionality doesn't meet your needs, you are always free to drop a ToolStrip or StatusStrip on your form and start from there.
If you like a legend and map interface and don't need to worry about the default layout, you can Customize the Branding of MapWindow 6

I'm just trying to display a simple map inside my application

In this case, you may only want to set the MapFunctionMode to Pan. The user will be able to use their mouse to pan and the scrollwheel to zoom. If you want them to have additional options, you are free to drop a ToolStrip or StatusStrip on your form and add the desired functionality.

What is recommended for GIS applications?

We recommend that you use the extension framework, because of the added flexibility. There are many examples that do this:

DemoMap
HydroDesktop
MapWindow 6

You no longer need to drop a toolstrip on your form and wire a map to it. Just drop the MenuBar dll in your plugins folder. The MenuBar dll includes instructions to add a number of useful buttons to your header control (ribbon or menu). If you would like to help localize the MenuBar, help us translate DotSpatial.Plugins.MenuBar.

How to Support Loading Extensions (Loading GDAL)

How to Add Support for Loading DotSpatial.Plugins.Ribbon

How to Load DotSpatial Extensions Into My Toolbar

Composing an Application by Combining Extensions

Getting started with MEF (Managed Extension Framework)