how to use it with DependencyInjection
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 9.6k
- Forks
- 1k
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
I am very interested in this WPF framework and hope to incorporate it into my project. However, my project has already taken shape, and I am using the Microsoft.Extensions.DependencyInjection DI framework, and have rewritten the constructor of MainWindow. In this case, when I tried the methods described in the Getting Started documentation, the framework did not take effect, and I did not find any relevant documentation that could solve my problem. What should I do?
To Reproduce
I am very interested in this WPF framework and hope to incorporate it into my project. However, my project has already taken shape, and I am using the Microsoft.Extensions.DependencyInjection DI framework, and have rewritten the constructor of MainWindow. In this case, when I tried the methods described in the Getting Started documentation, the framework did not take effect, and I did not find any relevant documentation that could solve my problem. What should I do?
Expected behavior
I can't find any doc describe how to use with Microsoft.Extensions.DependencyInjection
Screenshots
No response
OS version
win11
.NET version
8.0
WPF-UI NuGet version
4.0.3
Additional context
No response
Contributor guide
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 Getting Started documentation and the MainWindow constructor used with Microsoft.Extensions.DependencyInjection. Determine how WPF-UI should be integrated in that setup; done means the documentation explains the required .NET 8/WPF integration clearly enough for a reader to apply it without guesswork.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100