Upgrade ASP.NET 1.1 .aspx file to be viewed normally on IE9 or Chrome.

Question

0.00/5 (No votes)

See more:

An Intranet(yes, Intranet) application developed 10 years ago by ASP.NET 1.1. Now, the application's some controls cannot be seen or fail to work in IE9. Considering to just rewrite the aspx file (.cs file cannot be recode) or Javascript so the page can work normally in IE9 or Chrome.
I wanna to get your suggestions on the following questions:
1, Because it's an Intranet within a company, we can choose IE or Chrome. So, which browser is easier(or better) when we decide to modify the .aspx or Javascript file to suit the new browser;
2, Can we successfully rewrite .aspx file with HTML5 and CSS3 or Javascript/jQuery so the page can work normally on IE9 or Chrome?
3, Do we need to upgrade the IIS?

Any other suggestions?

Thanks in advance.

Posted 13-Mar-14 4:04am

wusir371

Updated 13-Mar-14 15:40pm

v2

Add a Solution

Comments

[no name] 13-Mar-14 10:26am

You have to figure out what exactly is not working. Is it some 3rd party library like telerik, infragistics, ajax control toolkit ? If yes, then try to upgrade them to latest version. I have done it in 3-4 projects with good results. It will give you a starting point but you still have to fix issues as they come.

wusir371 13-Mar-14 21:31pm

Thanks. I have just get the description from client and have not see the error. Maybe it's the problem of JS, not HTML or CSS.

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)

Christian Graus · Answer 1 · 2014-03-14T13:18:00

If you think IIS might need upgrading, then you clearly have no idea what you're doing :-)

You need to fix the HTML in the pages, which probably means code you wrote, more than code generated by the framework. Your best bet is probably Chrome, because the debug tools are better, so you can better work out why it's not working and then impliment fixes. As someone else said, if there are third party libraries, they may need updating. You could try changing the target to a newer version of .NET and seeing what happens, too. You can also decompile the dll if you don't have the source pages, but if you don't, for an intranet app, then the people you're working for are clearly morons, so I'd expect more problems down the road ( who pays for something to be written and doesn't make sure they have the source code ? )