In this video Pat Tormey demonstrates the use of ClickOnce for application deployment.
Author: Pat Tormey
Very Useful. Thanks
Hi Pat,
The video was really informative. I could publish my applications without any trouble but I am having a bit of issue developing my own custom pre requisites for Click once deployment.
I need to create a package that contains a msi file which I have created using the .NET frame work configuration tool. What I am trying to achieve is to have this msi file installed as prerequisite so that my .NETapplication will have sufficient privilleges to run on the client machine.
I am using Bootstrapper manifest generator for creating my custom package .The build output was successful with 0 warning and I could see the output folder on C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages.
However it is not appearing in the prerequisites window in my visual studio IDE.
Am I missing some cases. I am using Microsoft Visual C# 2008 express edition.
Any help would be really appreciated.
Generall Speaking the ClickOnce tool works perfectly for what it does And doesn't do much beyond that with out some digging around.
So...I've also provided a SetUp Video showing how to use the SetUp project.
Check it out..
And Good luck
Pat
New Hampshire USA
Hi Pat
Click Once works perfectly thanks!
But can you please poste the Link for the Setup Video. I didn't find it.
Thanks
Jakob
hello,
it s a good video but i have a trouble in my case, when i publish my application there is no probléme i can install it in my customers but the probléme when i make any modification , when the application is start normally he is gona to chek update in my case nothing happin the application continue to run with the old version i dont inderstand where is the trouble i chek everything but i got always the same probléme can you help thanks
Hello Issamglad,
The number one problem with new version not being deployed is that the developer forget to set the PUBLISH version to a higher number
Thi sisn't eh code or file version it's strictly the version that the ClickOnce component sees.
Good luck