Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. .NET (Core and Framework)
  4. Migrating web Application to .Net 2005

Migrating web Application to .Net 2005

Scheduled Pinned Locked Moved .NET (Core and Framework)
csharp
3 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • H Offline
    H Offline
    happyheartcs
    wrote on last edited by
    #1

    Hi All, I'm migrating a web application from .net 2003 to .net 2005. I need to know what I have to change manually in each page before I make the conversion because when I use the conversion wizard,many errors are generated. Thanks so so much

    S 1 Reply Last reply
    0
    • H happyheartcs

      Hi All, I'm migrating a web application from .net 2003 to .net 2005. I need to know what I have to change manually in each page before I make the conversion because when I use the conversion wizard,many errors are generated. Thanks so so much

      S Offline
      S Offline
      szukuro
      wrote on last edited by
      #2

      Mainly three things: 1. In the Markup replace "CodeBehind" with "CodeFile" int the Page directive 2. In the code file add the modifier "partial" to the class 3. Remove the control declarations in the code file. For example if you have <asp:Literal ID="Literal1" runat="server" /> in the markup, you don't need code like Literal Literal1 = new Literal() in the cs file. Also there could be a lot of code-specific changes you might need to do, sometimes just warning messages. To give an example, you should replace Page.RegisterStartupScript with Page.ClientScript.RegisterStartupScript. The best you can do, is examine these errors one be one and possibly resolve them with replace.

      H 1 Reply Last reply
      0
      • S szukuro

        Mainly three things: 1. In the Markup replace "CodeBehind" with "CodeFile" int the Page directive 2. In the code file add the modifier "partial" to the class 3. Remove the control declarations in the code file. For example if you have <asp:Literal ID="Literal1" runat="server" /> in the markup, you don't need code like Literal Literal1 = new Literal() in the cs file. Also there could be a lot of code-specific changes you might need to do, sometimes just warning messages. To give an example, you should replace Page.RegisterStartupScript with Page.ClientScript.RegisterStartupScript. The best you can do, is examine these errors one be one and possibly resolve them with replace.

        H Offline
        H Offline
        happyheartcs
        wrote on last edited by
        #3

        Thanks a lot :)

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups