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. C#
  4. .NET 1.1 application performance in Windows 2003 Server

.NET 1.1 application performance in Windows 2003 Server

Scheduled Pinned Locked Moved C#
csharpsysadminperformancehelpquestion
2 Posts 2 Posters 2 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.
  • S Offline
    S Offline
    Sushant Duggal
    wrote on last edited by
    #1

    Hi Friends, I developed a desktop applcation in .NET 1.1 frameework using C#. The application works perfect in Windows XP or Windows 2000 Server environment, but in Windows 2003 server the application is really slow. The performance is degraded upto 200%. i.e. it takes 4 times more time in Windows 2003 server than under Windows XP or Windows 2000 server. Can anyone tell me what is the problem and can it be rectified. Thanks,

    Sushant Duggal.

    N 1 Reply Last reply
    0
    • S Sushant Duggal

      Hi Friends, I developed a desktop applcation in .NET 1.1 frameework using C#. The application works perfect in Windows XP or Windows 2000 Server environment, but in Windows 2003 server the application is really slow. The performance is degraded upto 200%. i.e. it takes 4 times more time in Windows 2003 server than under Windows XP or Windows 2000 server. Can anyone tell me what is the problem and can it be rectified. Thanks,

      Sushant Duggal.

      N Offline
      N Offline
      Nick Parker
      wrote on last edited by
      #2

      That's a fairly broad question, have you tried profiling the application? If you don't have a commerical profiler, try the CLR Profiler[^] from Microsoft.

      - Nick Parker Microsoft MVP - Visual C#
      My Blog | My Articles

      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