RudolfMeier-2283 avatar image
0 Votes"
RudolfMeier-2283 asked XiaopoYang-MSFT edited

Adding an identity to a com dll?

today there seems to be a need to have an "identity", when you call some api functions... ok then... and the documentation tells you what to do to achieve this (even for win32 applications written e.g. in C/C++) ... that's all fine... but what about com dlls? do they (or all dlls) also have a manifest? ... do they also have an appx manifest? (I learned, that there are 2 different ones... one is the package manifest that you have to register and one the manifest inside the exe... so I guess there must also be one in the dll?) ... and, how do they look like? how do they work? when does Windows look at those manifests? when loading a com server? ... now... here's the next thing I don't understand... how would this work with the registration of the com classes? ... the examples always tell me, that the registration can be done insise this manifest... but, when it's ONLY a com dll (e.g. shell extension) and NOTHING else... how would Windows at runtime learn from this com dll??

does there exist a good documentation on that? or is it just like always? "help yourself and everyone is using .net anyway and there everything works by magic, when you sell your app via the Microsoft store, which is the reason why we don't explain it? ... and shell namespace extensions... those are no topic anymore for a discussion"

I hate my job...

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

0 Answers