When we add either the site column or content type to a list the managed metadata field works and shows up in the search refinement panel (at least it did in my testing).
At least in my testing when we create a list definition this isn’t all wired up correctly and the following steps were required.
This and the following step is often missed out in other articles but cause problems if you try to create custom list definitions that include the managed metadata column. The problem stems from the fact that Share Point is looking for an associated note (i.e.
Sidenote: you want to remove the /Lists/ prefix from the URL when creating document libraries to avoid breaking the default column values feature.
You will also want to add in the file dialog view as it goes missing when using the Visual Studio 2010 tools.
section to the field and hardcode the various Id’s that define a term set (required if you are using a sandboxed solution), or configure these in code.