Microsoft Knowledge Base Email Alertz

KBAlertz.com: FIX: Error message when you use the XMLSchema.Compile method to compile an XML schema (XSD) file: The content type of the base type must not be a simple type definition

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]

Search KbAlertz

Advanced Search

Webmasters
Put kbAlertz on your website.
[ Click Here for more! ]





ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
KBAlertz referrals get
** SIX MONTHS FREE **


Community Site



We Send hundreds of thousands of emails using ASP.NET Email


ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
KBAlertz referrals get
** SIX MONTHS FREE **




Mentioned In








Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks




Article ID: 957206 - Last Review: February 5, 2009 - Revision: 1.0

FIX: Error message when you use the XMLSchema.Compile method to compile an XML schema (XSD) file: "The content type of the base type must not be a simple type definition"

SYMPTOMS

In the NET Framework 1.1, you call the XMLSchema.Compile method to compile an XML schema (XSD) file that extends a type from simpleContent to complexContent. However, the compilation fails, and you receive an error message resembles the following:
The content type of the base type must not be a simple type definition.

RESOLUTION

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have the .NET Framework 1.1 Service Pack 1 (SP1) installed to apply this hotfix.

Restart requirement

You do not have to restart the computer if you install the hotfix for .NET Framework 1.1. You have to restart the computer if you install the hotfix for Windows Server 2003.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

x86 versions for .NET Framework 1.1 SP1

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Cachemgr.exe1.1.4318.081,92031-Jan-200809:55x86
Hotfix.exe1.0.0.153,24831-Jan-200809:57x86
Netfxupdate.exe1.0.3705.183,00001-Feb-200801:02x86
System.web.services.dll1.1.4322.2444573,44030-Sep-200820:53x86
System.xml.dll1.1.4322.24441,359,87230-Sep-200820:58x86

x86 versions of Windows Server 2003 that is running .NET Framework 1.1 SP1

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Netfxupdate.exe1.0.3705.382,98425-Jun-200807:26x86SP2SP2QFE
Setregni.exe1.1.4322.203566,60025-Jun-200807:26x86SP2SP2QFE
System.xml.dll1.1.4322.24441,359,87213-Oct-200807:08x86SP2SP2QFE
Togac.exe1.1.4322.225166,60025-Jun-200807:26x86SP2SP2QFE

WORKAROUND

To work around this problem, use .NET Framework 2.0, and then call the XMLSchemaSet.Compile method to compile the XSD file.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

APPLIES TO
  • Microsoft .NET Framework 1.1
Keywords: 
kbhotfixserver kbexpertiseadvanced kbqfe kbsurveynew KB957206
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Be the first to leave feedback, to help others about this knowledge base article.

(Optional) Name

(Optional) Public URL Or Email

Comments
No HTML -- Text Only Please