Bah, I have no more time to waste, have clients to work with today.

Want to sign your application, use GuardIT. It is a method that will allow for distribution of client apps - the kind I described earlier. It will act more-or-less like a certificate authority (CA) where you have a centralized server and it says it can/cannot run. Think of it as an extended license server. GuardIT is a library for .NET.

If you happen to use Silverlight, you can use their internal DRM to not only protect the media, but also for the app itself. It's the second part that's confusing. The use of audio/video is covered, but to deploy it to where the app is limited/restricted is based on licensing and you have to write a routine. If you have a MSDN account, you can find some Silverlight 4 routines for such a thing. I piggy-backed the existing app discussions to figure this and offline DRM out.

If you're talking about distributing an app has to obtain DRM keys, then you'd something like using the WMStubDRM.lib, which is a direct link to the Windows Media player DRM. This protects only the content, not your app.

If you're talking about Zune or XBOX apps, I personally don't know enough, but have resources. That's a true weakness of my skillset - at least I'm honest.

And there are other methods to signing, restricting, and protecting your app - some tap into the Windows Vista/Windows 7 DRM layer, some use external sources - like Verisign of SealedMedia among other routines.

It truly matters on what you want to protect and what you're after. You've specified as of yet, none of the above, I can't read your flippant mind, so above will start you off properly.

Sadly enough, I can't do it all for you. And no, dear child... it's not about about what I will and will not tell you; you just have not provided enough information for anybody to answer any of your vague questions.

Troll away. I was trying to answer; I'll do it no more.