Index containing types from DynamicContentModelsAssembly (13.2.8)

Mattias Olsson

Vote:

I have started seeing weird types in the index:

MyProject.Web.Features.Product.Models.DefaultVariationContent_DynamicProxy, DynamicContentModelsAssembly

I also have the correct type indexed, which is:

MyProject.Web.Features.Product.Models.DefaultVariationContent, MyProject.Web

Might this be a bug? If not, how can I get rid of those DynamicProxy types?

#227526

Edited, Sep 07, 2020 7:36

Mattias Olsson

Vote:

Just saw this:
https://world.episerver.com/support/Bug-list/bug/FIND-8423

However, we see this for EPiserver.CMS.Core 11.14.2 as well.

#227527

Edited, Sep 07, 2020 8:17

Mattias Olsson

Vote:

We are now on Episerver.CMS.Core 11.20.2 and Episerver.Find 13.3.0 but I can't get rid of these weird types. I clear the index but they keep re-appearing and filling up the index. Only happens on staging though which is a bit strange. Same code and package versions as production.

#246622

Edited, Jan 11, 2021 8:02

Quan Mai

Vote:

It looks like this has something to do with the recent IL generator changes. I will ping CMS core team so they can take a look. Thanks for bringing this into our attention

#246626

Jan 11, 2021 9:19

Mattias Olsson

Vote:

Thanks Quan. Do you have any news on this? This is the index in our staging environment right now. The weird thing is that it does not happen on production, any ideas why?

#247442

Jan 22, 2021 8:46

Quan Mai

Vote:

Hi - I reached to Johan, and this is what he wrote

Hmm, that sounds weird, especially that it just happens in one environment. It almost sounds like that environment runs with an older version. Could it be that they have e.g. a local instance running somewhere with older packages (e.g. on a developer box) that is configured to use the same find enviroment, I am thinking that it might then be the local instance that triggers the indexing job locally and then pushes the data to the index

#247443

Jan 22, 2021 8:57

Mattias Olsson

Vote:

I don't think we have any developer machine configured to use the staging index. The thing is that the invalid entries are added when the indexing job is triggered from the staging server as well.

#247457

Jan 22, 2021 10:44