Create an account
Today I got my copy of Visual Studio 2005 through the post, so I've… - John C. Kirk
Apr. 14th, 2006
Leave a comment
September 8th, 2006 07:35 pm (UTC)
I was just wrestling with the same sort of error message and noticed the tip you gave in your edit about a public constructor...I just wanted to also point out that the error also appears if you don't have a no-argument constructor defined for the form.
I was creating a form that could be invoked standalone as well as called from within another form, and had added an optional parameter to the constructor to allow an invoking form to pass in a string, but Visual Studio didn't like even the optional parameter.
Thanks for pointing me along the right path!