CompCreator - DynamicComponents compatibility

Now, is the moment to ask @Taifun why splits this thread in few new threads, if two "small" questions but different subjects ( CompCreator.Remove component and DynamicComponents.Remove id a subject-related questions with a quick "Solution" possibility) vas joined on this thread.

And of course, ask Taifun why close that thread as the answer to the subject question was not responded to, and it generates a lot of adjacent subjects (that BTW can be split in many other threads) from which, at least I learned a lot? The only one who posted in that thread (if I remember correctly), a subject-connected opinion, was @ewpatton (thank you ewpatton for your oppinion), and the subject doesn't have a solution... Yet (as you easily can see I'm working on it...).

I'm far from being a genius in software but from my knowledge, Google has something that Google named SEO. In the SEO chapter, this wonderful community has earned excellence in Google indexing. So...

If I search on Google for DynamicComponents.Remove id or CompCreator.Remove component those "small" but subject-related questions and those questions have separate title-related-subject, in the Google search will be the first place.

If the above subject-related questions are joined in another subject (in that case with the title CompCreator - DynamicComponents compatibility), from my point of view, will not have the same priority on the Google index (SEO policy).

From my point of view, separating "small" subject-related threads in independent threads offers SEO advantage and the possibility to mark "Solution" quickly.

The above is just an opinion that I argued from my point of view. I don't want to offend anybody, I want to make your work and my work simpler and more efficient.

Thank you. Dan

PS - The opinion on the above questions will be a reference for my future posts.