dcsimg


DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 5 of 5

Thread: convert my asp pages to asp.net

  1. #1
    Emad Ramadan Guest

    convert my asp pages to asp.net


    I have finished a new project and I'd like to convert my asp files to asp.net
    to add more efficiency on the site .. so anybody can send me the detailed
    method to convert them ?

    Thanks alot from Qatar

  2. #2
    Irfan Rizvi Guest

    Re: convert my asp pages to asp.net


    ASP.NET framework is very much different from unstrucured ASP and there is
    no correct way to just transform it into ASP.NET pages, and if you reall
    y want to convert your application and make it ASP.NET based then you have
    to re model it and code again almost all the pages , the most prominnet reason
    why you will do this are

    1. ASP supported scripting languages such as VB Script or Javscript while
    ASP.NEt supports proper Object oriented languages such as C# or VB.NET etc

    2. In ASP.NET you do proper Event based programming which was impossible
    in ASP

    3. ASP.NET seperates the code part from HTML parts , which in case of ASP
    all mixed up

    4. ASP.NET introduced server controls which aree much powerful then ASP controls

    i think the few above differnces made my point clear that ASP.NET and ASP
    are very differnet things

    "Emad Ramadan" <dotnet272@hotmail.com> wrote:
    >
    >I have finished a new project and I'd like to convert my asp files to asp.net
    >to add more efficiency on the site .. so anybody can send me the detailed
    >method to convert them ?
    >
    >Thanks alot from Qatar



  3. #3
    Greg Rothlander Guest

    Re: convert my asp pages to asp.net


    This is true if you want to completely covert the ASP to ASP.Net and replace
    the ASP controls and items with ASP.Net version.... but you do not have to
    do this all at once.

    I've converted a number of ASP websites to ASP.Net by simply renaming the
    ASP page to ASP.Net and fixing few errors. VS will add the code-behind class
    file and connect the ASP.Net to your VB.Net code (or C#). When you recompile,
    you will find a few errors that come us like using SET. You can simply fix
    the errors and recompile. I've converted dozens of these pages in just a
    few hours.

    This doesn't take advantage of all that .Net has to offer, but it's at least
    a start. I simply want to make point that you do not have to completly embrace
    everything that is .Net to simply start using .Net in your existing applicaitons.

    Of course this all depends on the ASP page and how it was written. If you
    where doing all of your business logic in the ASP page (I haven't done that
    in over 3-years) and you want to move that code to the code-behind (you don't
    have too) then you may have some issues depending on how complex your code
    is.

    If all you want to do is rename the ASP to ASPX, you will have very few issues
    to get the page to run. Then as time permits and you enhance the pages,
    you can move your code into the code-behind.

    We've been migration our applications into .Net one page at a time. We had
    to go ahead and rename the ASP files to ASPX to allow our session variables
    to work correctly. We also had to fix a small number of bugs, but it was
    pretty simple. It probably took me 5 to 10 minuts per page.

    Here a few points regarding each of the previous replies items that where
    listed...

    >ASP.NET framework is very much different from unstrucured ASP and there

    is
    >no correct way to just transform it into ASP.NET pages, and if you reall
    >y want to convert your application and make it ASP.NET based then you have
    >to re model it and code again almost all the pages , the most prominnet
    >reason why you will do this are


    This is true except that you can convert ASP to ASP.Net very simply. Of
    course you will not be able to take advantage of everything that is .Net,
    but as time permits you can add it.

    >1. ASP supported scripting languages such as VB Script or Javscript while
    >ASP.NEt supports proper Object oriented languages such as C# or VB.NET etc


    Yes, but it still supports VBScript and Javascript. You can convert this
    in steps as needed.

    >2. In ASP.NET you do proper Event based programming which was impossible
    >in ASP


    Yes, but existing ASP code will work in ASP.Net pages

    >3. ASP.NET seperates the code part from HTML parts , which in case of ASP
    >all mixed up.


    That's not completly true. I've been sepearting my HTML from my business
    logic code (mius about 8 lines in VBScript in the beginning of the page)for
    over 3 years and I have no problems with it. It depends on your ability
    to handle the use of DLL's for your business logic.

    Do this made the converstion to .Net very simple.

    >4. ASP.NET introduced server controls which aree much powerful then ASP

    controls

    Yes, but you do not have to implement them as soon as you start converting
    to .Net. Your old ASP code will still work. As time permits and as you
    need too, add .Net server controls to your page.



  4. #4
    Join Date
    Sep 2008
    Posts
    1
    Thanks Greg.. it was really helpful.
    What if I want to convert the entire web application into ASP.net at once and correct the errors later, what exactly is the procedure to do that.

    Please guide.

  5. #5
    Join Date
    Apr 2007
    Location
    Sterling Heights, Michigan
    Posts
    8,663
    Welcome to DevX harshita

    You do realize, don't you, that you responded to a thread that is over 6 years old?

    Have a look at this article.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center