Windows Forms application works fine on XP; falls over on Windows 2000

Hot Topic

C# Needs a Property keyword like MC++ has now
How do I iterate over cells in excel?
App.Config
Hex convertion to string in C#
Database Question
plz help re-write vb code to c# code
Initializing an instance to a pre-existing instance
bat-file startup + options
VS2005 Image Library Gone!
reading image from access database

Visual C#

Multiple Threads accessing RichTextBox.appendText Method (BeginInvoke)
Help! Access generic list data in App_code class from code behind
My question is so basic I'm ashamed to ask it! LOL..
simulating domain users file operations
determine if running in IE
how do you write a calculator programme
Exe file remaining the memory
Passing the managed class(with array of stuct as member) to unmanaged function
update values from form into database
Summary comments

Windows Forms application works fine on XP; falls over on Windows 2000

We have a C# Windows Forms application using the December 2005 CAB
that I can't get to run on some of our customers Windows 2000 machines.

The error is 'Exception has been thrown by the target of an invocation'
falling over at the System.RutimeTypeHandle.CreateInstance method call.

On the xp machines when we are running the Client we only install the
Dot Net framework 2.0 and the client runs with no problems.

Any ideas where we should start looking Due to security issues, its impossible for us to debug the Client on the customers mahines. We are using stongly named assemblies

Thanks

Answer this question

Windows Forms application works fine on XP; falls over on Windows 2000

  • MacKenzieMi

    We have narrowed it down to possibly being a problem with the parsing of our app.config file.Are there any known issues with this on Windows 2k

    Thanks

  • DeeDee Kruger

    Windows 2000 using the directory WINNT while Windows XP using WINDOWS. If that might help.

    jbattat

  • Oblansky

    Time to use Virtual PC and start debugging it.

  • Windows Forms application works fine on XP; falls over on Windows 2000
Answer this question