Getting, "No new content found in dynamic xap" after updating

notice that the fillingmodule is loading fine but the systemmodule is not. I have tried everything I can think of to see what is different about the SystemModule from the FillingModule and the other 3 that are loading fine and I have not come up with anything. There is no errors in the output and we are not messing with any search patterns as suggested here:

http://www.ideablade.com/forum/forum_posts.asp?TID=4207&PID=16526&title=ideabladecorecompositionpartscatalogloadcatalog-no-new-content-found-in-dynamic-xap-modules-custommodulexap-exported-viewmodel-instance-not-available#16526

Any ideas about what could be going wrong? We are using the CocktailMefBootstrapper and pretty much running it with everything as default. I also tried adding it as a reference in the main xap and the MEF still didnt pick it up. My only guess is that it is named System so it gets ignored but other than that I have nothing.

Not a bug, but following are the default IgnorePatterns to make sure we are not probing .NET system assemblies. If you name your assembly System.dll it's being ignored, because it machtes the "^System.*" pattern.

The IgnorePatterns are not new, but we've added new patterns over the years. You can also modify the list of ignore pattern. The discovery mechanism in DevForce is documented here: http://drc.ideablade.com/devforce-2012/bin/view/Documentation/discovery

We recommend for many reasons to adopt an assembly naming scheme that puts your own assemblies into its own namespace. Something like Company.AssemblyName.dll.