M
Michael Steidl
I use XMLspy for handling XML files and started testing its feature to generate
C# code from XML Schemas. Now I got stuck in a strange situation: (I have to
add being not a C# geek, only currently looking deeper into C# considering
making more use of it)
I created C# code from a schema with XMLspy 2005 rel 1. This code worked
flawlessly.
Then I moved to XMLspy 2005 rel. 3 and created C# code from exactly the same
schema again - and ran into a ton of CS0108 errors:
This generated code creates derived classes (as XML Schema types might be
derived from another type). VS2003 raises warnings on a method called Validate
which exists in the base class and in the derived class and VS2003 tells the
"new" keyword is required since the Validate method of the derived class hides
the Validate class of the initial class. This sounds reasonable.
BUT: how does it come to get the rel.1 code compiled without this warning as
the code looks completely the same as the rel.3 code? Is there a VS2003 switch
(in the Project settings ?) to let the methods of the derived class hide the
ones of the base class automatically?
Thanks for any glue
Michael
C# code from XML Schemas. Now I got stuck in a strange situation: (I have to
add being not a C# geek, only currently looking deeper into C# considering
making more use of it)
I created C# code from a schema with XMLspy 2005 rel 1. This code worked
flawlessly.
Then I moved to XMLspy 2005 rel. 3 and created C# code from exactly the same
schema again - and ran into a ton of CS0108 errors:
This generated code creates derived classes (as XML Schema types might be
derived from another type). VS2003 raises warnings on a method called Validate
which exists in the base class and in the derived class and VS2003 tells the
"new" keyword is required since the Validate method of the derived class hides
the Validate class of the initial class. This sounds reasonable.
BUT: how does it come to get the rel.1 code compiled without this warning as
the code looks completely the same as the rel.3 code? Is there a VS2003 switch
(in the Project settings ?) to let the methods of the derived class hide the
ones of the base class automatically?
Thanks for any glue
Michael