468,780 Members | 2,318 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 468,780 developers. It's quick & easy.

Checking for new versions in a setup project

HIK
Click once can be set up to pole the setup url if there is a newer
version or not. I have a project which can only be deployed using a
setup project. How can I create the same feature in my setup project,
so the client will automatically check if there is a newer version or not?

haim
Mar 8 '06 #1
7 3968
hai,
After you generate a setup project using the setup project wizard, look
under deployment project properties.
There is an option for "DetectNewerInstalledVersion". Set it to true
for your requirements.
Also set "RemovePreviousVersions" as per your requirement.

Hope this helps.

Mar 8 '06 #2
HIK
Thanks Mike. that was very easy.

Haim

Mike wrote:
hai,
After you generate a setup project using the setup project wizard, look
under deployment project properties.
There is an option for "DetectNewerInstalledVersion". Set it to true
for your requirements.
Also set "RemovePreviousVersions" as per your requirement.

Hope this helps.

Mar 8 '06 #3
HIK
Mike,

That didn't help. The "DetectNewerInstalledVersion" prevents the msi
from overwriting a newer version. But when the application is launched,
it does not check if there is a newer built installed.

Haim
Mike wrote:
hai,
After you generate a setup project using the setup project wizard, look
under deployment project properties.
There is an option for "DetectNewerInstalledVersion". Set it to true
for your requirements.
Also set "RemovePreviousVersions" as per your requirement.

Hope this helps.

Mar 8 '06 #4
Try to add a Launch condition from the Launch conditions editor..

Mar 8 '06 #5
Hi Haim,
How can I create the same feature in my setup project,
so the client will automatically check if there is a newer
version or not?


The ClickOnce project integrates the checking update routine inside its
application code, so the application will check its update automatically
while running.

But the VS2005 setup project is an independent project from the project it
installs. It cannot add the checking update routine to the target project.
And the setup package would not be invoked when its installed application
running. So the setup project could not implement the feature as the
ClickOnce project's. If you want a ClickOnce application's upgrading
feature to your application, you need to implement the checking update
routine manually.

Thanks for your understanding!

Best regards,

Gary Chang
Microsoft Community Support
================================================== ====
PLEASE NOTE the newsgroup SECURE CODE and PASSWORD will be updated at 9:00
AM PST, February 14, 2006. Please complete a re-registration process by
entering the secure code mmpng06 when prompted. Once you have entered the
secure code mmpng06, you will be able to update your profile and access the
partner newsgroups.
================================================== ====
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====

Mar 9 '06 #6
HIK
thank you Gary. Basically that is my question. How do I implent the
checking update routine manually?

Haim

Gary Chang[MSFT] wrote:
Hi Haim,

How can I create the same feature in my setup project,
so the client will automatically check if there is a newer
version or not?

The ClickOnce project integrates the checking update routine inside its
application code, so the application will check its update automatically
while running.

But the VS2005 setup project is an independent project from the project it
installs. It cannot add the checking update routine to the target project.
And the setup package would not be invoked when its installed application
running. So the setup project could not implement the feature as the
ClickOnce project's. If you want a ClickOnce application's upgrading
feature to your application, you need to implement the checking update
routine manually.

Thanks for your understanding!

Best regards,

Gary Chang
Microsoft Community Support
================================================== ====
PLEASE NOTE the newsgroup SECURE CODE and PASSWORD will be updated at 9:00
AM PST, February 14, 2006. Please complete a re-registration process by
entering the secure code mmpng06 when prompted. Once you have entered the
secure code mmpng06, you will be able to update your profile and access the
partner newsgroups.
================================================== ====
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====

Mar 9 '06 #7
Hi Haim,

I am not very clear how do you publish your product. If you put your new
product installation package on the web, your application needs to query
that target product info page or access a corresponding web service to
check whether an product update is available or not.

Then your application may download that new version installation package,
close itself and install the new one.
Thanks!

Best regards,

Gary Chang
Microsoft Community Support
================================================== ====
PLEASE NOTE the newsgroup SECURE CODE and PASSWORD will be updated at 9:00
AM PST, February 14, 2006. Please complete a re-registration process by
entering the secure code mmpng06 when prompted. Once you have entered the
secure code mmpng06, you will be able to update your profile and access the
partner newsgroups.
================================================== ====
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====

Mar 10 '06 #8

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

4 posts views Thread by Nick | last post: by
reply views Thread by Adam Clauss | last post: by
4 posts views Thread by Brett Romero | last post: by
7 posts views Thread by rustysmith | last post: by
1 post views Thread by rohan_from_mars | last post: by
6 posts views Thread by andrewbb | last post: by
reply views Thread by =?Utf-8?B?UGV0ZQ==?= | last post: by
1 post views Thread by CARIGAR | last post: by
2 posts views Thread by Marin | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.