When I try to validate standard HR-XML xsd schema's, Visual studio gives the
following error

BEC2013
"UserArea" - Specify a valid .NET type name for this root node. The current
.NET type name of this root node is a duplicate.


So, there seem to be duplicates in the HR-XML schema's. I can't make changes
on the schemas, because then te HR-XML standard will be lost.

Can anybody help me out, or has a workaround to validate the schema's?

Regards
Dirk

[ Post a follow-up to this message ]

It can say that when you have duplicate type names, for the schema, not for
the xml content, but rather the .net assembly types. The type name in
properties window of the xml schema in solution explorer, not the schema in
schema editor.

Paul.

"Dirkjan van Groeningen" <DirkjanvanGroeningen@discussions.microsoft.com>
wrote in message news:7CC4298F-E1DD-4A97-AE99-B984DD0CBBDA@microsoft.com...
> When I try to validate standard HR-XML xsd schema's, Visual studio gives
> the
> following error
>
> BEC2013
> "UserArea" - Specify a valid .NET type name for this root node. The
> current
> .NET type name of this root node is a duplicate.
>
>
> So, there seem to be duplicates in the HR-XML schema's. I can't make
> changes
> on the schemas, because then te HR-XML standard will be lost.
>
> Can anybody help me out, or has a workaround to validate the schema's?
>
> Regards
> Dirk

[ Post a follow-up to this message ]

Paul,
I've checked the duplicate type names for the schema's and I'm prety sure it
hasn't got anything to do with this.

I've imported the HR-XML schema's, one of the xsd schema's for example is
PositionOpening.xsd. Attributes for this example are CountryCode,
CurrencyCode, Frequency, GenderCode.etc.

On some of these attributes VisualStudio.NET gives errors.

f.e.

PositionOpening.xsd: error BEC2013: Node "CountryCode" - Specify a valid
.NET type name for this root node. The current .NET type name of this root
node is a duplicate.



"Paul Somers(MVP)" wrote:

> It can say that when you have duplicate type names, for the schema, not fo
r
> the xml content, but rather the .net assembly types. The type name in
> properties window of the xml schema in solution explorer, not the schema i
n
> schema editor.
>
> Paul.
>
> "Dirkjan van Groeningen" <DirkjanvanGroeningen@discussions.microsoft.com>
> wrote in message news:7CC4298F-E1DD-4A97-AE99-B984DD0CBBDA@microsoft.com..
. 
>
>
>

[ Post a follow-up to this message ]

I solved the problem by renaming all the .xsd schemas. I had to rename all
the root-reference properties from the xsd schemas.


"Dirkjan van Groeningen" wrote:
[vbcol=seagreen]
> Paul,
> I've checked the duplicate type names for the schema's and I'm prety sure 
it
> hasn't got anything to do with this.
>
> I've imported the HR-XML schema's, one of the xsd schema's for example is
> PositionOpening.xsd. Attributes for this example are CountryCode,
> CurrencyCode, Frequency, GenderCode.etc.
>
> On some of these attributes VisualStudio.NET gives errors.
>
> f.e.
>
> PositionOpening.xsd: error BEC2013: Node "CountryCode" - Specify a valid
> .NET type name for this root node. The current .NET type name of this root
> node is a duplicate.
>
>
>
> "Paul Somers(MVP)" wrote:
> 

[ Post a follow-up to this message ]