![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
InorganicMatter
[H]F Junkie
- Joined
- Oct 19, 2004
- Messages
- 15,461
We are developing an application that uses .NET Remoting functionality. Nothing too complicated - it hosts the remote object in IIS, and when the user launches the desktop client, it authenticates with NTLM then lets them in. The desktop app just displays info, and all the processing is done on the server.
We moved to Server 2008 yesterday. And yesterday, the application they are developing began to run very slow. One minute hangups on everything you try to do. Of course, in light of yesterday's server move, I'm the one upon who all the blame is being offloaded. I say they screwed up their code. The app is still in development for goodness sake!
Could they be right? Is there anything that changed in Server 2008 that could slow this down? The testing machines are totally different pieces of hardware. We have a junk box with XP running IIS/SQL as the "server," and the developers are all running Vista as the "clients."
We moved to Server 2008 yesterday. And yesterday, the application they are developing began to run very slow. One minute hangups on everything you try to do. Of course, in light of yesterday's server move, I'm the one upon who all the blame is being offloaded. I say they screwed up their code. The app is still in development for goodness sake!
Could they be right? Is there anything that changed in Server 2008 that could slow this down? The testing machines are totally different pieces of hardware. We have a junk box with XP running IIS/SQL as the "server," and the developers are all running Vista as the "clients."