locked
Are the four messages about the vsixmanifest when building a VS 2015 package normal? RRS feed

  • Question

  • I have noticed that the generated vsixmanifest file gets four build messages (in the error list window) when building the VSIX project, and wanted to know if these are 'normal' and can be ignored, or if there is something that can be done to avoid them.  The messages refer to 3 lines of the vsixmanifest file, as follows:

    <Dependency Id="Microsoft.Framework.NDP" DisplayName="Microsoft .NET Framework" d:Source="Manual" Version="[4.5,)" />

    gets the build message:

    • Could not find schema information for the attribute 'http://schemas.microsoft.com/developer/vsx-schema-design/2011:Source'.
    <Dependency Id="Microsoft.VisualStudio.MPF.14.0" DisplayName="Visual Studio MPF 14.0" d:Source="Installed" Version="[14.0]" />

    gets the build message:

    • Could not find schema information for the attribute 'http://schemas.microsoft.com/developer/vsx-schema-design/2011:Source'.

    and

    <Asset Type="Microsoft.VisualStudio.VsPackage" d:Source="Project" d:ProjectName="%CurrentProject%" Path="|%CurrentProject%;PkgdefProjectOutputGroup|" />

    gets the two build messages:

    • Could not find schema information for the attribute 'http://schemas.microsoft.com/developer/vsx-schema-design/2011:Source'.
    • Could not find schema information for the attribute 'http://schemas.microsoft.com/developer/vsx-schema-design/2011:ProjectName'.

    I used the VSIX Project template to generate the project.

    Thanks.


    • Edited by kengr Monday, May 16, 2016 11:10 PM
    Monday, May 16, 2016 11:10 PM

Answers

  • Hi kengr,

    >>"if these are 'normal' and can be ignored"

    It is not normal. It seems Visual Studio could not load VSIX Extension Schema or did not load VSIX Extension Schema correctly. The issue is related to Visual Studio itself. Try to reset settings for Visual Studio.
    https://msdn.microsoft.com/en-us/library/ms241273.aspx

    Best Regards,
    Li Wang


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    • Marked as answer by kengr Wednesday, May 18, 2016 3:28 PM
    Wednesday, May 18, 2016 9:43 AM

All replies

  • Hi kengr,

    Visual Studio 2015 use VSIX Extension Schema 2.0. Please doule check the version number.

    <PackageManifest Version="2.0.0" xmlns="http://schemas.microsoft.com/developer/vsx-schema/2011" xmlns:d="http://schemas.microsoft.com/developer/vsx-schema-design/2011">
    Best Regards,
    Li Wang

    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Tuesday, May 17, 2016 8:34 AM
  • Yes, the PackageManifest version is indeed 2.0.0.  Again, this vsixmanifest file was generated by the VSIX Package template included in the Visual Studio 2015 SDK.

    So, the version number does not appear to be the cause of the issue.

    Tuesday, May 17, 2016 2:10 PM
  • Hi kengr,

    >>"if these are 'normal' and can be ignored"

    It is not normal. It seems Visual Studio could not load VSIX Extension Schema or did not load VSIX Extension Schema correctly. The issue is related to Visual Studio itself. Try to reset settings for Visual Studio.
    https://msdn.microsoft.com/en-us/library/ms241273.aspx

    Best Regards,
    Li Wang


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    • Marked as answer by kengr Wednesday, May 18, 2016 3:28 PM
    Wednesday, May 18, 2016 9:43 AM
  • Running

    devenv.exe /ResetSettings

    resolved the issue.  The four messages are gone, and the build is completely clean now.

    Interestingly, I discovered that every time I perform a reset of the experimental instance of VS 2015, I start getting these messages again, and have to re-do this /ResetSettings on the non-experimental instance.


    • Edited by kengr Sunday, May 22, 2016 11:17 PM Added note on the effect of resetting the experimental instance
    Wednesday, May 18, 2016 3:28 PM