|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Force install of new version within ClickOnceWithin ClickOnce deployment, is it possible to prevent the prompt that tells
the user there is a new version and asks them whether they wish to install it? i.e. is it possible to always force the installation of a new version? What is the whole scenario ? In 2.0 I told that the application is only
available online and it gets automatically updated from the web site if needed. Never tried but else check http://msdn2.microsoft.com/en-us/library/s22azw1e.aspx and in particular the "Making Updates Required" section (basically you tell the update should be checked before the application starts and then specify the new updated version as the minimum version required to force the update. I suppose the UI is suppressed as the upgrade should be now mandatory)... Good luck. -- Patrice "Dick" <Dick@nospam.nospam> a écrit dans le message de news: 6D3A09DA-96E1-41F8-8429-42E67710C***@microsoft.com...Show quote > Within ClickOnce deployment, is it possible to prevent the prompt that > tells > the user there is a new version and asks them whether they wish to install > it? i.e. is it possible to always force the installation of a new version? Hi Dick,
I agree with Patrice. When a user runs the application on a client and a new version is now available, we could force the new version to be installed by specifying a minimum required version for the application before the new version is published . To do this, right-click the project in the Solution Explorer and choose Properties from the short cut menu. In the Project Designer, switch to Publish tab and then click the Updates button. In the Application Updates window, select the checkbox before the option "Sepcify a minimum required version for this application" and then input the new version that is currently going to be published in the below textboxes. Press OK. Alternatively, we could modify the deployment manifest directly(i.e. appName.application file in the publish folder "c:\Inetpub\wwwroot\appName"). Open the deployment manifest file with Notepad. Navigate to the <deployment> element and add minimumRequiredVersion attribute into this element. The following is a sample. <deployment install="true" mapFileExtensions="true" minimumRequiredVersion="1.0.0.3"> Hope this helps. If you have anything unclear, please feel free to let me know. Sincerely, Linda Liu Microsoft Online Community Support ================================================== Get notification to my posts through email? Please refer to http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif ications. Note: The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 1 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations that require urgent, real-time or phone-based interactions or complex project analysis and dump analysis issues. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at http://msdn.microsoft.com/subscriptions/support/default.aspx. ================================================== This posting is provided "AS IS" with no warranties, and confers no rights. |
|||||||||||||||||||||||