Deploying .Net Application from WinXP to WinNT and/or Win98

  • Thread starter Thread starter Jodi Wedll
  • Start date Start date
J

Jodi Wedll

I am attempting to deploy my .Net Application from my WinXP
development machine to production systems based upon WinNT and Win98.
I believe that it is mostly working except for code relating to the
error coding. I have error coding that warns the user of problems
with the information supplied. I used
"System.Windows.Forms.ErrorProvider" based error coding which flags
the control with the problem data for the user. The app blows when
the database refuses to accept a null input for the database field.
This is correct. I have error coding that should prevent the user
from seeing the database complaint about the bad data.

Any ideas of why this code works fine on my developement WinXP machine
and not my Winnt and Win98 production machines?

I appreciate in advance of anytime given to this question!
Jodi
 
Hi,

What exactly is wrong with the application when it runs on a Win98/WinNT
machine? It doesn't catch an exception it should have caught? It doesn't
display the error icon properly? The error message displayed as a tooltip
when the mouse pointer is over the error icon is not the expected one?

Note that the ErrorProvider component does not do any error handling, it can
only display errors. So you should probably post your error handling code so
we can see what could go wrong.

You can also deploy a Debug build to a Win98/WinNT machine and try to debug
it there. If this is not an option, at least instrument your application
with tracing controlled by a TraceSwitch instance and enable tracing on the
machine in question.

--
Dmitriy Lapshin [C# / .NET MVP]
X-Unity Test Studio
http://www.x-unity.net/teststudio.aspx
Bring the power of unit testing to VS .NET IDE

Jodi Wedll said:
I am attempting to deploy my .Net Application from my WinXP
development machine to production systems based upon WinNT and Win98.
I believe that it is mostly working except for code relating to the
error coding. I have error coding that warns the user of problems
with the information supplied. I used
"System.Windows.Forms.ErrorProvider" based error coding which flags
the control with the problem data for the user. The app blows when
the database refuses to accept a null input for the database field.
This is correct. I have error coding that should prevent the user
from seeing the database complaint about the bad data.

Any ideas of why this code works fine on my developement WinXP machine
and not my Winnt and Win98 production machines?

I appreciate in advance of anytime given to this question!
Jodi
Click to expand...
 
Back
Top