Yes, there are even multiple ways to accomplish this. Staging rollouts is useful for testing (ex. only deploying a new application updates to a beta user group) & for scalability (ex. rolling out an update to a 1000 users a day).

The simplest option is to simply create separate deployments (i.e. different deployment manifests) for each set of users. Ex. Beta users use the beta deployment, everyone else uses the main deployment.

A second option, is to use the System.Deployment APIs. The deployment APIs allows an application to control when updates happen. You could build your own custom logic for determining when an application should update & use the APIs to instruct “ClickOnce” to do an update at the appropriate time.

A third option is to have server side logic that dynamically decides which version of an application a user shoudl have & returns an appropriate deployment manifest for that user user.