You may want to save the current code to be able to revert this setting. Otherwise you may need to delete this Search Core Result Web Part and place an new one, which will bring these default values again.

Now you should see the XML-Version of the Search Result, including your new “Managed Properties”.

You can also use, of course, these new “Managed Properties” as so called “Search Refiners”, as well in the Search Refiner Web Part” on this Search Result Page, as you can use the Managed Properties as new keyword for searches in the Search Textbox:

Now here comes the point:

I tried to remove my new “Managed Properties” from the “Fetched Properties” settings in the Search Core Result Web Part.

What I expected was, that my new fields then would not appear in the XMl-Output anymore.

BUT THEY DID!

Developer often ask: “Why doesn’t my result show up?”, this time I asked myself: “Why DOES my result show up?”

I had no idea.

I made quite a looooooooooooot of chance here and there, but still. The fields showed up for no known reason.

A expert-friend BTW speculated, that they (the new Managed Properties” fields might have found their way into to default configuration, which can be made for the Search Core Results in the Central Administration.

Default Values for the Search Core Result Web Part in the Central Administration:

BUT: they were not there, because I did not put them their (I did not even knew this settings), and SharePoint does not THAT much magic, as one may believe. Sometimes :-)

So still I asked myself: Why do my fields show up, although I did have them entered anymore in the “Fetched Properties” settings?

Another assumption could have been, that the “Managed Properties Cache” could have something to do with this.
There are very little details about what the “Managed Properties Cache” actually is – and does.
But it seems, that this did not help, either.

Additional tests gave me the – somehow “strange” reason – and led towards the solution:

The solutions lies in the fact, that they were also entered in the “Search Refinement Panel” Web Part.

This surprised me a lot, because of the fact, that these Web Parts do “just the following to provide themselves with date and to build the output:

They all just sneak at the URL of this page and do what they have to do. I did not see a reason, why one Web Part would know what the other do.

But in fact, they DO!

The reason for this lies in another setting of these Web Parts, which everyone may occasionally have seen, but never spend more attention: the “Cross-Web Part query ID”

I already knew, that when one was placing MORE “Search Core Result Web Parts on one page, on has to turn off their connection using this setting.

I had no idea that also this setting exists in the “Search Refinement Web Part”!

So when removing my new “Managed Propertes” from the “Filter Category Definition” field, or changing the “User Query” id to another value then my “Search Core Result Web Part, where I still have the XML-Output set, will finally lead to the result, that these “Managed Properties” vanish from the XML output.

So finally I got back the feeling, having control over what happens here :-)