I am creating a Setup Project in Visual Studio 2008 Standard Edition. I am having issues with the Setup Projects inability to conveniently update the software just as the Click Once Publishing does. I am deploying the software using Active Directory and the installation of the actual project goes smoothly.

I cannot express how frustrated I am that this seemingly parallel feature lacks, or forcibly removes, the ability for the application to update itself. If I create and publish software using Click Once Publishing everything is great. But if I wrap that very same application into a Setup Project then all of the sudden it is unable to update? The created Windows Installer Package should be nothing but a shell around the published product! I have been working with Scalable WinInstall to create a Windows Installer Package that operates with the update functionality. This would be an entirely adequate solution, but the Click Once Publishing automatically stores the executable files in the user's Documents and Settings\Local Settings\apps folder so I am forced to reconfigure the registry errors. This is roughly equivalent to holding a tape deck up to a tape recorder to record audio while at the same time playing the drums to add the beat to a band's recording, who simply forgot to play the drums in the first freaking place.

And I am sorry to be so accusatory and sharp, but can anyone explain why any of this is excusable? I simply should not need to use a third party application to utilize functionality that is already built in to Visual Studio. Or, what would be greatly appreciated, let me know how I might deploy this application using Active Directory and get updates just as I do with the Click Once Publishing.

I honestly hope this is user error and not as frustrating as I see it. It appears that I can either trade off Active Directory or Automatic Updates. Or force my one-man development team, me, to write updatable applications which I haven't the first clue how to do.

I thought you need explanation from Microsoft. Do you need speculations from another forum visitor? Or just need help in updating?

---

MSMVP VC++

ClickOnce is designed to be used in any environment, so it does not require administrative privileges on the machine in order to be installed. Plus, it is a per-user installation. For these reasons, and to keep the user from messing around with the files (I assume), it is deployed in folders with obfuscated names under the user's profile. What is your problem with that?

RobinS.
GoldMail.com

---

Ts'i mahnu uterna ot twan ot geifur hingts uto.

This is apeer to peer community. To provide feedback to Microsoft, visit http://connect.microsoft.com/visualstudio.

---

MSMVP VC++

Thank you, Sheng Jiang. I don't really feel that would be productive. I am looking for assistance with the issue above.

I thought you need explanation from Microsoft. Do you need speculations from another forum visitor? Or just need help in updating?

---

MSMVP VC++

Any help is appreciated! After reviewing the documentation on the Updater Application Block, it may be just what I needed. Excellent!

I am still curious about why the Click Once Publishing installs the application files in [Windows Volume]\Documents and Settings\[Current User]\Local Settings\Apps. More specifically, is there any simple way to have this application behave in a more traditional manner? For example, can I force the installation into [Programs Folder]\?

Thanks again,
Nathan G.

ClickOnce is designed to be launched from web sites so it has a lot of secuirty complication.

---

MSMVP VC++

ClickOnce is designed to be used in any environment, so it does not require administrative privileges on the machine in order to be installed. Plus, it is a per-user installation. For these reasons, and to keep the user from messing around with the files (I assume), it is deployed in folders with obfuscated names under the user's profile. What is your problem with that?

RobinS.
GoldMail.com

---

Ts'i mahnu uterna ot twan ot geifur hingts uto.