Sure, we have Content Deployment and STSADM export etc., but the lowest level of granularity is a web, and if you don't want to overwrite the whole thing neither option can be used.The only other option is to write code which uses the Content Migration API.
Therefore, if you are deploying Click Once applications, any authentication scenario besides Windows authentication is unsupported.
by Microsoft Even though Microsoft says that Click Once doesn't support ASP. Understanding How a Click Once Application is Downloaded When access the Click Once deployment manifest (.application) file from IE, files are downloaded in following sequence: As the Click Once engine doesn't support cookies, without a workaround step 2 will fail.
Regular readers might have spotted I've been slightly quieter than usual over the past few weeks - actually I've not been slacking, but working on a tool which you might find useful from time to time.
As I've discussed in numerous posts, deployment of Share Point artifacts is something that's perhaps more complex than it should be, and the standard tools provided don't always simplify this picture.
Since pictures are often more useful than words, let's look at using the tool.