I thought I would start a page on some interseting side effects I come accross when playing with the content types in a document library feature:

Try this:

  • Create a document library feature and remove the content types from the schema.xml file.
  • Now activate the feature on a site and browse to the new document library.
    • Click the "New" dropdown and you will see that a content type with the same name as your document library is available :)
  • If you create a instance of this document library that has content type bindings, then you will not have this problem.