Results 1 to 3 of 3

Thread: Classic ASP apps on W2003/ASP.NET?

  1. #1
    Throbbing Member
    Join Date
    Aug 2004
    Location
    Scotlandshire
    Posts
    640
    Thanks
    15
    Thanked
    9 times in 8 posts
    • 8bit's system
      • Motherboard:
      • MSI Z170A-G43 PLUS
      • CPU:
      • Intel i7-6700K
      • Memory:
      • 2x Kingston HyperX Fury Black (8GB)
      • Storage:
      • 1x Crucial MX100 512GB, 1x Western Digital Caviar Black 1TB (WD1001FALS)
      • Graphics card(s):
      • Sapphire AMD R9 390 Nitro
      • PSU:
      • Corsair RM650x
      • Case:
      • Corsair Carbide Air 540
      • Operating System:
      • Windows 10 Home
      • Monitor(s):
      • LG 29UM67 29", 21:9, 2560x1080
      • Internet:
      • PlusNet Fibre

    Classic ASP apps on W2003/ASP.NET?

    My work are beginning to look at Windows2003 Server, currently on 2000. I develop our corporate intranet which is entirely IIS5/Classic ASP/ADO/SQL Server 2000 powered.

    I know MS say ASP.NET is fine with Classic ASP applications but can anyone tell me if they've encountered any issues with this?

  2. #2
    Senior Member Shad's Avatar
    Join Date
    Jul 2003
    Location
    In front
    Posts
    2,782
    Thanks
    23
    Thanked
    42 times in 25 posts
    We were developing ASP and ASP.NET applications on a Windows 2000 server without any problems at work, and we've continued to do so since Febuary with a Windows 2003 server. The only stumbling block that commonly comes up is if you have relative paths to include files. These are disabled by default, but can easily and quickly be enabled.

    ASP and ASP.NET code can run in the same application (i.e. web or virtual directory) but if you are developing projects it's best to setup each project in a seperate web under a different host header.

    If you are moving to ASP.NET and your development workstations run Windows XP, and you wish to use remote debugging, there are some... issues

    Firstly (and this doesn't specifically apply to Windows XP), you can only have one one debugger attached at any one time, on the server. So if you have say 3 developers working on the same project, using source control, then all hell can break lose if you're not careful. The biggest time cost with this configuration is either waiting for Visual Studio to get its arse into gear, or waiting for other people to finish with the debugger. Worse still, if you try and use the debugger without realising it's in use, VS will build your solution and overwrite your colleagues build on the server, rendering their debug session useless and prone to crashing.

    Roll on Visual Studio 2005!

    The other issue is with WinXP SP2. I lost a morning trying to get remote debugging working with my workstation (running XP SP2) and failed. Microsoft has listed VS.NET as 'having issues' with SP2 and this clearly is one of them. No end of messing about with the firewall could sovle the problem.

    Bottom line is that Windows 2003 is great and your applications will run fine on it (in most cases)
    Simon


  3. #3
    Throbbing Member
    Join Date
    Aug 2004
    Location
    Scotlandshire
    Posts
    640
    Thanks
    15
    Thanked
    9 times in 8 posts
    • 8bit's system
      • Motherboard:
      • MSI Z170A-G43 PLUS
      • CPU:
      • Intel i7-6700K
      • Memory:
      • 2x Kingston HyperX Fury Black (8GB)
      • Storage:
      • 1x Crucial MX100 512GB, 1x Western Digital Caviar Black 1TB (WD1001FALS)
      • Graphics card(s):
      • Sapphire AMD R9 390 Nitro
      • PSU:
      • Corsair RM650x
      • Case:
      • Corsair Carbide Air 540
      • Operating System:
      • Windows 10 Home
      • Monitor(s):
      • LG 29UM67 29", 21:9, 2560x1080
      • Internet:
      • PlusNet Fibre
    Thanks a lot Shad, thats kinda what I was hoping to hear I'll wait to hear some more tales before I make my recommendation but it sounds like our requirements don't stretch to yours. I use Dreamweaver MX04, no Visual Studio, 2000pro on desktop, no remote debugging, developing probably much lighter weight apps than yours so if I get the same breaks you did I should be OK.

    ty m8,
    8bit

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •