-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WindowsCommunityToolkit Can not be installed on WinUI 3 version 1.0 Experimental #4171
Comments
Hello ghost1372, thank you for opening an issue with us! I have automatically added a "needs triage" label to help get things started. Our team will analyze and investigate the issue, and escalate it to the relevant team if possible. Other community members may also look into the issue and provide feedback 🙌 |
Thanks for the report @ghost1372. This is a known issue, we currently only support version 0.8 as per the WinUI release notes. We're also waiting for WinUI 3 to adopt the WinUI 2.6 changes as we've updated to WinUI 2.6 in our main branch for our upcoming 7.1 release. When they ship a release for 1.0 that supports the new styles, we can ship an new update. |
This is also blocked by: |
@michael-hawker This is currently blocking existing WinUI applications to try the new alpha. What I need is a package with 7.0 feature (thus depending on features of WinUI/Reuion0.8) and recompiled for WinUI/WindowsAppSDK1.0 . It's OK to be alpha and sit on private feed. Cloning and forking the community toolkit is just too big work for the projects. If we can migrate to the new package earlier, we can find potential issues sooner. WCTK is a very important part of WinUI ecosystem and shouldn't block migration. |
@azchohfi The Bootstrap.dll issue seems to of been resolved in the latest WindowsAppSDK preview release. After that roadblock was resolved I then hit the next one in that the toolkit doesn't work, hence what led me to this issue... |
Thanks everyone for letting us know, we're aware that this has been a paint-point and are working towards, if anything, an interim solution. As suggested this just maybe a more 'preview' type drop that supports the latest 1.0-preview but may be a bit wonky from still having the mixed styles from 2.5 vs. 2.6, at least until 1.0 ships. @azchohfi has the AnyCPU issue microsoft/WindowsAppSDK#1217 been resolved in the latest 1.0-preview? |
Hi @michael-hawker |
@ghost1372 we're still waiting on our dependencies to update to 1.0-preview1/2; once that is done we can move forward. |
@michael-hawker Can you give us a timeline for when this will be working, really need WCT on WinUI 3. Is there an issue to subscribe to or will you update this one? |
@tinmac we'll post a discussion when we release and close this issue. Right now we're waiting for Preview 3 as WASDK Preview 1 and 2 have a critical bug, see microsoft/WindowsAppSDK#1599 |
@michael-hawker but here
Am I misunderstood? |
@ghost1372 they have the message on NuGet here: https://www.nuget.org/packages/Microsoft.WindowsAppSDK/1.0.0-preview2 |
Thanks @ghost1372 for closing the issue, I knew I'd forget to post in one place. Link to the new release: https://github.com/CommunityToolkit/WindowsCommunityToolkit/releases/tag/winui-7.1.1-preview3 |
Describe the bug
WindowsCommunityToolkit can not be installed on WindowsAppSDK 1.0-Experimental version
it seems that This is due to the renaming of windowsAppSDK nuget packages
If possible, please publish a new version compatible with this version.
microsoft/WindowsAppSDK#1209
Steps to Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: