Asp.net 2.0 dynamically HTML rendered differently on server 2012 (IIS)

Question

0.00/5 (No votes)

See more:

I have a strange problem.
Hopefully someone has an easy and very logical explanation on this 

The web based system is a course enrollment system.

An ASP.NET 2.0 site has been moved from Windows 2003 server (IIS) to a new Windows 2012 server (IIS).
After this potation a dynamically generated HTML file is rendered differently on the new 2012 server. A checkbox on 2003 server becomes a text box on the 2012 server.

What I have tried:

We have been investigating the ASP.NET code on both servers and this is identically. But the dynamically generated HTML pop up box is slightly different on the 2012 server. Below I have inserted the HTML code for both versions. It is the ID “6154” that is set (correctly) to type “checkbox” on 2003 server and wrongly to type “text” on 2012 server.

Windows 2003 Server:
====================
<input id="CH6156" type="checkbox" name="CH6156" /><label for="CH6156">

Windows 2012 Server:
====================
Bekræft *<input name="DF6156" type="text" maxlength="1" id="DF6156" class="INPUT" style="width:100px;" />

Because it is dynamically generated I cannot change the HTML file (the pop up box) This pop up box is new for every course and the person must confirm the she has read the “general terms” by setting a check mark in the check box.

We have done a lot of testing.
If the source code in the HTML is changed so it refers to the old 2003 server, a rerun of the Course9999.HTML is rendered correctly.
If the source code in the Course9999.HTML is changed so it refers to the new 2012 server, a rerun of the file now displays a text box.

We have checked that websites on both 2003 server and 2012 server runs .NET Framework 2.0.50727.
The REGESTRY on both servers has been investigated and there is a little difference in how the versions are displayed. I have no access to the servers at the moment so I cannot checkup if it is as simple as a missing NET Framework SP2 on the new server.

I was inspired to dig into this matter by this article https://support.microsoft.com/en-us/kb/318785

Posted 22-Aug-16 0:51am

MadsBorik

Updated 22-Aug-16 0:59am

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Patrice T · Answer 1 · 2016-08-22T00:59:00

Obviously, something behave differently on both servers.
The only solution is to use the debugger on both servers to see where the code don't behave the same. You will probably see that there is a point where it don't do the same.

You should learn to use the debugger as soon as possible. Rather than guessing what your code is doing, It is time to see your code executing and ensuring that it does what you expect.

The debugger allow you to follow the execution line by line, inspect variables and you will see that there is a point where it stop doing what you expect.
Debugger - Wikipedia, the free encyclopedia[^]
Mastering Debugging in Visual Studio 2010 - A Beginner's Guide[^]
http://docs.oracle.com/javase/7/docs/technotes/tools/windows/jdb.html[^]
https://www.jetbrains.com/idea/help/debugging-your-first-java-application.html[^]

The debugger is here to show you what your code is doing and your task is to compare with what it should do.
When the code don't do what is expected, you are close to a bug.