Xcopy and we found the problem. The main winform was corrupt. Apparently sometime in the past, a member of the team did some copying of code within the partial classes of the form. While the application was running on a machine with VS2005 installed, the application would perform until it was ported over to a client - then it failed.
We solved the problem by removing the offending form and put a new form being very careful not to copy anything into the partial classes. Recompiled and it works now. I guess Microsoft really means it when they say - "stay out of this area" Best regards, Jerry -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Curt Hagenlocher Sent: Monday, January 29, 2007 5:28 PM To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM Subject: Re: [ADVANCED-DOTNET] System.InvalidOperationException On 1/29/07, Knowlton, Gerald F. <[EMAIL PROTECTED]> wrote: > > No - wish it was that. I wasn't clear in my post. This is occurring on > many client machines. It only works on machines that have VS2005 > installed. All client machines have the framework 2.0 Are you deploying via MSI or XCOPY? -- Curt Hagenlocher [EMAIL PROTECTED] =================================== This list is hosted by DevelopMentor(r) http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
