Explore tweets tagged as #cppwinrt
cppwinrt no WRL COM server, with full automatic shutdown + varaidic factory registration. Worthy to add to wil?
0
0
1
https://t.co/TwZ87hmuOi So I made a sample for pure cppwinrt OOP COM server without WRL (let's just call it cppwinrt-only from now on...). Time to file an issue in WIL...
0
1
1
So, cppwinrt out-of-proc COM server without WRL, with automatic shutdown is here. This is surprisingly simple. Apart from an if-else to check clsid and calling corresponding winrt::make<> in class factory, did I miss anything? @alexsklar @DHowett
1
0
0
1 million LOC. that's the size of the generated cppwinrt headers, which are only wrappers around the Window Runtime ABI.
0
0
0
https://t.co/EglodQv8lN PR for cppwinrt-only out of proc COM server is up
0
0
1
https://t.co/EglodQv8lN My PR for cppwinrt-only COM server has been merged. Real work starts from here. Goal: advocate updating samples from WRL to WIL. And hopefully make WASDK folks aware of this addition
0
0
2
With @alexsklar adding cppwinrt property helper in WIL in this PR https://t.co/ez55OlfaXe, the tool could automatically such helpers and there should be no attributes needed to specify getters/setters
1
0
2
Ok now that someone had worked on FileLocksmith windows 11 menu, maybe it's time to write a working sample that uses cppwinrt instead of WRL...
0
0
3
@a_donglee My lib needs to be able to activate all cswinrt dll's xaml metadata provider so that they can be found by my dll loader (a preview) app. It is working flawlessly for cppwinrt dll by default for now. I will have to hard code https://t.co/c7vlhU4SJK.dll by default for cswinrt
2
0
0
I just want to port stuff I wrote in the cppwinrt server demo to WIL and here I'm reading WIL'd docs and finding how TF the run init.cmd😅
0
0
1
So it turns out cppwinrt doesn't provide much value over WRT in implementing classic COM as it doesn't generate a default class factory (unlike WinRT, which cppwinrt would generate a default activation factory in module.g.cpp)
1
0
0
https://t.co/Gc0f8TkZOg ここのdirectx-vs-templatesの*uwp_cppwinrtのコード、特にエントリポイントの処理が謎コードだらけだったけど公式ドキュメントちゃんとあるのか。あるだけで何言ってるのかさっぱりわからんけど https://t.co/13znvdIM3E
0
0
3
Out of all of the quotes, I think this is the most important. Wish the larger windows UI/UX team(s) (shell, inbox apps, etc) adopt this culture...I know the low level folks certainly embrace this culture (e.g. cppwinrt).
Culture change is how you make the impact long lasting.
0
0
2
Things I didn't expect to see: - https://t.co/GA12RugJqA - https://t.co/RIEBFIuuPO -
0
0
0
> Me thinking I'm about to do some slick stuff with header units to improve build perf > Me realizing all the errors I see, are because cppwinrt doesn't support modules yet, and win sdk only works when targeting above 19041
1
0
4
