Re: C# app works perfectly on XP but not on 2003 server

Hi Gunnar,

it's tough to really get a feel for what the problem is because there isn't much information you've given to go on. There can be hundreds of reasons an application would work on one machine and not another. Finding whether or not it's windows 2003
vs just a computer other than your dev box would narrow it somewhat. More information about specific errors it's giving you and how your getting them to occur would help even more.

-Allen
http://allenanderson.blogspot.com
http://www.glacialcomponents.com

On Fri, 26 Aug 2005 00:10:03 -0700, OfurGørn <ofurgorn@xxxxxxxxxxxxx> wrote:

>Hey Allen
>
>I am sutre that the problem lies within the 2003 box, although, I can't be
>sure whether it is 2003 itself, or the other programs on that specific box.
>My program is designed to get data from another program that is running,
>which is both running on the developer computer (XP) and on the target
>system(2003). I am really afraid that the 3rd party app is the source of the
>problem, but I wanted to post here to check if there is something very simple
>in "porting" from XP to 2003 i am missing. My program uses Windows Sockets
>and the C# xml services.
>
>________________________
>Gunnar Gudmundsson
>
>
>"Allen Anderson" wrote:
>
>> there are any number of reasons why it might not work on another machine. Are you sure it's a problem with windows 2003 though? Have you tried it on other XP boxes to make sure?
>>
>> when you say you put a debug code in, what exactly do you mean? a messagebox? a debug writeline out? Does the program work if you don't put any debug statements in at all?
>>
>> -Allen
>> http://allenanderson.blogspot.com/
>> http://www.glacialcomponents.com
>>
>> On Thu, 25 Aug 2005 06:35:04 -0700, OfurGørn <ofurgorn@xxxxxxxxxxxxx> wrote:
>>
>> >Hi everybody - here is an easy one (hopefully)
>> >
>> >I have a funny error, that is driving me nuts !!! I have a application that
>> >I have written on a Windows XP SP2 machine, and tuned to near-perfection -
>> >then I copied the program to the target system, a Windows 2003 standard
>> >server, the program works fine for 5-10 minutes, and then comes up with an
>> >exception. The problem is, that whenever I put any debug code in the code
>> >that generates the exception, the exception does not come again, but another
>> >exception comes. I have so far received exceptions like:
>> > - System.IO.IOException: Transfer complete.
>> > - System.NullReferenceException
>> >
>> >I am having a hard time fixing this, as I am running an Release version on
>> >the remote server, and have no debug information. I suspect that there is
>> >something basic I have forgotten in making my code work for Windows 2003
>> >Server.
>> >
>> >hoping the solution is quick and simple !
>> >
>> >________________________
>> >Gunnar Gudmundsson
>>
>>

.

Relevant Pages

  • Re: C# app works perfectly on XP but not on 2003 server
    ... My program uses Windows Sockets ... > when you say you put a debug code in, ... that whenever I put any debug code in the code ... >>that generates the exception, the exception does not come again, but another ...
    (microsoft.public.dotnet.framework.windowsforms)
  • Re: C# app works perfectly on XP but not on 2003 server
    ... In production/release mode on Windows 2003 production server where you have many things going on, the GC is probably doing it's job more efficiently and getting rid of objects that you closed/disposed or set to nothing. ... I have a application that I have written on a Windows XP SP2 machine, and tuned to near-perfection - then I copied the program to the target system, a Windows 2003 standard server, the program works fine for 5-10 minutes, and then comes up with an exception. ... The problem is, that whenever I put any debug code in the code that generates the exception, the exception does not come again, but another exception comes. ...
    (microsoft.public.dotnet.framework.windowsforms)
  • Re: C# app works perfectly on XP but not on 2003 server
    ... Are you sure it's a problem with windows 2003 though? ... when you say you put a debug code in, ... that whenever I put any debug code in the code ... >that generates the exception, the exception does not come again, but another ...
    (microsoft.public.dotnet.framework.windowsforms)
  • Re: The Big Mac Hoax. (aka OS X is a dog)
    ... The "debug code is in the betas and will be removed on RTM" is an urban myth. ... Of course, performance can and will no doubt be improved between now and RTM, but it won't be because "the debug code has been removed". ... Then you are saying that when they release the beta for testing that the debug code is already been removed. ... There has never been a "Windows Beta" that had debug code in it. ...
    (comp.sys.mac.advocacy)
  • C# app works perfectly on XP but not on 2003 server
    ... I have written on a Windows XP SP2 machine, ... that whenever I put any debug code in the code ... that generates the exception, the exception does not come again, but another ... the remote server, ...
    (microsoft.public.dotnet.framework.windowsforms)