microsoft / microsoft/Windows-classic-samples
Opening Explorer Data Provider in Visual Studio 2022
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 5.7k
- Forks
- 3.3k
- PR merge metrics
- No merged PRs in 30d
Description
Hi
I am trying to open the ExplorerDataProvider project in Visual Studio 2022. When I open the .sln file in VS 2022, I get a pop-up asking me if I want to auto-upgrade the project, which I then do.
The project the launches with incompatible in parenthese next to the project name, and "The application is not installed" below it.
I then try to reload the project, which shows me the One-Way upgrade dialog again. Then I let the de continue, but after a few second I get a error message saying "The operation could not be completed" without any other information. The project then has "load failed" in parenthesis, with "The project requires user input. Reload the project for more information." below it.
Reloading the project just repeats the process without any more information becoming available.
Is there anything else I need to do to get the project to load in VS 2022? Or should I rather try to load the project in an older version of VS?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the ExplorerDataProvider project and its .sln file in Visual Studio 2022, reproducing the auto-upgrade and reload sequence described in the issue. Check whether the project can load in an older Visual Studio version; done would mean documenting the required version or steps that allow the project to load without the incompatible, load-failed, or application-not-installed messages.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100