Questions about clickOnce

[Irfan]

hi,

I have couple of questions about clickonce again,

I am publishing a Winform appplication using ClickOnce. In the 'Publishing
Location' text box I input the directory name
(C:\CLICKONCE\Test2\). In the 'Installation URL' what shall i input. Why do
i need to input a URL when it is
simple Winform Application.


Question2:
When I publish a new version, The client should be prompted about the new
version and it should run that instead of old one.
It doesnt do it in my case, even though 'Application Should check for
updates' is ON.


Thanks in Advance

irfan

 

[Rory Becker]

I am publishing a Winform appplication using ClickOnce. In the

'Publishing
Location' text box I input the directory name
(C:\CLICKONCE\Test2\). In the 'Installation URL' what shall i input.
Why do
i need to input a URL when it is
simple Winform Application.

Click once is all about deployment through a web interface. If you don't
specify a web location to deploy to then it doesn't work.

Note that a local web server is also a valid "web location"

Question2:
When I publish a new version, The client should be prompted about the
new
version and it should run that instead of old one.
It doesnt do it in my case, even though 'Application Should check for
updates' is ON.

If you're not deploying to a web location then you're likely directly launching
the exe.
This is not the way click once is designed to work.

Once working properly, the user visit's your web page once and clicks a link
which triggers the download and installation of the program
This causes a special shortcut to be added to the startmenu which triggers
special behavior which checks each time loaded to make sure the latest version
is present before loading.

This is a very rough outline of the process, but as you can see, the web
aspect is important to the process.

 

[Rad [Visual C# MVP]]

Click once is all about deployment through a web interface. If you don't
specify a web location to deploy to then it doesn't work.

Note that a local web server is also a valid "web location"


If you're not deploying to a web location then you're likely directly launching
the exe.
This is not the way click once is designed to work.

Once working properly, the user visit's your web page once and clicks a link
which triggers the download and installation of the program
This causes a special shortcut to be added to the startmenu which triggers
special behavior which checks each time loaded to make sure the latest version
is present before loading.

This is a very rough outline of the process, but as you can see, the web
aspect is important to the process.

Not 100% true -- you can also deploy click once from a folder share. It
does not have to be a web location

 

[Irfan]

thanks for the replies, though i am still struggling as i am not able to
achieve the update aspect:


I created a project, My Publish Location is C://ClickOnceTest and my
InstallationLocation is http://localhost/.
Everything works fine as long as I test it on my computer. But I am not able
to inderstand what files do i need
to send to the client to install it to their computer, assuming their is no
Internet Connection at his end.

Irfan

 

[Rory Becker]

thanks for the replies, though i am still struggling as i am not able

to achieve the update aspect:

I created a project, My Publish Location is C://ClickOnceTest and my
InstallationLocation is http://localhost/.
Everything works fine as long as I test it on my computer. But I am
not able
to inderstand what files do i need
to send to the client to install it to their computer, assuming their
is no
Internet Connection at his end.

Sorry Infran.. whilst I was a little incomplete in my answer before, I think
you'll find that click once is not a replacement for all installer technology
and is intended to be a http / UNC deployment tech.

This basically means that whomever has your program needs to have a connection
to the location that you publich the app to.

This means Internet, Intranet or LAN/WAN

It sounds like what you need is a CD installation.

 

[Rory Becker]

This basically means that whomever has your program needs to have a

connection to the location that you publich the app to.

I should say here that this connection does not always have to be available.
It is mearely the means by which said user would perform their update.

However (I think) you can insist that the program check every time.

 

[Irfan]

Many thanks Rory for the info,

Once last thing, How can i add additional files during the deployment, ie,
Excel Database

irfan

 

[RobinS]

They have to be imbedded in VisualStudio in order to include them in the
deployment. Check out Brian Noyes' book about ClickOnce deployment; he
has an entire chapter about this very thing. Too long to tell you how to do
it in a posting.

Robin S.
---------------------------

Many thanks Rory for the info,

Once last thing, How can i add additional files during the deployment,
ie, Excel Database

irfan

 

[Irfan]

thanks for the right direction

They have to be imbedded in VisualStudio in order to include them in the
deployment. Check out Brian Noyes' book about ClickOnce deployment; he
has an entire chapter about this very thing. Too long to tell you how to
do it in a posting.

Robin S.
---------------------------