Update docs #9522
Update docs #9522
Conversation
Updates docs to include more information on project system selectors.
Replace IVsProjectSystemSelector (incorrect) with IVsProjectSelector (correct).
There was a problem hiding this comment.
Might be helpful to add some information about XML solutions (.slnx files) as they don't explicitly list a project type GUID. The example here would just be:
<Solution>
<Project Path="Library3\Library3.csproj" />
</Solution>My assumption is that in such a case, the decision is based on file extension and delegation to IVSProjectSelector.
| EndProject | ||
| ``` | ||
|
|
||
| Here the "Library3.csproj" project should be opened with the project system designated by the "FAE04EC0-301F-11D3-BF4B-00C04F79EFBC" GUID. |
There was a problem hiding this comment.
Users reading this might be interested in other project type GUIDs too. We don't have an official doc that lists these that I know of, but this source file does a decent job of enumerating the ones that are most likely interesting to the reader:
| EndProject | ||
| ``` | ||
|
|
||
| Here the "Library3.csproj" project should be opened with the project system designated by the "FAE04EC0-301F-11D3-BF4B-00C04F79EFBC" GUID. |
There was a problem hiding this comment.
is the other GUID relevant? ADFEAAF5-225C-4E13-8B65-77057AAC44B8
|
|
||
| ## Problem | ||
|
|
||
| There may be situations where more than one project system is capable of loading project files with a particular extension, or where the choice of project system needs to be dynamically determined. In this case the solution file itself does not contain enough information for the correct project system to be determined. |
There was a problem hiding this comment.
nit: In this case, the solution file...
Co-authored-by: Drew Noakes <[email protected]>
Updates docs to include more information on project system selectors.
Microsoft Reviewers: Open in CodeFlow