Skip to content

[API Proposal]: XSD DCS Schema API's from 4.8 #72243

Description

@StephenMolloy

Background and motivation

We're trying to bring DCS and friends back to par with .Net 4.8 in this release. One of the capabilities of the DCS library in .Net 4.8 is to generate XSD schemas or import XSD schemas into usable code. This functionality is used to support WCF and svcutil. The code that handles schema importing however, had a dependency on System.CodeDom. After some extended discussion around the goals and motivations, we decided to take a two-pronged approach here. The existing DCS assembly in the runtime will be receiving updates to align with 4.8 and to support this schema work under the covers... but the top-level functionality (and public surface area) of the schema support will live in a separate package in dotnet/runtime that is not part of the runtime. (Like the System.CodeDom package it depends on.) See the PR #71752 and other half of the API review #72242.

This is the corresponding API review for the external Schema package. The public surface area it presents is almost exactly as it was in .Net 4.8, so it's a proven design. There is one difference though - because .Net Core originally started with a strange Silverlight-based port of DataContractSerializer. The way it handled surrogates was changed and limited. The other API proposal contains an extended surrogate interface with the missing parts of the corresponding interface in 4.8... except for one method which we could not include on the runtime side because it has CodeDom types in the signature. (We can't define that interface in this 'external' package though because it is used pretty deep in the workings of the newly 4.8-aligned DCS.) In this review, I've placed that method as a Func<> on the ImportOptions class. We have also considered creating yet another extending interface in this project to round out the complete functionality of IDataContractSurrogate from 4.8. I honestly have no preference which way to go. Hoping the API experts have input on that one.

API Proposal

