Why is the .rdlc report different in different environments?

Question

I have a project in Visual Studio that uses .rdlc reports. After processing all the data, it displays the output in the form of a report on a web page. However, I get the problem in terms of rendering / formatting.

Problem

When I start the localhost environment (IE11 is the main browser), the report is visualized as intended and displays the result as follows:

However, when I run the program on the dev development environment web server (also in IE11), I get the following error:

As shown in the figure, in the dev environment, report subtitles go at the top of the table header when it reaches a new line.

What have i done so far?

1) I compared the versions of IE that ran in localhost and dev. Both of them ran in the same IE11 browsers. Which excluded my theory, unlike the version of IE browser.

2) I ran the localhost and dev environments in different browsers (Chrome, Firefox). The localhost and dev environment reports are displayed properly in these browsers, which eliminates another browser theory.

3). Based on the conclusion I made below, I did some research, and the next post was the closest I could achieve.

Generally

After completing the above steps, I noticed that only the dev environment in IE11 generates a header error (second image). This led me to the conclusion that this is due to the rendering of IE11. This bothers me even more, because the local environment works in IE11, which displays correctly (first image) .

Question

What causes this error? Why does IE in dev behave differently than localhost?

Ultimately, is there a way to fix this error? If so, what should I do (add / remove files to the dev environment, write lines of compatibility code somewhere)?

EDIT

After some additional research, I found this question , but this question has never been answered. I tried looking for suggestions in the comments, but to no avail.

EDIT 2

I tried to add a meta tag to the parent view file, it did not solve the problem.

<meta http-equiv="X-UA-Compatible" content="IE=edge" /> 

It also does not help when I add the following lines to web.config

 <httpProtocol> <customHeaders> <add name="X-UA-Compatible" value="IE=edge" /> </customHeaders> </httpProtocol> 

Answer 1

The main reason I caused the problem for me is because it works in compatibility mode. Disabling the first flag in the compatibility view settings solved the problem for me.