You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 25, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Feb 25, 2026. It is now read-only.
@Dylan-H I tried and it seems that the only package you can use is Toolkit.Notifications. That's mainly because the other packages have a managed dependency (like Newtonsoft).
If there was one package that can be used in C++/CX, what do you think it should be ? (controls, helpers, services)
You could perhaps pull the source code and swap the behaviours reference for the unmanaged/c++ version wherever it's used, Win2D should be fine as it supports CX usage OoTB, and that might let you use Controls.
@Odonno We could have both as output as for dotnet projects, managed would perform better..Native / WinRT would mean crossing into Runtime with every call. For dependencies dont think we can toggle managed / native usage
It will be on per project basis. Initially we did not pick winrt but UWp as base because the vast majority of users we are targeting are using C#
But if we can migrate a project to be winrt compatible while keeping backward compatibility, I'm ok
ghost locked as resolved and limited conversation to collaborators on Nov 26, 2019
Activity
Odonno commentedon Dec 28, 2016
@Dylan-H I tried and it seems that the only package you can use is Toolkit.Notifications. That's mainly because the other packages have a managed dependency (like Newtonsoft).
If there was one package that can be used in C++/CX, what do you think it should be ? (controls, helpers, services)
Dylan-H commentedon Dec 28, 2016
@Odonno Thanks, I get it.
I want to use constrols
hermitdave commentedon Dec 28, 2016
Animations lib used by Controls requires Behaviours and Win2D. The base toolkit lib requires Newtonsoft.Json..
JohnnyWestlake commentedon Dec 29, 2016
You could perhaps pull the source code and swap the behaviours reference for the unmanaged/c++ version wherever it's used, Win2D should be fine as it supports CX usage OoTB, and that might let you use Controls.
Dylan-H commentedon Dec 29, 2016
@JohnnyWestlake Thanks
I'm trying to transplant a control with c++/cx
But it difficult for me
hermitdave commentedon Dec 29, 2016
I think we should move away from Json dependency and use one from WinRT API
hermitdave commentedon Dec 29, 2016
Also behaviours sdk can be swapped for native version. Then i doubt see why this can't be used c++
Odonno commentedon Dec 29, 2016
@hermitdave So, like Behaviours package, should we handle both
ManagedandNativeprojects at the same time ? Or could we have a single project ?hermitdave commentedon Dec 29, 2016
@Odonno We could have both as output as for dotnet projects, managed would perform better..Native / WinRT would mean crossing into Runtime with every call. For dependencies dont think we can toggle managed / native usage
xied75 commentedon Feb 6, 2017
@deltakosh you didn't give a reason as why this is closed.
deltakosh commentedon Feb 7, 2017
It will be on per project basis. Initially we did not pick winrt but UWp as base because the vast majority of users we are targeting are using C#
But if we can migrate a project to be winrt compatible while keeping backward compatibility, I'm ok