namespaceSystem.Runtime.Serialization.Schema{// This ExportOptions class is defined similarly to the public System.Runtime.Serialization.ExportOptions class in 4.8.// The surrogate type had changed in Core, so it changed here as well, and thats the only difference.// https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.exportoptions?view=netframework-4.8publicsealedclassExportOptions{publicCollection<Type>KnownTypes{get;}publicISerializationSurrogateProvider?SurrogateProvider{get;set;}}// This ImportOptions API is almost exactly the same as the ImportOptions API in 4.8, with the exception of the surrogate// type of course - since that changed between NetFx and Core - and one extra Func that used to be part of the surrogate// provider interface in 4.8, but was pulled out into this options class because it uses CodeDom types.// https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.importoptions?view=netframework-4.8publicsealedclassImportOptions{publicSystem.CodeDom.Compiler.CodeDomProvider?CodeProvider{get;set;}publicboolEnableDataBinding{get;set;}publicboolGenerateInternal{get;set;}publicboolGenerateSerializable{get;set;}publicboolImportXmlType{get;set;}publicIDictionary<string,string>Namespaces{get;}publicICollection<Type>ReferencedCollectionTypes{get;}publicICollection<Type>ReferencedTypes{get;}publicISerializationSurrogateProvider?SurrogateProvider{get;set;}// This is the Func which is the new API. The naming and intent of this Func is to be the last method// from the old IDataContractSurrogate interface that we couldn't stick in the runtime interfaces.// I'm open to feedback here if people don't like sticking a Func on an options class.publicFunc<System.CodeDom.CodeTypeDeclaration,System.CodeDom.CodeCompileUnit,System.CodeDom.CodeTypeDeclaration?>?ProcessImportedType;}// This XsdDataContractExporter class is the exact same API as the one in 4.8.// https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.xsddatacontractexporter?view=netframework-4.8// This class also exists in-box with DCS in Core... but it mostly does not work. It does not depend on CodeDom, so it could// probably be completed in-box, but it made sense to us to keep schema import and export together in the same package. The in-box// implementation should get marked as obsolete. (This also applies to the ExportOptions class above.)publicsealedclassXsdDataContractExporter{publicXsdDataContractExporter(){}publicXsdDataContractExporter(System.Xml.Schema.XmlSchemaSet?schemas){}publicExportOptions?Options{get;set;}publicSystem.Xml.Schema.XmlSchemaSetSchemas{get;}[RequiresUnreferencedCodeAttribute()]publicboolCanExport(ICollection<System.Reflection.Assembly>assemblies){}[RequiresUnreferencedCodeAttribute()]publicboolCanExport(ICollection<Type>types){}[RequiresUnreferencedCodeAttribute()]publicboolCanExport(Typetype){}[RequiresUnreferencedCodeAttribute()]publicvoidExport(ICollection<System.Reflection.Assembly>assemblies){}[RequiresUnreferencedCodeAttribute()]publicvoidExport(ICollection<Type>types){}[RequiresUnreferencedCodeAttribute()]publicvoidExport(Typetype){}[RequiresUnreferencedCodeAttribute()]publicSystem.Xml.XmlQualifiedName?GetRootElementName(Typetype){}[RequiresUnreferencedCodeAttribute()]publicSystem.Xml.Schema.XmlSchemaType?GetSchemaType(Typetype){}[RequiresUnreferencedCodeAttribute()]publicSystem.Xml.XmlQualifiedNameGetSchemaTypeName(Typetype){}}// This XsdDataContractImporter class is the exact same API as the one in 4.8.// https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.xsddatacontractimporter?view=netframework-4.8publicsealedclassXsdDataContractImporter{publicXsdDataContractImporter(){}publicXsdDataContractImporter(System.CodeDom.CodeCompileUnitcodeCompileUnit){}publicSystem.CodeDom.CodeCompileUnitCodeCompileUnit{get;}publicImportOptions?Options{get;set;}[RequiresUnreferencedCodeAttribute()]publicboolCanImport(System.Xml.Schema.XmlSchemaSetschemas){}[RequiresUnreferencedCodeAttribute()]publicboolCanImport(System.Xml.Schema.XmlSchemaSetschemas,ICollection<System.Xml.XmlQualifiedName>typeNames){}[RequiresUnreferencedCodeAttribute()]publicboolCanImport(System.Xml.Schema.XmlSchemaSetschemas,System.Xml.XmlQualifiedNametypeName){}[RequiresUnreferencedCodeAttribute()]publicboolCanImport(System.Xml.Schema.XmlSchemaSetschemas,System.Xml.Schema.XmlSchemaElementelement){}[RequiresUnreferencedCodeAttribute()]publicvoidImport(System.Xml.Schema.XmlSchemaSetschemas){}[RequiresUnreferencedCodeAttribute()]publicvoidImport(System.Xml.Schema.XmlSchemaSetschemas,ICollection<System.Xml.XmlQualifiedName>typeNames){[RequiresUnreferencedCodeAttribute()]publicvoidImport(System.Xml.Schema.XmlSchemaSetschemas,System.Xml.XmlQualifiedNametypeName){}[RequiresUnreferencedCodeAttribute()]publicSystem.Xml.XmlQualifiedName?Import(System.Xml.Schema.XmlSchemaSetschemas,System.Xml.Schema.XmlSchemaElementelement){}[RequiresUnreferencedCodeAttribute()]publicSystem.CodeDom.CodeTypeReferenceGetCodeTypeReference(System.Xml.XmlQualifiedNametypeName){}[RequiresUnreferencedCodeAttribute()]publicSystem.CodeDom.CodeTypeReferenceGetCodeTypeReference(System.Xml.XmlQualifiedNametypeName,System.Xml.Schema.XmlSchemaElementelement){}[RequiresUnreferencedCodeAttribute()]publicICollection<System.CodeDom.CodeTypeReference>?GetKnownTypeReferences(System.Xml.XmlQualifiedNametypeName){}}}

API Usage

See XsdDataContractImporter and XsdDataContractExporter in .Net 4.8.

Alternative Designs

No response

Risks

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    api-approvedAPI was approved in API review, it can be implementedarea-SerializationblockingMarks issues that we want to fast track in order to unblock other important work

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      , 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all
       blocks
      (function() {
      function addCopyButtons() {
      document.querySelectorAll('pre code').forEach(function(codeBlock) {
      if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
      codeBlock.parentElement.setAttribute('data-copy-added', 'true');
      var btn = document.createElement('button');
      btn.textContent = 'Copy';
      btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
      btn.onmouseover = function() { this.style.opacity = '1'; };
      btn.onmouseout = function() { this.style.opacity = '0.7'; };
      btn.onclick = function() {
      navigator.clipboard.writeText(codeBlock.textContent).then(function() {
      btn.textContent = 'Copied!';
      setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
      });
      };
      codeBlock.parentElement.style.position = 'relative';
      codeBlock.parentElement.appendChild(btn);
      });
      }
      addCopyButtons();
      // Re-run on dynamic content
      var observer = new MutationObserver(addCopyButtons);
      observer.observe(document.body, { childList: true, subtree: true });
      })();
      }
      } catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
      })();
      (function(){
      try {
      var __m = "github.com";
      var __re = new RegExp('^' + "github\\.com" + '
      [API Proposal]: XSD DCS Schema API's from 4.8 · Issue #72243 · dotnet/runtime · GitHub
      Skip to content

      [API Proposal]: XSD DCS Schema API's from 4.8 #72243

      Description

      @StephenMolloy

      Background and motivation

      We're trying to bring DCS and friends back to par with .Net 4.8 in this release. One of the capabilities of the DCS library in .Net 4.8 is to generate XSD schemas or import XSD schemas into usable code. This functionality is used to support WCF and svcutil. The code that handles schema importing however, had a dependency on System.CodeDom. After some extended discussion around the goals and motivations, we decided to take a two-pronged approach here. The existing DCS assembly in the runtime will be receiving updates to align with 4.8 and to support this schema work under the covers... but the top-level functionality (and public surface area) of the schema support will live in a separate package in dotnet/runtime that is not part of the runtime. (Like the System.CodeDom package it depends on.) See the PR #71752 and other half of the API review #72242.

      This is the corresponding API review for the external Schema package. The public surface area it presents is almost exactly as it was in .Net 4.8, so it's a proven design. There is one difference though - because .Net Core originally started with a strange Silverlight-based port of DataContractSerializer. The way it handled surrogates was changed and limited. The other API proposal contains an extended surrogate interface with the missing parts of the corresponding interface in 4.8... except for one method which we could not include on the runtime side because it has CodeDom types in the signature. (We can't define that interface in this 'external' package though because it is used pretty deep in the workings of the newly 4.8-aligned DCS.) In this review, I've placed that method as a Func<> on the ImportOptions class. We have also considered creating yet another extending interface in this project to round out the complete functionality of IDataContractSurrogate from 4.8. I honestly have no preference which way to go. Hoping the API experts have input on that one.

      API Proposal

      namespaceSystem.Runtime.Serialization.Schema{// This ExportOptions class is defined similarly to the public System.Runtime.Serialization.ExportOptions class in 4.8.// The surrogate type had changed in Core, so it changed here as well, and thats the only difference.// https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.exportoptions?view=netframework-4.8publicsealedclassExportOptions{publicCollection<Type>KnownTypes{get;}publicISerializationSurrogateProvider?SurrogateProvider{get;set;}}// This ImportOptions API is almost exactly the same as the ImportOptions API in 4.8, with the exception of the surrogate// type of course - since that changed between NetFx and Core - and one extra Func that used to be part of the surrogate// provider interface in 4.8, but was pulled out into this options class because it uses CodeDom types.// https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.importoptions?view=netframework-4.8publicsealedclassImportOptions{publicSystem.CodeDom.Compiler.CodeDomProvider?CodeProvider{get;set;}publicboolEnableDataBinding{get;set;}publicboolGenerateInternal{get;set;}publicboolGenerateSerializable{get;set;}publicboolImportXmlType{get;set;}publicIDictionary<string,string>Namespaces{get;}publicICollection<Type>ReferencedCollectionTypes{get;}publicICollection<Type>ReferencedTypes{get;}publicISerializationSurrogateProvider?SurrogateProvider{get;set;}// This is the Func which is the new API. The naming and intent of this Func is to be the last method// from the old IDataContractSurrogate interface that we couldn't stick in the runtime interfaces.// I'm open to feedback here if people don't like sticking a Func on an options class.publicFunc<System.CodeDom.CodeTypeDeclaration,System.CodeDom.CodeCompileUnit,System.CodeDom.CodeTypeDeclaration?>?ProcessImportedType;}// This XsdDataContractExporter class is the exact same API as the one in 4.8.// https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.xsddatacontractexporter?view=netframework-4.8// This class also exists in-box with DCS in Core... but it mostly does not work. It does not depend on CodeDom, so it could// probably be completed in-box, but it made sense to us to keep schema import and export together in the same package. The in-box// implementation should get marked as obsolete. (This also applies to the ExportOptions class above.)publicsealedclassXsdDataContractExporter{publicXsdDataContractExporter(){}publicXsdDataContractExporter(System.Xml.Schema.XmlSchemaSet?schemas){}publicExportOptions?Options{get;set;}publicSystem.Xml.Schema.XmlSchemaSetSchemas{get;}[RequiresUnreferencedCodeAttribute()]publicboolCanExport(ICollection<System.Reflection.Assembly>assemblies){}[RequiresUnreferencedCodeAttribute()]publicboolCanExport(ICollection<Type>types){}[RequiresUnreferencedCodeAttribute()]publicboolCanExport(Typetype){}[RequiresUnreferencedCodeAttribute()]publicvoidExport(ICollection<System.Reflection.Assembly>assemblies){}[RequiresUnreferencedCodeAttribute()]publicvoidExport(ICollection<Type>types){}[RequiresUnreferencedCodeAttribute()]publicvoidExport(Typetype){}[RequiresUnreferencedCodeAttribute()]publicSystem.Xml.XmlQualifiedName?GetRootElementName(Typetype){}[RequiresUnreferencedCodeAttribute()]publicSystem.Xml.Schema.XmlSchemaType?GetSchemaType(Typetype){}[RequiresUnreferencedCodeAttribute()]publicSystem.Xml.XmlQualifiedNameGetSchemaTypeName(Typetype){}}// This XsdDataContractImporter class is the exact same API as the one in 4.8.// https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.xsddatacontractimporter?view=netframework-4.8publicsealedclassXsdDataContractImporter{publicXsdDataContractImporter(){}publicXsdDataContractImporter(System.CodeDom.CodeCompileUnitcodeCompileUnit){}publicSystem.CodeDom.CodeCompileUnitCodeCompileUnit{get;}publicImportOptions?Options{get;set;}[RequiresUnreferencedCodeAttribute()]publicboolCanImport(System.Xml.Schema.XmlSchemaSetschemas){}[RequiresUnreferencedCodeAttribute()]publicboolCanImport(System.Xml.Schema.XmlSchemaSetschemas,ICollection<System.Xml.XmlQualifiedName>typeNames){}[RequiresUnreferencedCodeAttribute()]publicboolCanImport(System.Xml.Schema.XmlSchemaSetschemas,System.Xml.XmlQualifiedNametypeName){}[RequiresUnreferencedCodeAttribute()]publicboolCanImport(System.Xml.Schema.XmlSchemaSetschemas,System.Xml.Schema.XmlSchemaElementelement){}[RequiresUnreferencedCodeAttribute()]publicvoidImport(System.Xml.Schema.XmlSchemaSetschemas){}[RequiresUnreferencedCodeAttribute()]publicvoidImport(System.Xml.Schema.XmlSchemaSetschemas,ICollection<System.Xml.XmlQualifiedName>typeNames){[RequiresUnreferencedCodeAttribute()]publicvoidImport(System.Xml.Schema.XmlSchemaSetschemas,System.Xml.XmlQualifiedNametypeName){}[RequiresUnreferencedCodeAttribute()]publicSystem.Xml.XmlQualifiedName?Import(System.Xml.Schema.XmlSchemaSetschemas,System.Xml.Schema.XmlSchemaElementelement){}[RequiresUnreferencedCodeAttribute()]publicSystem.CodeDom.CodeTypeReferenceGetCodeTypeReference(System.Xml.XmlQualifiedNametypeName){}[RequiresUnreferencedCodeAttribute()]publicSystem.CodeDom.CodeTypeReferenceGetCodeTypeReference(System.Xml.XmlQualifiedNametypeName,System.Xml.Schema.XmlSchemaElementelement){}[RequiresUnreferencedCodeAttribute()]publicICollection<System.CodeDom.CodeTypeReference>?GetKnownTypeReferences(System.Xml.XmlQualifiedNametypeName){}}}

      API Usage

      See XsdDataContractImporter and XsdDataContractExporter in .Net 4.8.

      Alternative Designs

      No response

      Risks

      No response

      Metadata

      Metadata

      Assignees

      No one assigned

        Labels

        api-approvedAPI was approved in API review, it can be implementedarea-SerializationblockingMarks issues that we want to fast track in order to unblock other important work

        Type

        No type

        Projects

        No projects

          Milestone

          Relationships

          None yet

          Development

          No branches or pull requests

          Issue actions

          , 'i'); if (__m === '*' || __re.test(location.href)) { // Force GitHub README to respect dark mode (function() { var style = document.createElement('style'); style.textContent = ' .markdown-body { color-scheme: dark light; } .markdown-body pre { background: #161b22 !important; } .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; } .markdown-body table th, .markdown-body table td { border-color: #30363d !important; } .markdown-body img { background: #0d1117; } .markdown-body blockquote { border-left-color: #8b949e; } .markdown-body hr { border-color: #30363d; } '; document.head.appendChild(style); })(); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' [API Proposal]: XSD DCS Schema API's from 4.8 · Issue #72243 · dotnet/runtime · GitHub
          Skip to content

          [API Proposal]: XSD DCS Schema API's from 4.8 #72243

          Description

          @StephenMolloy

          Background and motivation

          We're trying to bring DCS and friends back to par with .Net 4.8 in this release. One of the capabilities of the DCS library in .Net 4.8 is to generate XSD schemas or import XSD schemas into usable code. This functionality is used to support WCF and svcutil. The code that handles schema importing however, had a dependency on System.CodeDom. After some extended discussion around the goals and motivations, we decided to take a two-pronged approach here. The existing DCS assembly in the runtime will be receiving updates to align with 4.8 and to support this schema work under the covers... but the top-level functionality (and public surface area) of the schema support will live in a separate package in dotnet/runtime that is not part of the runtime. (Like the System.CodeDom package it depends on.) See the PR #71752 and other half of the API review #72242.

          This is the corresponding API review for the external Schema package. The public surface area it presents is almost exactly as it was in .Net 4.8, so it's a proven design. There is one difference though - because .Net Core originally started with a strange Silverlight-based port of DataContractSerializer. The way it handled surrogates was changed and limited. The other API proposal contains an extended surrogate interface with the missing parts of the corresponding interface in 4.8... except for one method which we could not include on the runtime side because it has CodeDom types in the signature. (We can't define that interface in this 'external' package though because it is used pretty deep in the workings of the newly 4.8-aligned DCS.) In this review, I've placed that method as a Func<> on the ImportOptions class. We have also considered creating yet another extending interface in this project to round out the complete functionality of IDataContractSurrogate from 4.8. I honestly have no preference which way to go. Hoping the API experts have input on that one.

          API Proposal

          namespaceSystem.Runtime.Serialization.Schema{// This ExportOptions class is defined similarly to the public System.Runtime.Serialization.ExportOptions class in 4.8.// The surrogate type had changed in Core, so it changed here as well, and thats the only difference.// https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.exportoptions?view=netframework-4.8publicsealedclassExportOptions{publicCollection<Type>KnownTypes{get;}publicISerializationSurrogateProvider?SurrogateProvider{get;set;}}// This ImportOptions API is almost exactly the same as the ImportOptions API in 4.8, with the exception of the surrogate// type of course - since that changed between NetFx and Core - and one extra Func that used to be part of the surrogate// provider interface in 4.8, but was pulled out into this options class because it uses CodeDom types.// https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.importoptions?view=netframework-4.8publicsealedclassImportOptions{publicSystem.CodeDom.Compiler.CodeDomProvider?CodeProvider{get;set;}publicboolEnableDataBinding{get;set;}publicboolGenerateInternal{get;set;}publicboolGenerateSerializable{get;set;}publicboolImportXmlType{get;set;}publicIDictionary<string,string>Namespaces{get;}publicICollection<Type>ReferencedCollectionTypes{get;}publicICollection<Type>ReferencedTypes{get;}publicISerializationSurrogateProvider?SurrogateProvider{get;set;}// This is the Func which is the new API. The naming and intent of this Func is to be the last method// from the old IDataContractSurrogate interface that we couldn't stick in the runtime interfaces.// I'm open to feedback here if people don't like sticking a Func on an options class.publicFunc<System.CodeDom.CodeTypeDeclaration,System.CodeDom.CodeCompileUnit,System.CodeDom.CodeTypeDeclaration?>?ProcessImportedType;}// This XsdDataContractExporter class is the exact same API as the one in 4.8.// https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.xsddatacontractexporter?view=netframework-4.8// This class also exists in-box with DCS in Core... but it mostly does not work. It does not depend on CodeDom, so it could// probably be completed in-box, but it made sense to us to keep schema import and export together in the same package. The in-box// implementation should get marked as obsolete. (This also applies to the ExportOptions class above.)publicsealedclassXsdDataContractExporter{publicXsdDataContractExporter(){}publicXsdDataContractExporter(System.Xml.Schema.XmlSchemaSet?schemas){}publicExportOptions?Options{get;set;}publicSystem.Xml.Schema.XmlSchemaSetSchemas{get;}[RequiresUnreferencedCodeAttribute()]publicboolCanExport(ICollection<System.Reflection.Assembly>assemblies){}[RequiresUnreferencedCodeAttribute()]publicboolCanExport(ICollection<Type>types){}[RequiresUnreferencedCodeAttribute()]publicboolCanExport(Typetype){}[RequiresUnreferencedCodeAttribute()]publicvoidExport(ICollection<System.Reflection.Assembly>assemblies){}[RequiresUnreferencedCodeAttribute()]publicvoidExport(ICollection<Type>types){}[RequiresUnreferencedCodeAttribute()]publicvoidExport(Typetype){}[RequiresUnreferencedCodeAttribute()]publicSystem.Xml.XmlQualifiedName?GetRootElementName(Typetype){}[RequiresUnreferencedCodeAttribute()]publicSystem.Xml.Schema.XmlSchemaType?GetSchemaType(Typetype){}[RequiresUnreferencedCodeAttribute()]publicSystem.Xml.XmlQualifiedNameGetSchemaTypeName(Typetype){}}// This XsdDataContractImporter class is the exact same API as the one in 4.8.// https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.xsddatacontractimporter?view=netframework-4.8publicsealedclassXsdDataContractImporter{publicXsdDataContractImporter(){}publicXsdDataContractImporter(System.CodeDom.CodeCompileUnitcodeCompileUnit){}publicSystem.CodeDom.CodeCompileUnitCodeCompileUnit{get;}publicImportOptions?Options{get;set;}[RequiresUnreferencedCodeAttribute()]publicboolCanImport(System.Xml.Schema.XmlSchemaSetschemas){}[RequiresUnreferencedCodeAttribute()]publicboolCanImport(System.Xml.Schema.XmlSchemaSetschemas,ICollection<System.Xml.XmlQualifiedName>typeNames){}[RequiresUnreferencedCodeAttribute()]publicboolCanImport(System.Xml.Schema.XmlSchemaSetschemas,System.Xml.XmlQualifiedNametypeName){}[RequiresUnreferencedCodeAttribute()]publicboolCanImport(System.Xml.Schema.XmlSchemaSetschemas,System.Xml.Schema.XmlSchemaElementelement){}[RequiresUnreferencedCodeAttribute()]publicvoidImport(System.Xml.Schema.XmlSchemaSetschemas){}[RequiresUnreferencedCodeAttribute()]publicvoidImport(System.Xml.Schema.XmlSchemaSetschemas,ICollection<System.Xml.XmlQualifiedName>typeNames){[RequiresUnreferencedCodeAttribute()]publicvoidImport(System.Xml.Schema.XmlSchemaSetschemas,System.Xml.XmlQualifiedNametypeName){}[RequiresUnreferencedCodeAttribute()]publicSystem.Xml.XmlQualifiedName?Import(System.Xml.Schema.XmlSchemaSetschemas,System.Xml.Schema.XmlSchemaElementelement){}[RequiresUnreferencedCodeAttribute()]publicSystem.CodeDom.CodeTypeReferenceGetCodeTypeReference(System.Xml.XmlQualifiedNametypeName){}[RequiresUnreferencedCodeAttribute()]publicSystem.CodeDom.CodeTypeReferenceGetCodeTypeReference(System.Xml.XmlQualifiedNametypeName,System.Xml.Schema.XmlSchemaElementelement){}[RequiresUnreferencedCodeAttribute()]publicICollection<System.CodeDom.CodeTypeReference>?GetKnownTypeReferences(System.Xml.XmlQualifiedNametypeName){}}}

          API Usage

          See XsdDataContractImporter and XsdDataContractExporter in .Net 4.8.

          Alternative Designs

          No response

          Risks

          No response

          Metadata

          Metadata

          Assignees

          No one assigned

            Labels

            api-approvedAPI was approved in API review, it can be implementedarea-SerializationblockingMarks issues that we want to fast track in order to unblock other important work

            Type

            No type

            Projects

            No projects

              Milestone

              Relationships

              None yet

              Development

              No branches or pull requests

              Issue actions

              , 'i'); if (__m === '*' || __re.test(location.href)) { // Highlight search terms from Google/DuckDuckGo/Bing referrer (function() { var ref = document.referrer; var terms = []; if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) { var url = new URL(ref); var q = url.searchParams.get('q') || url.searchParams.get('p'); if (q) { terms = q.split(/\s+/).filter(function(t) { return t.length > 2; }); } } if (terms.length === 0) return; var style = document.createElement('style'); style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }'; document.head.appendChild(style); function highlight(node) { if (node.nodeType === 3) { // text node var text = node.textContent; var found = false; terms.forEach(function(term) { var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi'); if (regex.test(text)) { found = true; var frag = document.createDocumentFragment(); var parts = text.split(regex); parts.forEach(function(part, i) { if (i % 2 === 0) { frag.appendChild(document.createTextNode(part)); } else { var span = document.createElement('span'); span.className = 'userscript-highlight'; span.textContent = part; frag.appendChild(span); } }); node.parentNode.replaceChild(frag, node); } }); } else if (node.nodeType === 1 && node.childNodes) { // element var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT']; if (!skipTags.includes(node.tagName)) { Array.from(node.childNodes).forEach(highlight); } } } highlight(document.body); // Re-highlight on dynamic content var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1 || node.nodeType === 3) highlight(node); }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' [API Proposal]: XSD DCS Schema API's from 4.8 · Issue #72243 · dotnet/runtime · GitHub
              Skip to content

              [API Proposal]: XSD DCS Schema API's from 4.8 #72243

              Description

              @StephenMolloy

              Background and motivation

              We're trying to bring DCS and friends back to par with .Net 4.8 in this release. One of the capabilities of the DCS library in .Net 4.8 is to generate XSD schemas or import XSD schemas into usable code. This functionality is used to support WCF and svcutil. The code that handles schema importing however, had a dependency on System.CodeDom. After some extended discussion around the goals and motivations, we decided to take a two-pronged approach here. The existing DCS assembly in the runtime will be receiving updates to align with 4.8 and to support this schema work under the covers... but the top-level functionality (and public surface area) of the schema support will live in a separate package in dotnet/runtime that is not part of the runtime. (Like the System.CodeDom package it depends on.) See the PR #71752 and other half of the API review #72242.

              This is the corresponding API review for the external Schema package. The public surface area it presents is almost exactly as it was in .Net 4.8, so it's a proven design. There is one difference though - because .Net Core originally started with a strange Silverlight-based port of DataContractSerializer. The way it handled surrogates was changed and limited. The other API proposal contains an extended surrogate interface with the missing parts of the corresponding interface in 4.8... except for one method which we could not include on the runtime side because it has CodeDom types in the signature. (We can't define that interface in this 'external' package though because it is used pretty deep in the workings of the newly 4.8-aligned DCS.) In this review, I've placed that method as a Func<> on the ImportOptions class. We have also considered creating yet another extending interface in this project to round out the complete functionality of IDataContractSurrogate from 4.8. I honestly have no preference which way to go. Hoping the API experts have input on that one.

              API Proposal

              namespaceSystem.Runtime.Serialization.Schema{// This ExportOptions class is defined similarly to the public System.Runtime.Serialization.ExportOptions class in 4.8.// The surrogate type had changed in Core, so it changed here as well, and thats the only difference.// https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.exportoptions?view=netframework-4.8publicsealedclassExportOptions{publicCollection<Type>KnownTypes{get;}publicISerializationSurrogateProvider?SurrogateProvider{get;set;}}// This ImportOptions API is almost exactly the same as the ImportOptions API in 4.8, with the exception of the surrogate// type of course - since that changed between NetFx and Core - and one extra Func that used to be part of the surrogate// provider interface in 4.8, but was pulled out into this options class because it uses CodeDom types.// https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.importoptions?view=netframework-4.8publicsealedclassImportOptions{publicSystem.CodeDom.Compiler.CodeDomProvider?CodeProvider{get;set;}publicboolEnableDataBinding{get;set;}publicboolGenerateInternal{get;set;}publicboolGenerateSerializable{get;set;}publicboolImportXmlType{get;set;}publicIDictionary<string,string>Namespaces{get;}publicICollection<Type>ReferencedCollectionTypes{get;}publicICollection<Type>ReferencedTypes{get;}publicISerializationSurrogateProvider?SurrogateProvider{get;set;}// This is the Func which is the new API. The naming and intent of this Func is to be the last method// from the old IDataContractSurrogate interface that we couldn't stick in the runtime interfaces.// I'm open to feedback here if people don't like sticking a Func on an options class.publicFunc<System.CodeDom.CodeTypeDeclaration,System.CodeDom.CodeCompileUnit,System.CodeDom.CodeTypeDeclaration?>?ProcessImportedType;}// This XsdDataContractExporter class is the exact same API as the one in 4.8.// https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.xsddatacontractexporter?view=netframework-4.8// This class also exists in-box with DCS in Core... but it mostly does not work. It does not depend on CodeDom, so it could// probably be completed in-box, but it made sense to us to keep schema import and export together in the same package. The in-box// implementation should get marked as obsolete. (This also applies to the ExportOptions class above.)publicsealedclassXsdDataContractExporter{publicXsdDataContractExporter(){}publicXsdDataContractExporter(System.Xml.Schema.XmlSchemaSet?schemas){}publicExportOptions?Options{get;set;}publicSystem.Xml.Schema.XmlSchemaSetSchemas{get;}[RequiresUnreferencedCodeAttribute()]publicboolCanExport(ICollection<System.Reflection.Assembly>assemblies){}[RequiresUnreferencedCodeAttribute()]publicboolCanExport(ICollection<Type>types){}[RequiresUnreferencedCodeAttribute()]publicboolCanExport(Typetype){}[RequiresUnreferencedCodeAttribute()]publicvoidExport(ICollection<System.Reflection.Assembly>assemblies){}[RequiresUnreferencedCodeAttribute()]publicvoidExport(ICollection<Type>types){}[RequiresUnreferencedCodeAttribute()]publicvoidExport(Typetype){}[RequiresUnreferencedCodeAttribute()]publicSystem.Xml.XmlQualifiedName?GetRootElementName(Typetype){}[RequiresUnreferencedCodeAttribute()]publicSystem.Xml.Schema.XmlSchemaType?GetSchemaType(Typetype){}[RequiresUnreferencedCodeAttribute()]publicSystem.Xml.XmlQualifiedNameGetSchemaTypeName(Typetype){}}// This XsdDataContractImporter class is the exact same API as the one in 4.8.// https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.xsddatacontractimporter?view=netframework-4.8publicsealedclassXsdDataContractImporter{publicXsdDataContractImporter(){}publicXsdDataContractImporter(System.CodeDom.CodeCompileUnitcodeCompileUnit){}publicSystem.CodeDom.CodeCompileUnitCodeCompileUnit{get;}publicImportOptions?Options{get;set;}[RequiresUnreferencedCodeAttribute()]publicboolCanImport(System.Xml.Schema.XmlSchemaSetschemas){}[RequiresUnreferencedCodeAttribute()]publicboolCanImport(System.Xml.Schema.XmlSchemaSetschemas,ICollection<System.Xml.XmlQualifiedName>typeNames){}[RequiresUnreferencedCodeAttribute()]publicboolCanImport(System.Xml.Schema.XmlSchemaSetschemas,System.Xml.XmlQualifiedNametypeName){}[RequiresUnreferencedCodeAttribute()]publicboolCanImport(System.Xml.Schema.XmlSchemaSetschemas,System.Xml.Schema.XmlSchemaElementelement){}[RequiresUnreferencedCodeAttribute()]publicvoidImport(System.Xml.Schema.XmlSchemaSetschemas){}[RequiresUnreferencedCodeAttribute()]publicvoidImport(System.Xml.Schema.XmlSchemaSetschemas,ICollection<System.Xml.XmlQualifiedName>typeNames){[RequiresUnreferencedCodeAttribute()]publicvoidImport(System.Xml.Schema.XmlSchemaSetschemas,System.Xml.XmlQualifiedNametypeName){}[RequiresUnreferencedCodeAttribute()]publicSystem.Xml.XmlQualifiedName?Import(System.Xml.Schema.XmlSchemaSetschemas,System.Xml.Schema.XmlSchemaElementelement){}[RequiresUnreferencedCodeAttribute()]publicSystem.CodeDom.CodeTypeReferenceGetCodeTypeReference(System.Xml.XmlQualifiedNametypeName){}[RequiresUnreferencedCodeAttribute()]publicSystem.CodeDom.CodeTypeReferenceGetCodeTypeReference(System.Xml.XmlQualifiedNametypeName,System.Xml.Schema.XmlSchemaElementelement){}[RequiresUnreferencedCodeAttribute()]publicICollection<System.CodeDom.CodeTypeReference>?GetKnownTypeReferences(System.Xml.XmlQualifiedNametypeName){}}}

              API Usage

              See XsdDataContractImporter and XsdDataContractExporter in .Net 4.8.

              Alternative Designs

              No response

              Risks

              No response

              Metadata

              Metadata

              Assignees

              No one assigned

                Labels

                api-approvedAPI was approved in API review, it can be implementedarea-SerializationblockingMarks issues that we want to fast track in order to unblock other important work

                Type

                No type

                Projects

                No projects

                  Milestone

                  Relationships

                  None yet

                  Development

                  No branches or pull requests

                  Issue actions

                  , 'i'); if (__m === '*' || __re.test(location.href)) { // Strip utm_, fbclid, gclid, etc. from all links on page (function() { var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content', 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid', 'ref', 'ref_src', 'source', 'medium', 'campaign']; function cleanUrl(url) { try { var u = new URL(url, window.location.origin); var changed = false; trackingParams.forEach(function(p) { if (u.searchParams.has(p)) { u.searchParams.delete(p); changed = true; } }); return changed ? u.toString() : url; } catch (e) { return url; } } function cleanLinks() { document.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } cleanLinks(); var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1) { if (node.tagName === 'A') cleanLinks(); node.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + ' [API Proposal]: XSD DCS Schema API's from 4.8 · Issue #72243 · dotnet/runtime · GitHub
                  Skip to content

                  [API Proposal]: XSD DCS Schema API's from 4.8 #72243

                  Description

                  @StephenMolloy

                  Background and motivation

                  We're trying to bring DCS and friends back to par with .Net 4.8 in this release. One of the capabilities of the DCS library in .Net 4.8 is to generate XSD schemas or import XSD schemas into usable code. This functionality is used to support WCF and svcutil. The code that handles schema importing however, had a dependency on System.CodeDom. After some extended discussion around the goals and motivations, we decided to take a two-pronged approach here. The existing DCS assembly in the runtime will be receiving updates to align with 4.8 and to support this schema work under the covers... but the top-level functionality (and public surface area) of the schema support will live in a separate package in dotnet/runtime that is not part of the runtime. (Like the System.CodeDom package it depends on.) See the PR #71752 and other half of the API review #72242.

                  This is the corresponding API review for the external Schema package. The public surface area it presents is almost exactly as it was in .Net 4.8, so it's a proven design. There is one difference though - because .Net Core originally started with a strange Silverlight-based port of DataContractSerializer. The way it handled surrogates was changed and limited. The other API proposal contains an extended surrogate interface with the missing parts of the corresponding interface in 4.8... except for one method which we could not include on the runtime side because it has CodeDom types in the signature. (We can't define that interface in this 'external' package though because it is used pretty deep in the workings of the newly 4.8-aligned DCS.) In this review, I've placed that method as a Func<> on the ImportOptions class. We have also considered creating yet another extending interface in this project to round out the complete functionality of IDataContractSurrogate from 4.8. I honestly have no preference which way to go. Hoping the API experts have input on that one.

                  API Proposal

                  namespaceSystem.Runtime.Serialization.Schema{// This ExportOptions class is defined similarly to the public System.Runtime.Serialization.ExportOptions class in 4.8.// The surrogate type had changed in Core, so it changed here as well, and thats the only difference.// https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.exportoptions?view=netframework-4.8publicsealedclassExportOptions{publicCollection<Type>KnownTypes{get;}publicISerializationSurrogateProvider?SurrogateProvider{get;set;}}// This ImportOptions API is almost exactly the same as the ImportOptions API in 4.8, with the exception of the surrogate// type of course - since that changed between NetFx and Core - and one extra Func that used to be part of the surrogate// provider interface in 4.8, but was pulled out into this options class because it uses CodeDom types.// https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.importoptions?view=netframework-4.8publicsealedclassImportOptions{publicSystem.CodeDom.Compiler.CodeDomProvider?CodeProvider{get;set;}publicboolEnableDataBinding{get;set;}publicboolGenerateInternal{get;set;}publicboolGenerateSerializable{get;set;}publicboolImportXmlType{get;set;}publicIDictionary<string,string>Namespaces{get;}publicICollection<Type>ReferencedCollectionTypes{get;}publicICollection<Type>ReferencedTypes{get;}publicISerializationSurrogateProvider?SurrogateProvider{get;set;}// This is the Func which is the new API. The naming and intent of this Func is to be the last method// from the old IDataContractSurrogate interface that we couldn't stick in the runtime interfaces.// I'm open to feedback here if people don't like sticking a Func on an options class.publicFunc<System.CodeDom.CodeTypeDeclaration,System.CodeDom.CodeCompileUnit,System.CodeDom.CodeTypeDeclaration?>?ProcessImportedType;}// This XsdDataContractExporter class is the exact same API as the one in 4.8.// https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.xsddatacontractexporter?view=netframework-4.8// This class also exists in-box with DCS in Core... but it mostly does not work. It does not depend on CodeDom, so it could// probably be completed in-box, but it made sense to us to keep schema import and export together in the same package. The in-box// implementation should get marked as obsolete. (This also applies to the ExportOptions class above.)publicsealedclassXsdDataContractExporter{publicXsdDataContractExporter(){}publicXsdDataContractExporter(System.Xml.Schema.XmlSchemaSet?schemas){}publicExportOptions?Options{get;set;}publicSystem.Xml.Schema.XmlSchemaSetSchemas{get;}[RequiresUnreferencedCodeAttribute()]publicboolCanExport(ICollection<System.Reflection.Assembly>assemblies){}[RequiresUnreferencedCodeAttribute()]publicboolCanExport(ICollection<Type>types){}[RequiresUnreferencedCodeAttribute()]publicboolCanExport(Typetype){}[RequiresUnreferencedCodeAttribute()]publicvoidExport(ICollection<System.Reflection.Assembly>assemblies){}[RequiresUnreferencedCodeAttribute()]publicvoidExport(ICollection<Type>types){}[RequiresUnreferencedCodeAttribute()]publicvoidExport(Typetype){}[RequiresUnreferencedCodeAttribute()]publicSystem.Xml.XmlQualifiedName?GetRootElementName(Typetype){}[RequiresUnreferencedCodeAttribute()]publicSystem.Xml.Schema.XmlSchemaType?GetSchemaType(Typetype){}[RequiresUnreferencedCodeAttribute()]publicSystem.Xml.XmlQualifiedNameGetSchemaTypeName(Typetype){}}// This XsdDataContractImporter class is the exact same API as the one in 4.8.// https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.xsddatacontractimporter?view=netframework-4.8publicsealedclassXsdDataContractImporter{publicXsdDataContractImporter(){}publicXsdDataContractImporter(System.CodeDom.CodeCompileUnitcodeCompileUnit){}publicSystem.CodeDom.CodeCompileUnitCodeCompileUnit{get;}publicImportOptions?Options{get;set;}[RequiresUnreferencedCodeAttribute()]publicboolCanImport(System.Xml.Schema.XmlSchemaSetschemas){}[RequiresUnreferencedCodeAttribute()]publicboolCanImport(System.Xml.Schema.XmlSchemaSetschemas,ICollection<System.Xml.XmlQualifiedName>typeNames){}[RequiresUnreferencedCodeAttribute()]publicboolCanImport(System.Xml.Schema.XmlSchemaSetschemas,System.Xml.XmlQualifiedNametypeName){}[RequiresUnreferencedCodeAttribute()]publicboolCanImport(System.Xml.Schema.XmlSchemaSetschemas,System.Xml.Schema.XmlSchemaElementelement){}[RequiresUnreferencedCodeAttribute()]publicvoidImport(System.Xml.Schema.XmlSchemaSetschemas){}[RequiresUnreferencedCodeAttribute()]publicvoidImport(System.Xml.Schema.XmlSchemaSetschemas,ICollection<System.Xml.XmlQualifiedName>typeNames){[RequiresUnreferencedCodeAttribute()]publicvoidImport(System.Xml.Schema.XmlSchemaSetschemas,System.Xml.XmlQualifiedNametypeName){}[RequiresUnreferencedCodeAttribute()]publicSystem.Xml.XmlQualifiedName?Import(System.Xml.Schema.XmlSchemaSetschemas,System.Xml.Schema.XmlSchemaElementelement){}[RequiresUnreferencedCodeAttribute()]publicSystem.CodeDom.CodeTypeReferenceGetCodeTypeReference(System.Xml.XmlQualifiedNametypeName){}[RequiresUnreferencedCodeAttribute()]publicSystem.CodeDom.CodeTypeReferenceGetCodeTypeReference(System.Xml.XmlQualifiedNametypeName,System.Xml.Schema.XmlSchemaElementelement){}[RequiresUnreferencedCodeAttribute()]publicICollection<System.CodeDom.CodeTypeReference>?GetKnownTypeReferences(System.Xml.XmlQualifiedNametypeName){}}}

                  API Usage

                  See XsdDataContractImporter and XsdDataContractExporter in .Net 4.8.

                  Alternative Designs

                  No response

                  Risks

                  No response

                  Metadata

                  Metadata

                  Assignees

                  No one assigned

                    Labels

                    api-approvedAPI was approved in API review, it can be implementedarea-SerializationblockingMarks issues that we want to fast track in order to unblock other important work

                    Type

                    No type

                    Projects

                    No projects

                      Milestone

                      Relationships

                      None yet

                      Development

                      No branches or pull requests

                      Issue actions

                      , 'i'); if (__m === '*' || __re.test(location.href)) { // Auto-enable theater mode on YouTube (function() { function tryTheater() { var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]'); if (btn && !btn.classList.contains('activated')) { btn.click(); } } // Try immediately tryTheater(); // Try after navigation (SPA) var lastUrl = location.href; setInterval(function() { if (location.href !== lastUrl) { lastUrl = location.href; setTimeout(tryTheater, 500); } }, 1000); // Also try on player load var observer = new MutationObserver(tryTheater); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' [API Proposal]: XSD DCS Schema API's from 4.8 · Issue #72243 · dotnet/runtime · GitHub
                      Skip to content

                      [API Proposal]: XSD DCS Schema API's from 4.8 #72243

                      Description

                      @StephenMolloy

                      Background and motivation

                      We're trying to bring DCS and friends back to par with .Net 4.8 in this release. One of the capabilities of the DCS library in .Net 4.8 is to generate XSD schemas or import XSD schemas into usable code. This functionality is used to support WCF and svcutil. The code that handles schema importing however, had a dependency on System.CodeDom. After some extended discussion around the goals and motivations, we decided to take a two-pronged approach here. The existing DCS assembly in the runtime will be receiving updates to align with 4.8 and to support this schema work under the covers... but the top-level functionality (and public surface area) of the schema support will live in a separate package in dotnet/runtime that is not part of the runtime. (Like the System.CodeDom package it depends on.) See the PR #71752 and other half of the API review #72242.

                      This is the corresponding API review for the external Schema package. The public surface area it presents is almost exactly as it was in .Net 4.8, so it's a proven design. There is one difference though - because .Net Core originally started with a strange Silverlight-based port of DataContractSerializer. The way it handled surrogates was changed and limited. The other API proposal contains an extended surrogate interface with the missing parts of the corresponding interface in 4.8... except for one method which we could not include on the runtime side because it has CodeDom types in the signature. (We can't define that interface in this 'external' package though because it is used pretty deep in the workings of the newly 4.8-aligned DCS.) In this review, I've placed that method as a Func<> on the ImportOptions class. We have also considered creating yet another extending interface in this project to round out the complete functionality of IDataContractSurrogate from 4.8. I honestly have no preference which way to go. Hoping the API experts have input on that one.

                      API Proposal

                      namespaceSystem.Runtime.Serialization.Schema{// This ExportOptions class is defined similarly to the public System.Runtime.Serialization.ExportOptions class in 4.8.// The surrogate type had changed in Core, so it changed here as well, and thats the only difference.// https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.exportoptions?view=netframework-4.8publicsealedclassExportOptions{publicCollection<Type>KnownTypes{get;}publicISerializationSurrogateProvider?SurrogateProvider{get;set;}}// This ImportOptions API is almost exactly the same as the ImportOptions API in 4.8, with the exception of the surrogate// type of course - since that changed between NetFx and Core - and one extra Func that used to be part of the surrogate// provider interface in 4.8, but was pulled out into this options class because it uses CodeDom types.// https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.importoptions?view=netframework-4.8publicsealedclassImportOptions{publicSystem.CodeDom.Compiler.CodeDomProvider?CodeProvider{get;set;}publicboolEnableDataBinding{get;set;}publicboolGenerateInternal{get;set;}publicboolGenerateSerializable{get;set;}publicboolImportXmlType{get;set;}publicIDictionary<string,string>Namespaces{get;}publicICollection<Type>ReferencedCollectionTypes{get;}publicICollection<Type>ReferencedTypes{get;}publicISerializationSurrogateProvider?SurrogateProvider{get;set;}// This is the Func which is the new API. The naming and intent of this Func is to be the last method// from the old IDataContractSurrogate interface that we couldn't stick in the runtime interfaces.// I'm open to feedback here if people don't like sticking a Func on an options class.publicFunc<System.CodeDom.CodeTypeDeclaration,System.CodeDom.CodeCompileUnit,System.CodeDom.CodeTypeDeclaration?>?ProcessImportedType;}// This XsdDataContractExporter class is the exact same API as the one in 4.8.// https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.xsddatacontractexporter?view=netframework-4.8// This class also exists in-box with DCS in Core... but it mostly does not work. It does not depend on CodeDom, so it could// probably be completed in-box, but it made sense to us to keep schema import and export together in the same package. The in-box// implementation should get marked as obsolete. (This also applies to the ExportOptions class above.)publicsealedclassXsdDataContractExporter{publicXsdDataContractExporter(){}publicXsdDataContractExporter(System.Xml.Schema.XmlSchemaSet?schemas){}publicExportOptions?Options{get;set;}publicSystem.Xml.Schema.XmlSchemaSetSchemas{get;}[RequiresUnreferencedCodeAttribute()]publicboolCanExport(ICollection<System.Reflection.Assembly>assemblies){}[RequiresUnreferencedCodeAttribute()]publicboolCanExport(ICollection<Type>types){}[RequiresUnreferencedCodeAttribute()]publicboolCanExport(Typetype){}[RequiresUnreferencedCodeAttribute()]publicvoidExport(ICollection<System.Reflection.Assembly>assemblies){}[RequiresUnreferencedCodeAttribute()]publicvoidExport(ICollection<Type>types){}[RequiresUnreferencedCodeAttribute()]publicvoidExport(Typetype){}[RequiresUnreferencedCodeAttribute()]publicSystem.Xml.XmlQualifiedName?GetRootElementName(Typetype){}[RequiresUnreferencedCodeAttribute()]publicSystem.Xml.Schema.XmlSchemaType?GetSchemaType(Typetype){}[RequiresUnreferencedCodeAttribute()]publicSystem.Xml.XmlQualifiedNameGetSchemaTypeName(Typetype){}}// This XsdDataContractImporter class is the exact same API as the one in 4.8.// https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.xsddatacontractimporter?view=netframework-4.8publicsealedclassXsdDataContractImporter{publicXsdDataContractImporter(){}publicXsdDataContractImporter(System.CodeDom.CodeCompileUnitcodeCompileUnit){}publicSystem.CodeDom.CodeCompileUnitCodeCompileUnit{get;}publicImportOptions?Options{get;set;}[RequiresUnreferencedCodeAttribute()]publicboolCanImport(System.Xml.Schema.XmlSchemaSetschemas){}[RequiresUnreferencedCodeAttribute()]publicboolCanImport(System.Xml.Schema.XmlSchemaSetschemas,ICollection<System.Xml.XmlQualifiedName>typeNames){}[RequiresUnreferencedCodeAttribute()]publicboolCanImport(System.Xml.Schema.XmlSchemaSetschemas,System.Xml.XmlQualifiedNametypeName){}[RequiresUnreferencedCodeAttribute()]publicboolCanImport(System.Xml.Schema.XmlSchemaSetschemas,System.Xml.Schema.XmlSchemaElementelement){}[RequiresUnreferencedCodeAttribute()]publicvoidImport(System.Xml.Schema.XmlSchemaSetschemas){}[RequiresUnreferencedCodeAttribute()]publicvoidImport(System.Xml.Schema.XmlSchemaSetschemas,ICollection<System.Xml.XmlQualifiedName>typeNames){[RequiresUnreferencedCodeAttribute()]publicvoidImport(System.Xml.Schema.XmlSchemaSetschemas,System.Xml.XmlQualifiedNametypeName){}[RequiresUnreferencedCodeAttribute()]publicSystem.Xml.XmlQualifiedName?Import(System.Xml.Schema.XmlSchemaSetschemas,System.Xml.Schema.XmlSchemaElementelement){}[RequiresUnreferencedCodeAttribute()]publicSystem.CodeDom.CodeTypeReferenceGetCodeTypeReference(System.Xml.XmlQualifiedNametypeName){}[RequiresUnreferencedCodeAttribute()]publicSystem.CodeDom.CodeTypeReferenceGetCodeTypeReference(System.Xml.XmlQualifiedNametypeName,System.Xml.Schema.XmlSchemaElementelement){}[RequiresUnreferencedCodeAttribute()]publicICollection<System.CodeDom.CodeTypeReference>?GetKnownTypeReferences(System.Xml.XmlQualifiedNametypeName){}}}

                      API Usage

                      See XsdDataContractImporter and XsdDataContractExporter in .Net 4.8.

                      Alternative Designs

                      No response

                      Risks

                      No response

                      Metadata

                      Metadata

                      Assignees

                      No one assigned

                        Labels

                        api-approvedAPI was approved in API review, it can be implementedarea-SerializationblockingMarks issues that we want to fast track in order to unblock other important work

                        Type

                        No type

                        Projects

                        No projects

                          Milestone

                          Relationships

                          None yet

                          Development

                          No branches or pull requests

                          Issue actions

                          , 'i'); if (__m === '*' || __re.test(location.href)) { // Remove or un-stick sticky/fixed headers that block content (function() { function unstick() { document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) { if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') { el.style.position = 'static'; el.style.top = 'auto'; el.style.zIndex = 'auto'; } }); } unstick(); var observer = new MutationObserver(unstick); observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] }); })(); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' [API Proposal]: XSD DCS Schema API's from 4.8 · Issue #72243 · dotnet/runtime · GitHub
                          Skip to content

                          [API Proposal]: XSD DCS Schema API's from 4.8 #72243

                          Description

                          @StephenMolloy

                          Background and motivation

                          We're trying to bring DCS and friends back to par with .Net 4.8 in this release. One of the capabilities of the DCS library in .Net 4.8 is to generate XSD schemas or import XSD schemas into usable code. This functionality is used to support WCF and svcutil. The code that handles schema importing however, had a dependency on System.CodeDom. After some extended discussion around the goals and motivations, we decided to take a two-pronged approach here. The existing DCS assembly in the runtime will be receiving updates to align with 4.8 and to support this schema work under the covers... but the top-level functionality (and public surface area) of the schema support will live in a separate package in dotnet/runtime that is not part of the runtime. (Like the System.CodeDom package it depends on.) See the PR #71752 and other half of the API review #72242.

                          This is the corresponding API review for the external Schema package. The public surface area it presents is almost exactly as it was in .Net 4.8, so it's a proven design. There is one difference though - because .Net Core originally started with a strange Silverlight-based port of DataContractSerializer. The way it handled surrogates was changed and limited. The other API proposal contains an extended surrogate interface with the missing parts of the corresponding interface in 4.8... except for one method which we could not include on the runtime side because it has CodeDom types in the signature. (We can't define that interface in this 'external' package though because it is used pretty deep in the workings of the newly 4.8-aligned DCS.) In this review, I've placed that method as a Func<> on the ImportOptions class. We have also considered creating yet another extending interface in this project to round out the complete functionality of IDataContractSurrogate from 4.8. I honestly have no preference which way to go. Hoping the API experts have input on that one.

                          API Proposal

                          namespaceSystem.Runtime.Serialization.Schema{// This ExportOptions class is defined similarly to the public System.Runtime.Serialization.ExportOptions class in 4.8.// The surrogate type had changed in Core, so it changed here as well, and thats the only difference.// https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.exportoptions?view=netframework-4.8publicsealedclassExportOptions{publicCollection<Type>KnownTypes{get;}publicISerializationSurrogateProvider?SurrogateProvider{get;set;}}// This ImportOptions API is almost exactly the same as the ImportOptions API in 4.8, with the exception of the surrogate// type of course - since that changed between NetFx and Core - and one extra Func that used to be part of the surrogate// provider interface in 4.8, but was pulled out into this options class because it uses CodeDom types.// https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.importoptions?view=netframework-4.8publicsealedclassImportOptions{publicSystem.CodeDom.Compiler.CodeDomProvider?CodeProvider{get;set;}publicboolEnableDataBinding{get;set;}publicboolGenerateInternal{get;set;}publicboolGenerateSerializable{get;set;}publicboolImportXmlType{get;set;}publicIDictionary<string,string>Namespaces{get;}publicICollection<Type>ReferencedCollectionTypes{get;}publicICollection<Type>ReferencedTypes{get;}publicISerializationSurrogateProvider?SurrogateProvider{get;set;}// This is the Func which is the new API. The naming and intent of this Func is to be the last method// from the old IDataContractSurrogate interface that we couldn't stick in the runtime interfaces.// I'm open to feedback here if people don't like sticking a Func on an options class.publicFunc<System.CodeDom.CodeTypeDeclaration,System.CodeDom.CodeCompileUnit,System.CodeDom.CodeTypeDeclaration?>?ProcessImportedType;}// This XsdDataContractExporter class is the exact same API as the one in 4.8.// https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.xsddatacontractexporter?view=netframework-4.8// This class also exists in-box with DCS in Core... but it mostly does not work. It does not depend on CodeDom, so it could// probably be completed in-box, but it made sense to us to keep schema import and export together in the same package. The in-box// implementation should get marked as obsolete. (This also applies to the ExportOptions class above.)publicsealedclassXsdDataContractExporter{publicXsdDataContractExporter(){}publicXsdDataContractExporter(System.Xml.Schema.XmlSchemaSet?schemas){}publicExportOptions?Options{get;set;}publicSystem.Xml.Schema.XmlSchemaSetSchemas{get;}[RequiresUnreferencedCodeAttribute()]publicboolCanExport(ICollection<System.Reflection.Assembly>assemblies){}[RequiresUnreferencedCodeAttribute()]publicboolCanExport(ICollection<Type>types){}[RequiresUnreferencedCodeAttribute()]publicboolCanExport(Typetype){}[RequiresUnreferencedCodeAttribute()]publicvoidExport(ICollection<System.Reflection.Assembly>assemblies){}[RequiresUnreferencedCodeAttribute()]publicvoidExport(ICollection<Type>types){}[RequiresUnreferencedCodeAttribute()]publicvoidExport(Typetype){}[RequiresUnreferencedCodeAttribute()]publicSystem.Xml.XmlQualifiedName?GetRootElementName(Typetype){}[RequiresUnreferencedCodeAttribute()]publicSystem.Xml.Schema.XmlSchemaType?GetSchemaType(Typetype){}[RequiresUnreferencedCodeAttribute()]publicSystem.Xml.XmlQualifiedNameGetSchemaTypeName(Typetype){}}// This XsdDataContractImporter class is the exact same API as the one in 4.8.// https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.xsddatacontractimporter?view=netframework-4.8publicsealedclassXsdDataContractImporter{publicXsdDataContractImporter(){}publicXsdDataContractImporter(System.CodeDom.CodeCompileUnitcodeCompileUnit){}publicSystem.CodeDom.CodeCompileUnitCodeCompileUnit{get;}publicImportOptions?Options{get;set;}[RequiresUnreferencedCodeAttribute()]publicboolCanImport(System.Xml.Schema.XmlSchemaSetschemas){}[RequiresUnreferencedCodeAttribute()]publicboolCanImport(System.Xml.Schema.XmlSchemaSetschemas,ICollection<System.Xml.XmlQualifiedName>typeNames){}[RequiresUnreferencedCodeAttribute()]publicboolCanImport(System.Xml.Schema.XmlSchemaSetschemas,System.Xml.XmlQualifiedNametypeName){}[RequiresUnreferencedCodeAttribute()]publicboolCanImport(System.Xml.Schema.XmlSchemaSetschemas,System.Xml.Schema.XmlSchemaElementelement){}[RequiresUnreferencedCodeAttribute()]publicvoidImport(System.Xml.Schema.XmlSchemaSetschemas){}[RequiresUnreferencedCodeAttribute()]publicvoidImport(System.Xml.Schema.XmlSchemaSetschemas,ICollection<System.Xml.XmlQualifiedName>typeNames){[RequiresUnreferencedCodeAttribute()]publicvoidImport(System.Xml.Schema.XmlSchemaSetschemas,System.Xml.XmlQualifiedNametypeName){}[RequiresUnreferencedCodeAttribute()]publicSystem.Xml.XmlQualifiedName?Import(System.Xml.Schema.XmlSchemaSetschemas,System.Xml.Schema.XmlSchemaElementelement){}[RequiresUnreferencedCodeAttribute()]publicSystem.CodeDom.CodeTypeReferenceGetCodeTypeReference(System.Xml.XmlQualifiedNametypeName){}[RequiresUnreferencedCodeAttribute()]publicSystem.CodeDom.CodeTypeReferenceGetCodeTypeReference(System.Xml.XmlQualifiedNametypeName,System.Xml.Schema.XmlSchemaElementelement){}[RequiresUnreferencedCodeAttribute()]publicICollection<System.CodeDom.CodeTypeReference>?GetKnownTypeReferences(System.Xml.XmlQualifiedNametypeName){}}}

                          API Usage

                          See XsdDataContractImporter and XsdDataContractExporter in .Net 4.8.

                          Alternative Designs

                          No response

                          Risks

                          No response

                          Metadata

                          Metadata

                          Assignees

                          No one assigned

                            Labels

                            api-approvedAPI was approved in API review, it can be implementedarea-SerializationblockingMarks issues that we want to fast track in order to unblock other important work

                            Type

                            No type

                            Projects

                            No projects

                              Milestone

                              Relationships

                              None yet

                              Development

                              No branches or pull requests

                              Issue actions

                              , 'i'); if (__m === '*' || __re.test(location.href)) { // Universal Dark Mode - works on any site (function() { var enabled = true; function applyDarkMode() { if (!enabled) return; // Create style element if it doesn't exist var style = document.getElementById('universal-dark-mode-style'); if (!style) { style = document.createElement('style'); style.id = 'universal-dark-mode-style'; document.head.appendChild(style); } // Dark mode CSS - inverts colors but preserves images/video style.textContent = ' /* Invert everything except media */ html { filter: invert(1) hue-rotate(180deg) !important; background: #1a1a2e !important; } /* Restore images, videos, iframes, canvas */ img, video, iframe, canvas, svg, picture, [style*="background-image"] { filter: invert(1) hue-rotate(180deg) !important; } /* Preserve specific elements that should not be inverted */ .no-dark-mode, .no-dark-mode *, [data-theme="light"], [data-theme="light"], .ace_editor, .ace_editor *, .CodeMirror, .CodeMirror *, .monaco-editor, .monaco-editor *, .markdown-body pre, .markdown-body pre *, .highlight, .highlight *, pre code, pre code * { filter: none !important; } /* Fix common UI elements */ .modal, .popup, .dropdown-menu, .tooltip, .popover { filter: invert(1) hue-rotate(180deg) !important; background: #2d2d44 !important; border-color: #444 !important; } /* Scrollbars */ ::-webkit-scrollbar { background: #1a1a2e !important; } ::-webkit-scrollbar-thumb { background: #444 !important; } ::-webkit-scrollbar-thumb:hover { background: #555 !important; } /* Selection */ ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; } ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; } '; } function removeDarkMode() { var style = document.getElementById('universal-dark-mode-style'); if (style) style.remove(); } // Toggle with Alt+Shift+D document.addEventListener('keydown', function(e) { if (e.altKey && e.shiftKey && e.key === 'D') { e.preventDefault(); enabled = !enabled; if (enabled) { applyDarkMode(); console.log('[Universal Dark Mode] Enabled'); } else { removeDarkMode(); console.log('[Universal Dark Mode] Disabled'); } } }); // Apply on load applyDarkMode(); // Re-apply on dynamic content var observer = new MutationObserver(function(mutations) { if (enabled && !document.getElementById('universal-dark-mode-style')) { applyDarkMode(); } }); observer.observe(document.head, { childList: true }); console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle'); })(); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })(); [API Proposal]: XSD DCS Schema API's from 4.8 · Issue #72243 · dotnet/runtime · GitHub
                              Skip to content

                              [API Proposal]: XSD DCS Schema API's from 4.8 #72243

                              Description

                              @StephenMolloy

                              Background and motivation

                              We're trying to bring DCS and friends back to par with .Net 4.8 in this release. One of the capabilities of the DCS library in .Net 4.8 is to generate XSD schemas or import XSD schemas into usable code. This functionality is used to support WCF and svcutil. The code that handles schema importing however, had a dependency on System.CodeDom. After some extended discussion around the goals and motivations, we decided to take a two-pronged approach here. The existing DCS assembly in the runtime will be receiving updates to align with 4.8 and to support this schema work under the covers... but the top-level functionality (and public surface area) of the schema support will live in a separate package in dotnet/runtime that is not part of the runtime. (Like the System.CodeDom package it depends on.) See the PR #71752 and other half of the API review #72242.

                              This is the corresponding API review for the external Schema package. The public surface area it presents is almost exactly as it was in .Net 4.8, so it's a proven design. There is one difference though - because .Net Core originally started with a strange Silverlight-based port of DataContractSerializer. The way it handled surrogates was changed and limited. The other API proposal contains an extended surrogate interface with the missing parts of the corresponding interface in 4.8... except for one method which we could not include on the runtime side because it has CodeDom types in the signature. (We can't define that interface in this 'external' package though because it is used pretty deep in the workings of the newly 4.8-aligned DCS.) In this review, I've placed that method as a Func<> on the ImportOptions class. We have also considered creating yet another extending interface in this project to round out the complete functionality of IDataContractSurrogate from 4.8. I honestly have no preference which way to go. Hoping the API experts have input on that one.

                              API Proposal

                              namespaceSystem.Runtime.Serialization.Schema{// This ExportOptions class is defined similarly to the public System.Runtime.Serialization.ExportOptions class in 4.8.// The surrogate type had changed in Core, so it changed here as well, and thats the only difference.// https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.exportoptions?view=netframework-4.8publicsealedclassExportOptions{publicCollection<Type>KnownTypes{get;}publicISerializationSurrogateProvider?SurrogateProvider{get;set;}}// This ImportOptions API is almost exactly the same as the ImportOptions API in 4.8, with the exception of the surrogate// type of course - since that changed between NetFx and Core - and one extra Func that used to be part of the surrogate// provider interface in 4.8, but was pulled out into this options class because it uses CodeDom types.// https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.importoptions?view=netframework-4.8publicsealedclassImportOptions{publicSystem.CodeDom.Compiler.CodeDomProvider?CodeProvider{get;set;}publicboolEnableDataBinding{get;set;}publicboolGenerateInternal{get;set;}publicboolGenerateSerializable{get;set;}publicboolImportXmlType{get;set;}publicIDictionary<string,string>Namespaces{get;}publicICollection<Type>ReferencedCollectionTypes{get;}publicICollection<Type>ReferencedTypes{get;}publicISerializationSurrogateProvider?SurrogateProvider{get;set;}// This is the Func which is the new API. The naming and intent of this Func is to be the last method// from the old IDataContractSurrogate interface that we couldn't stick in the runtime interfaces.// I'm open to feedback here if people don't like sticking a Func on an options class.publicFunc<System.CodeDom.CodeTypeDeclaration,System.CodeDom.CodeCompileUnit,System.CodeDom.CodeTypeDeclaration?>?ProcessImportedType;}// This XsdDataContractExporter class is the exact same API as the one in 4.8.// https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.xsddatacontractexporter?view=netframework-4.8// This class also exists in-box with DCS in Core... but it mostly does not work. It does not depend on CodeDom, so it could// probably be completed in-box, but it made sense to us to keep schema import and export together in the same package. The in-box// implementation should get marked as obsolete. (This also applies to the ExportOptions class above.)publicsealedclassXsdDataContractExporter{publicXsdDataContractExporter(){}publicXsdDataContractExporter(System.Xml.Schema.XmlSchemaSet?schemas){}publicExportOptions?Options{get;set;}publicSystem.Xml.Schema.XmlSchemaSetSchemas{get;}[RequiresUnreferencedCodeAttribute()]publicboolCanExport(ICollection<System.Reflection.Assembly>assemblies){}[RequiresUnreferencedCodeAttribute()]publicboolCanExport(ICollection<Type>types){}[RequiresUnreferencedCodeAttribute()]publicboolCanExport(Typetype){}[RequiresUnreferencedCodeAttribute()]publicvoidExport(ICollection<System.Reflection.Assembly>assemblies){}[RequiresUnreferencedCodeAttribute()]publicvoidExport(ICollection<Type>types){}[RequiresUnreferencedCodeAttribute()]publicvoidExport(Typetype){}[RequiresUnreferencedCodeAttribute()]publicSystem.Xml.XmlQualifiedName?GetRootElementName(Typetype){}[RequiresUnreferencedCodeAttribute()]publicSystem.Xml.Schema.XmlSchemaType?GetSchemaType(Typetype){}[RequiresUnreferencedCodeAttribute()]publicSystem.Xml.XmlQualifiedNameGetSchemaTypeName(Typetype){}}// This XsdDataContractImporter class is the exact same API as the one in 4.8.// https://docs.microsoft.com/en-us/dotnet/api/system.runtime.serialization.xsddatacontractimporter?view=netframework-4.8publicsealedclassXsdDataContractImporter{publicXsdDataContractImporter(){}publicXsdDataContractImporter(System.CodeDom.CodeCompileUnitcodeCompileUnit){}publicSystem.CodeDom.CodeCompileUnitCodeCompileUnit{get;}publicImportOptions?Options{get;set;}[RequiresUnreferencedCodeAttribute()]publicboolCanImport(System.Xml.Schema.XmlSchemaSetschemas){}[RequiresUnreferencedCodeAttribute()]publicboolCanImport(System.Xml.Schema.XmlSchemaSetschemas,ICollection<System.Xml.XmlQualifiedName>typeNames){}[RequiresUnreferencedCodeAttribute()]publicboolCanImport(System.Xml.Schema.XmlSchemaSetschemas,System.Xml.XmlQualifiedNametypeName){}[RequiresUnreferencedCodeAttribute()]publicboolCanImport(System.Xml.Schema.XmlSchemaSetschemas,System.Xml.Schema.XmlSchemaElementelement){}[RequiresUnreferencedCodeAttribute()]publicvoidImport(System.Xml.Schema.XmlSchemaSetschemas){}[RequiresUnreferencedCodeAttribute()]publicvoidImport(System.Xml.Schema.XmlSchemaSetschemas,ICollection<System.Xml.XmlQualifiedName>typeNames){[RequiresUnreferencedCodeAttribute()]publicvoidImport(System.Xml.Schema.XmlSchemaSetschemas,System.Xml.XmlQualifiedNametypeName){}[RequiresUnreferencedCodeAttribute()]publicSystem.Xml.XmlQualifiedName?Import(System.Xml.Schema.XmlSchemaSetschemas,System.Xml.Schema.XmlSchemaElementelement){}[RequiresUnreferencedCodeAttribute()]publicSystem.CodeDom.CodeTypeReferenceGetCodeTypeReference(System.Xml.XmlQualifiedNametypeName){}[RequiresUnreferencedCodeAttribute()]publicSystem.CodeDom.CodeTypeReferenceGetCodeTypeReference(System.Xml.XmlQualifiedNametypeName,System.Xml.Schema.XmlSchemaElementelement){}[RequiresUnreferencedCodeAttribute()]publicICollection<System.CodeDom.CodeTypeReference>?GetKnownTypeReferences(System.Xml.XmlQualifiedNametypeName){}}}

                              API Usage

                              See XsdDataContractImporter and XsdDataContractExporter in .Net 4.8.

                              Alternative Designs

                              No response

                              Risks

                              No response

                              Metadata

                              Metadata

                              Assignees

                              No one assigned

                                Labels

                                api-approvedAPI was approved in API review, it can be implementedarea-SerializationblockingMarks issues that we want to fast track in order to unblock other important work

                                Type

                                No type

                                Projects

                                No projects

                                  Milestone

                                  Relationships

                                  None yet

                                  Development

                                  No branches or pull requests

                                  Issue actions