renojim wrote:nowhereman wrote:It's a pain because it means each channel that I want to have its own screen saver will need its own unique developer ID. That means every time I want to update a given channel, I have to go through the process of re-signing my box with the correct ID for that channel. It's also problematic because the box's registry seems to key off of the developer ID as well, so if I change the developer ID associated with a given channel, it will lose access to any data it has saved in the registry.
Maybe I'm misunderstanding what you're saying, but "re-signing" the box? It's just the app that has to be packaged with a different password from another execution of genkey (maybe that's what you were saying). It would be nice to take this discussion to the Developer's Forum because I agree that there's some improvements that could be made in this area.
The messy part is developing several different channels, each with its own key, in parallel. You can't just generate a new key every time you package a channel because you would run into the registry issue I mentioned. You have to be sure that the appropriate key stays associated with each channel and that each channel always gets packaged with the appropriate key. And if you have a large collection of channels all built with the same key, suddenly having to change them all to have their own unique key because of these screen saver conflicts is going to cause headaches for end users when their channels forget any data they have stored in the registry. Re-signing the box with an existing key involves uploading an existing package known to be signed with that key to the box, then entering the password associated with that key. It's not overly complicated, but it's tedious.