How to convert HTML TO ASP .NET

Question

3.33/5 (3 votes)

See more:

I have a website that is static html, now i need to apply user login etc on it... is there any easiest way to do so... there are more than 300 html pages i need to change...
if i could convert the whole into aspx files with codes and master page which holds all the authentication process.....?????

Posted 14-Jan-12 7:22am

psychic6000

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)

Sergey Alexandrovich Kryukov · Accepted Answer · 2012-01-14T18:15:00

Solution 1

First of all, the question itself has very little sense and shows the lack of understanding of APS.NET and HTTP and Web applications in general. There notion of "conversion" makes no sense in principle, and the desire to make a static site to dynamic itself has no sense. If a site is static, it means its content is static and the properties of it are static. It is self-sufficient and does not need to be "converted". A real ASP.NET site should have completely different content, otherwise doing it does not make any sense.

I want to give any hint though. You should start adding some ASP.NET pages to existing site, not trying to "convert" everything. Gradually, you would move some pages to ASP.NET part, and only the pages which should be functionally changed. Better yes, gradually add new pages, and later remove obsolete static pages, but only when the integrity of the site is not disrupted.

—SA

Posted 14-Jan-12 18:15pm

Sergey Alexandrovich Kryukov

Comments

psychic6000 15-Jan-12 1:12am

thanks for the reply...
i actually need a software that reads the html tags and updates that into asp tags, also adding default site master... i thought if i could find any...
actually its university project, and it had to be static, so we made it on html, now instructor says to apply some login capabilities... that if user is not logged in, page doesnt load at all....

Sergey Alexandrovich Kryukov 15-Jan-12 2:40am

Pretty boring stuff... this is just text processing; you can code such transformation by yourself. Again, no need to go to ASP.NET without the purpose and essential change in behavior.
--SA

psychic6000 15-Jan-12 2:47am

yes you are right again... i do realize it was a mistake to use html in first place. even by a designer point of view, html is nothing compared to asp/php... i mean all the look up etc... but as i mentioned above, now the problem is time...
and i think you are right... i should write a text soft which reads the files and replaces the lines as acquired to my needs... thanks again :)

Sergey Alexandrovich Kryukov 15-Jan-12 11:49am

The mistake in first place is a different story. What was done in the past was done, the problem is what to do in future. I would advise just one thing: if you are to re-implement things, despite of the limited chance, try to do as much as possible to change the quality of content and design, not just formal transition.

What can help a lot is the structure of your HTML. If it is a well-formed as XML, or if you have a chance to fix it to be a well-formed XML, you can save a lot of time and reduce mistakes by using XML processing instead of text processing. For example, you could use XDocument (see) and use XPath, LINQ to XML for automatic processing.

You know what? Maybe this is good that you have to re-implement things? From my experience, good things we totally re-implemented at least twice. What about teams where people pretend that they "reuse" everything and don't waste time for re-doing what is "just working"? They often bound to infinite "improvement" of the product and often never complete if. Pretending doing the work "only once" and "reuse" they actually get sunk into "infinite" development.

Cheers,
--SA

Sergey Alexandrovich Kryukov 15-Jan-12 11:54am

By the way, if you feel convinced, please consider formally accepting the answer (green button) :-)
--SA

psychic6000 15-Jan-12 12:00pm

thanks for all your time and efforts... i will take your advise seriously next time... :)

Sergey Alexandrovich Kryukov 16-Jan-12 12:36pm

You are welcome.
--SA