Checking for new versions in a setup project

8 Mar 2006 11:31 AM

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

8 Mar 2006 1:08 PM

Mike

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.

8 Mar 2006 1:23 PM

HIK

Thanks Mike. that was very easy.

Haim

Mike wrote:
Show quoteHide quote

> 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.
>

8 Mar 2006 1:35 PM

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:

Show quoteHide quote

> 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.
>

8 Mar 2006 2:12 PM

Mike

Try to add a Launch condition from the Launch conditions editor..

9 Mar 2006 7:57 AM

Gary Chang[MSFT]

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.
======================================================

9 Mar 2006 12:58 PM

HIK

thank you Gary. Basically that is my question. How do I implent the
checking update routine manually?

Haim

Gary Chang[MSFT] wrote:
Show quoteHide quote

> 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.
> ======================================================
>

10 Mar 2006 3:09 AM

Gary Chang[MSFT]

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.
======================================================