There is a limitation with LUA (non-administrative) patching an application on XP when the original installation was not done from removable media (when using Windows Installer 3). This limitation has apparently been removed in Windows Installer 4
For such an installed application, would upgrading Windows Installer to v4 permit me to LUA-patch the application? Or does the fact that the app was originally installed using Installer v3 limit me?
Related
I am putting together a WiX installer that includes silently installing DirectX 9:
dxsetup.exe /silent
How do I tell WiX how to un-install DirectX? Is there another switch on the command line?
I need to be able to configure the installer to un-install DirectX automatically, else users complain if they can't uninstall.
For the DirectX End-User Runtime (aka DirectSetup or DXSETUP), it has long been recommended that you don't even try to uninstall it.
In any case, on most versions of Windows you can't 'uninstall' DirectX and running DXSETUP doesn't actually "Install DirectX" either as it's built into the OS. It can only be updated by installing a new version of the OS, installing a Service Pack, or applying a Windows Update. This applies to all versions of Windows starting with Windows XP Service Pack 2, Windows Server 2003 Service Pack 1, and Windows XP x64 Edition.
DXSETUP is still useful for deploying stuff like legacy D3DX9, D3DX10, D3DX11, XACTEngine, XAudio 2.7, XInput 1.3, D3DCompile #43 or earlier, etc. It just doesn't ever install "DirectX".
See No So Direct Setup. If after reading this article you still think you need to run DXSETUP as part of your deployment, you should pick up the latest version of DXSETUP to avoid some potential issues, and trim it down to just those CABs you actually use in your application.
I was looking for some documentation which will explain what requirements of my installer will be if I made it with wix and burn...
I`m still not sure about that because that information is hard to get...
When I was looking for an answer i found dependency of VC++redist... so it is telling me if I wrote custom action in c++ I need to have these on my target machine?
Also If I want to have my own UI, using burn... automatically I need .net framework 3.5?
I want to write installer, with custom actions and custom UI, I don`t mind which language use to write custom action (c++ or c#) but I want to be able to use my installation on winxp...
So if anybody have some info about requirements of installers... I did just couple of simple installers... all of them are running on win7 all right... but what about winxp? Thanks
Note that WiX is not an installation environment of its own. To put it simply, it is a comfortable, XML-style way to describe your installation requirements that gets translated into Windows Installer .msi databases by its compiler and linker. In this respect, WiX is a relatively thin wrapper around Windows Installer technology, and while it does provide extra features to help the setup developers, its abilities are dictated by the underlying technology and its limitations are not of its own but the limitations of Windows Installer itself.
System Requirements from Windows Installer 3.1 shows this:
Supported Operating System
Windows 2000 Service Pack 3, Windows 2000 Service Pack 4, Windows Server 2003, Windows XP, Windows XP Service Pack 1, Windows XP Service Pack 2
Windows Installer 3.1 Redistributable supports Windows 2000 with Service Pack 3 or later, Windows XP, Windows XP Service Pack 1, Windows XP Service Pack 2 and Windows Server 2003. Windows Server 2003 Service Pack 1 contains Windows Installer 3.1 and therefore can't be installed or upgraded by this redistributable.
So it should work like a charm on xp machines.
Sources:
WIX Tutorial
MSDN
I have a Windows Desktop App ( WPF + c++ ).
I have just made a ClickOnce installer. I built it on Windows 7, but I want to certify the App for the Windows Store, so I'm running the Windows App Certification kit on Windows 8.
The installer works fine, it installs my application and puts an icon on Windows 8 start screen. My Application runs fine. I then uninstalled it ready to run the certification.
When I try to Certify it, the Application Compatibility Kit fails to install it ( a couple of windows flash open and closed SO fast I can't read them, I DON'T experience the installer dialog which would normally require some interaction from me).
Then the kit pops a dialog:
The Windows App Certification Kit did not detect any new applications
as a result of your installation. testing cannot continue unless an
application is successfully installed).
Previously a had a MSI installer that did seem to work with the compatibility kit (the app failed certification, but for legitimate reasons). Now I can't get the compatibility kit to even install my ClickOnce application. How can I certify my desktop app?
Edit Desktop apps are indeed possible in the store. See this. http://msdn.microsoft.com/en-us/library/windows/desktop/hh749939.aspx
ClickOnce applications are not eligible for Windows 7 and Windows 8 Software Logo program.
http://social.msdn.microsoft.com/Forums/en-US/windowscompatibility/thread/f10242cb-39f1-4f5e-ac1f-e55a6c722a6b
created in a prjeto. NET Compact Framework 3.5 for Windows Mobile 6.x.
I wonder how you do to create the installer (. cab) for this project?
How do deploy. NET Framework and SQL CE for Mobile?
Given a novice user.
Today I have an installer.cab and .msi for Windows
But to my system running is to install the SQL CE and Compact Framework 3.5. How to download and install these applications after the installation of my system?
Would not want to send these applications together because the size of the installer can get big
Thanks.
You're going to want to do a multi-CAB install. MSDN covers it here. CodeProject here.
I tried to start developing for Microsoft Surface. For that I first installed Visual Studio 2008. Then I followed this guide:
http://msdn.microsoft.com/en-us/library/ee804897.aspx
However there it says that only Windows Vista is supported. I'm still running Windows XP on my laptop and old PC and I don't want to update if not absolutely necessary. So I wonder if it is really necessary to use Windows Vista or if it is just a recommendation.
I already tried to install it on Windows XP, but every time i start the Surace SDK installer, the following error message appears:
This installation package cannot be
installed by the Windows Installer
service. You must install a Windows
service pack that contains a newer
version of the Windows Installer
service.
So I was wondering if this is the problem because I don't use Windows Vista. And if not, how can I solve this problem?
Yep, probably.
You can try installing the latest version of Windows installer.
http://support.microsoft.com/kb/942288
Windows vista is definitely required. I can't tell you if this is an artificially imposed requirement, or a physical incompatibility, but vista has been a requirement to install the SDK since was first released to Microsoft partners.
surface has a number of hard Vista dependencies. DWM is the most obvious one