Add RemoveTypeHint with not existing type name
Result: InvalidOperationException "Type 'SomeTypeName' is not found."
I think that remove already removed type (or type that not existed at all) is safe action
asked Aug 29 '14 at 02:30
It's complicated situation. There are two cases (or maybe more than two): 1)type was removed on previous upgrade and DO can skip that hint (your case) 2)user types name of type incorrectly and DO must tell him about that
And DO don't know which one in this time. And if DO will try to resolve this situation then user may receive unexpected result. DO expects that all hints, which user defines, have correct parameters (type name in this case). And DO only validates them to make sure that all actions with those parameters will finish correctly.
You can check that type exists in extracted model when you add some hint. Use UpgradeContext.ExtractedDomainModel or UpgradeContext.ExtractedTypeMap for that.
answered Aug 29 '14 at 07:28