Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


On 25/07/2011 19:14, plino wrote:
Jonathan

The most interesting part is that if you stop the Windows installation after
the files are unpacked and then execute the msi file on a batch of PCs you
will not be bothered by the MS VC++ outdated libraries because they are not
contained in the msi :)

In fact this is explained in the readme file:

"If you perform an administrative installation using setup /a, you need to
make sure that the file msvc90.dll is installed on the system. This file is
required for LibreOffice to start after an administrative installation."

So this seems to be the solution for not installing outdated runtimes. Thank
you for helping me find this hack :)

--
View this message in context: 
http://nabble.documentfoundation.org/Windows-MSI-installers-WAS-LibO-3-4-2-RC1-under-Windows-tp3195485p3198079.html
Sent from the Discuss mailing list archive at Nabble.com.

My pleasure. I was thinking about enterprise setups with large amounts of computers to configure applications on.

--
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.