@Matthijs: If I'm understanding this correctly, the 3rd party developer builds the Windows Phone application and packages it in a XAP (not sure if it is signed or not signed at this point by the 3rd party developer). The XAP is then given to the enterprise where they can sign it and publish it in their private store.
What about enterprise customers who do not run a private store (i.e. small customers)? Can the 3rd party developer run a private store? This must be where you mention "give them access by an account or token". It seems like the customer's machines could only be enrolled in one store and in the case of a smaller customer it wouldn't make sense to have them NOT be enrolled in Microsoft's public store. This area is foggy.
What is the enterprise story for when a 3rd party developer produces a solution for an enterprise that includes a Windows Phone component? How does the 3rd party package and distribute the Windows Phone application such that it is private to the 3rd party and the 3rd party customers?
I needed to know the scope of what Microsoft Security Essentials scans when performing a Quick scan. I pulled out Process Monitor (elevated) and filtered on MsMpEng.exe to take a looksie. While Process Monitor showed lots of lovely stuff, I wondered did it show it all? Who has the lowest hook, Process Monitor or MSE? Who is hiding from who?
Yes and yes, Tim. All businesses change from state A to state B by way of a transition that weighs the downside risk against the upside gains. Your dimmer analogy is right on.
The stress these days on the development supply side is the loss of market supply at scale for on-premise. To parallel the electricity analogy, the cost of backup generators today is way more expensive than if everyone had a generator for primary power. The same holds true for the physical on-premise IT parts.
Developers have to follow the dimmer and move their finely tuned code base from state A to state B just as carefully (change, retune, change, retune, change, retune,...).