Could not find schema warning

[alekdavis]

I am using Visual Studio 2022 Professional (latest version) and I just upgraded SHFB to the latest version. After adding a conceptual content topic file (using the standard Add menu and selecting the Conceptual topic from the list), I get the "Could not find schema information for" the element/attribute warnings:

When installing SHFB, I went over all options to set up VS extension, install schemas, etc., and I did not see any errors or warnings, but just in case I reinstalled it and it all looks good:

So, not sure, what I may be missing.

[EWSoftware]

If Visual Studio is using the schemas, you should see them in the properties window for the file in the Schemas property. If you click the "..." button to the right of the property value it will list all schemas.

[alekdavis]

@EWSoftware I see a few dozen schemas in the Properties window, but I'm not sure how this would help. The warning comes from the root element:

<topic id="95884982-ff04-4b6e-9214-7622491f4679" revisionNumber="1">

What schema do the topic, id, and revisionNumber belong to? Is there a way to fix it?

[EWSoftware]

The schemas are installed as part of the extension. You should see entries with a path pointing to C:\Program Files\Microsoft Visual Studio\2022\Community\xml\schemas\SandcastleMAML or something like it. If you open the noted dialog box and click the Use column to sort by those in use, the Sandcastle ones should be listed first:

As noted, they are part of the package so I don't know why they wouldn't be there for you.

[alekdavis]

They are there. So, why are the warning there?

[EWSoftware]

I figured it out. They're not warnings or errors just informational messages. The topic element and the ID and revisionNumber attributes aren't part of the formal MAML schema so that's why they show up.

[alekdavis]

Ah, I see. Thanks for the info. So should these be defined is a custom namespace to make the error list clean?

[EWSoftware]

I could probably add them to the schemas though I think this is the first time anyone's ever brought it up as an issue.