I have renamed a load of my classes and change their MetaClassName in code. I have compeltely cleared my catalogue and tried deleting these meta classes that no longer exist and although they say deleted as soon as I restarted IIS they are back. Due to this they are coming up as availible types in the catalogue when trying to add items on the MainCatalog.
Is there some way of actually making these go away?
How did you go about trying to delete the meta classes?
For the catalog classes they should be stored in [commercedb].[dbo].[MetaClass].
Does it contain your new classes?
Does your old ones disappear from that table when you try to delete them?
I see what the problem is, they are actually my base types that my commerce items are inheriting. It's creating meta classes for these base types when they don't have a CatalogContentType on them which is different to how the CMS models work. Do you know how to stop this?
Would decorating them with the attribute and setting AvailableInEditMode to false at least remove them from the types that can be created? Commerce always seems to work just a little bit different than the normal CMS models?
Can you provide an example on your implementation of your catalog classes?
Both the base class and the actual implementation you are using?
Thanks I've figured out what it was, some of my new base types I'd forgotten to make abstract and therefore commerce was generating items for these. Now I've marked the base types as abstracted and cleaned them out all is good.
Thanks for the council :-)
Indeed, abstract is even better