You cannot load Microsoft Visual Studio 2012 projects that depend on the graphics assets (mesh, image, and shader) content pipeline by using Microsoft Visual Studio 2013 Preview. In this situation, these projects are marked as "load failed" in Solution Explorer.
Additionally, you receive an error message that resembles the following message in the output window:
<Driver name>:\code\Visual Studio 3D Starter Kit (Windows Store only)\C++\StarterKit\StarterKit.vcxproj : error : Unable to read the project file "StarterKit.vcxproj".
<Driver name>:\code\Visual Studio 3D Starter Kit (Windows Store only)\C++\StarterKit\StarterKit.vcxproj(72,5): The imported project "C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\Extensions\Microsoft\VsGraphics\MeshContentTask.props" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.
This issue occurs because Visual Studio 2013 Preview does not support the mesh, image, and shader content pipelines that are created in Visual Studio 2012 projects.
To work around this issue, follow these steps:
- In a text editor, open the project's .vcxproj files.
- Remove the following sections:
- Save the .vcxproj files.
- Reopen the project in Visual Studio, right-click the project in Solution Explorer, and then click Build Customizations.
- Add the following items by clicking Find Existing:
Note In these paths, %ProgramFiles% represents the Visual Studio installation directory. For x64-based computers, the default installation directory is C:\Program Files (x86). For x86-based computers, the default installation directory is C:\Program Files.
- %ProgramFiles%\Microsoft Visual Studio 12.0\Common7\IDE\Extensions\Microsoft\VsGraphics\MeshContentTask.props
- %ProgramFiles%\Microsoft Visual Studio 12.0\Common7\IDE\Extensions\Microsoft\VsGraphics\ImageContentTask.props
- %ProgramFiles%\Microsoft Visual Studio 12.0\Common7\IDE\Extensions\Microsoft\VsGraphics\ShaderGraphContentTask.props
- Select the check box for all three added items, and then click OK.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.