How can Microsoft XML Parser 4.0 be installed from Inno Setup? - inno-setup

I need to install Microsoft XML Parser 4.0 from Inno Setup.
How can that be done?
I was given a task to embed MSXML in the installer of ours. It's a proprietary piece of software our company makes (for accounting, it uses XML to store and exchange data). Apart from modern systems It's also going to be installed on many old systems using Windows XP.
I'm using Inno Setup 6.1.2.
Also, is there a quiet mode of installation as an option? So the users won't have to click anything and just be notified that MSXML was installed?

Did you Google this?
https://silent-install.net/software/microsoft/msxml_parser/4.30.2107.0
Eg:
msxml.msi /qn /L* "%temp%\XML Parser 4.30.2107.0.log" /norestart ALLUSERS=2
If you look at the Msiexec (command-line options) it does say the qn switch will display no user interface.

Somewhat of an aside, the requirement of installing both on XP and on 'modern' systems may create a conflict that you or your installer will have to resolve.
From Installing and Redistributing MSXML 4.0:
System Requirements
MSXML 4.0 is supported in Windows Server 2008 R2, Windows 7, Windows
Server 2008, Windows Vista Windows Server 2003, Windows XP, and
Windows 2000
From Installing and Redistributing MSXML 6.0:
System Requirements
MSXML 6.0 is supported in Windows Vista; Windows 2000 Service Pack 4;
Windows Server 2003; Windows Server 2003 Service Pack 1; Windows XP
Service Pack 1; Windows XP Service Pack 2.
MSXML 6.0 is preinstalled with Windows Vista. For earlier versions of
Windows, you can install MSXML 6.0 as a separate download.
So you can only use MSXML4 below Vista. And with Vista and above you should be able to reply on MSXML6 already existing.
Your installer could perform an OS version check (alt ref) and then only install MSXML4 if needed. Or you might be able to detect specifically if MSXML6 is installed and then install MSXML4 only if not (assuming therefore its an older system).
But I would test your application (if you haven't already) and see if it will run against MSXML6; it may, without changes. If so then I would forget MSXML4 and include MSXML6 in the installer instead (*). That way your installer could just run it 100% of the time, and expect that on Vista and up it would just do nothing. Your installer would therefore be simpler plus you would be taking advantage of "MSXML 6.0 provides security and performance improvements over earlier MSXML versions." noted here.
(*) Unless you have to run on WinXP pre-SP1?

Related

Running Platform Builder 5.0 on recent operating systems

Platform Builder 5.0 is only supported on Windows 2000 and XP.
This question is to aid those looking for a way to run Platform Builder 5.0 on more recent operating systems.
A few reasons one might want to do that:
Corporate IT policy may not permit the use of Windows 2000/XP
With time, genuine copies of Windows 2000/XP may become increasingly hard to obtain
Depending on your overall setup and requirements, might eliminate the need for using a virtual machine for Platform Builder 5.0
You may simply wish to run a more modern and secure operating system
This answer explains how to install and run Platform Builder 5.0 on operating systems it is not officially supported on.
Windows Server 2008 and 2012
This procedure has been found to work on:
Windows Server 2008 (32-bit)
Windows Server 2012
Windows Server 2012 R2
It is recommended that you install Platform Builder before joining a Windows domain. I've had some issues getting the Platform Manager components registered while logged in as a domain user. See also the description further below.
Virus protection software might prevent the installation of .NET Framework 1.1, at least this has been a problem with Symantec Endpoint Protection. You may have to remove any security products before starting the installation (these may be re-installed later, but see the note below on the Full vs. Basic version of Symantec EP).
To install PB5, start by copying the contents of the installation CD (or mounted .iso) to a local folder, from here onwards referred to as the installation folder.
Use an .msi editor (like Orca) to remove the following entries from Microsoft Windows CE 5.0.msi in the installation folder:
OS version check (Table LaunchCondition, Action (MsiNTProductType=1 OR ...)
Emulator device driver (Table InstallExecuteSequence, Action CA_InstallVMMDriver.3D2F911E_A60A_4C07_8F7D_5306DC073E9A)
From the installation folder, run, in this order
ISScript8.msi (installs the InstallShield 8.0 script engine)
dotnetfx.exe (installs .NET Framework 1.1)
Microsoft Windows CE 5.0.msi (installs Platform Builder 5.0)
The installation may appear to hang at the Registering Platform Manager components step. It should proceed after a few minutes. If it is still stuck after, say, ten minutes, and your machine is joined to a Windows domain, then kill the installer in Task Manager, leave the domain and try installing again (you can rejoin after the installation is complete).
During the installation, you will receive a warning about compatibility issues. Select Don't show this warning again and click Run the program without getting help.
After the installation has finished, add a registry entry as follows.
If installing on a 32-bit system:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools]
"SharedFilesDir"="C:\Program Files\Common Files\Microsoft Shared\"
Otherwise (installing on a 64-bit system):
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Shared Tools]
"SharedFilesDir"="C:\Program Files (x86)\Common Files\Microsoft Shared\"
Next, install Windows CE / Platform Builder updates as required (i.e. the "monthly updates" provided by Microsoft).
Optional: If any of your Windows CE targets require CJK support, you will need to update the cenlscmp tool to avoid an error during the makeimg phase. While this bug has long been fixed in Platform Builder 6.0 (PB6), the PB5 version has been left in the dust. So for CJK support you will need to copy cenlscmp from a PB6 installation, i.e. copy C:\WINCE600\PUBLIC\COMMON\OAK\BIN\I386\cenlscmp.exe to the corresponding folder in your new WINCE500 tree. Note that I've only tested the PB6 version; it is likely that newer versions would work too.
Optional: If you need support for building SDKs, you must make a copy of the Platform Builder help files, or a hard-coded assumption in the SDK builder will cause the build to fail. Copy the directory C:\Program Files (x86)\Windows CE Platform Builder\5.00\cepb\help to C:\Program Files\Windows CE Platform Builder\5.00\cepb\help.
Launch Platform Builder.
You will see a warning about compatibility issues. Select Don't show this warning again and click Run the program without getting help.
Optional: In the main window, click Tools | Customize. Click the Build OS menu once to open it. Drag the Build and Sysgen menu item out of the menu and drop it when the cursor displays a small 'X'. This will remove a dangerous command that, if clicked by accident, will require reinstalling Platform Builder. Hit Close to dismiss the Customize dialog box.
Platform Builder 5.0 is now ready to use, including the IDE itself, the build system, the help system, the debugger, and the run-time licensing tool.
Features that I haven't tested and which may or may not work include CETK and the emulator (the latter highly unlikely to work, as the emulator device driver had to be removed from the .msi).
If you use Symantec Endpoint Protection, be aware that the Full version may prevent pbxmlutils - an important Platform Builder tool - from running. This does not appear to be an issue with the Basic version.
One last hurdle is to configure the firewall to permit debugger traffic. To do this, open Windows Firewall with Advanced Security and
Under Inbound Rules, hit New Rule...
Select Program, Next
Enter the Path %ProgramFiles% (x86)\Windows CE Platform Builder\5.00\CORECON\BIN\cesvchost.exe, click Next
Ensure Allow the connection is selected, Next
Ensure Private and Domain are selected (but not Public, unless you really need this), Next
Enter a Name, e.g. "Platform Builder 5.0 debugger - cesvchost", Finish
Repeat the above with the path %ProgramFiles% (x86)\Common Files\Microsoft Shared\Windows CE Tools\Platman\bin\cemgr.exe.
Platform Builder will now be able to receive BOOTME frames, upload images, and connect to target with the kernel debugger.
Windows 7 and 8
The procedure documented above will not work for 64-bit Windows 7 or 8 (32-bit not tested).
Modifying the .msi as described makes the installation hang at the Registering Platform Manager components step. Removing the Platform Manager components from the installer causes a number of other issues, including failed registrations of the Help system and some common controls. More importantly, with Platform Manager missing it will not be possible to install any Windows CE/Platform Builder updates, making it virtually impossible to build any non-trivial CE project.
Windows 10
Not tested.

service bus 1.0 not showing up in windows platform installer 4.5

I am trying to install Service Bus 1.0 on my developer machine. When i am searching for "Service Bus 1.0" in the web platform installer 4.5, it is not able to find it.
I downloaded .exe file manually from http://go.microsoft.com/fwlink/?LinkID=252361. When the setup runs, it gives me an error message in Web Platform Installer that "Microsoft web platform installer couldn't find the product you tried to install. Either the link you clicked is incorrect or you may be overriding you feed with different feed."
I checked my feed and it is set to "default".
My operating system is windows 7 SP1 Enterprise Edition.
VS 2010 and V2012 installed. I also have SQL Server 2008 R2 Express
Any idea what is causing this problem?
It turned out that my OS is 32 bit and it requires 64 bit OS.

installshield 2012 LE and windows service for windows 2008 r2 64 bit VS.NEt 2012

I have windows service developed by VS.Net 2012 , Windows 7 32 bit and installshield 2012 LE for setup.
In the development machine everything going well ,installation completed and service working fine .
When upload it to the server (windows server 2008 R2 SP1 64bit) during the installation , installation stopped and rolled back because of error 1001 .
Advise Please
You're in a rough spot. Error 1001 comes from an InstallerClass, which uses a very fragile technology. The error 1001 has many different possible sources, ranging from an unhandled exception to what feels like the phase of the moon. However InstallShield LE doesn't really support installing services any other way.
The best advice I can offer is to use Windows Installer support for installing services. But in order to do that you will have to use a different installation creator. If you want to stick with InstallShield, the Professional edition has a view in which you can configure the Windows Installer support for services.
You can use Windows Installer XML (WiX) to author a merge module that installs a windows service and then consume that merge module in a InstallShield LE project. See:
Augmenting InstallShield using Windows Installer XML - Windows Services
Installshield LE 2012 doesn't support 64bit.
There is a new beta available of Installshield LE that is supposed to add this feature: http://blogs.msdn.com/b/visualstudio/archive/2013/08/15/what-s-new-in-visual-studio-2013-and-installshield-limited-edition.aspx
It's also supposed to support the proper Windows Installer for installing services now, even in the LE (via "3 Configure the Target System" -> Services"). However I've not been able to get that bit working yet - maybe there's some magic setting I've missed.
You could try using this version - let me know if you have any luck getting it working via the proper windows installer services!

Does open xml sdk 2.0 support linux platform or not?

I want to know Whether OPENXML SDK provide support for linux platform or not?
Supported Operating Systems:Windows 7;Windows Server 2003 Service Pack 2;Windows Server 2008 R2;Windows Server 2008 Service Pack 2;Windows Vista Service Pack 2;Windows XP Service Pack 3
It MIGHT run under mono but I really doubt it. It depends on .Net 3.5 and System.IO.Packaging which has a partial implementation in mono.

Sharepoint 2010 development on Windows XP 32-bit?

Possible or not?
I know Sharepoint 2010 Server won't even run on a client side of Vista/Windows 7 64-bit, forget about Windows XP 32-bit.
But if I can install and use Visual Studio 2010 on Windows XP just fine, shouldn't Sharepoint development tools also work on Windows XP 32-bit?
The thing is I have a very old laptop (from 2005) that doesn't even support 64-bit architecture so I am stuck with WinXP 32bit.
If there is any way at all of (Remote?) Sharepoint development on Windows XP 32-bit with VS2010 please let me know.
Most of what the developer tools offer you make two assumptions:
You are running on a 64-bit architecture
SharePoint is installed side-by-side with Visual Studio
Running on a 32-bit XP machine breaks these assumptions. Many of the built-in Visual Studio productivity aids, such as the deploy and retract commands, will fail. I couldn't even create a project using the SharePoint 2010 project template under similar conditions.
You might make some headway by using regular class library or web application projects, copying SharePoint .dll's from a server's GAC (for use as references) and by manually creating your .ddl and .wsp files using MakeCab (as I did with 2007, with a little help from PowerShell); however, it sounds excruciating compared to running on Vista SP2 X64 or Windows 7 X64 with SharePoint installed.
As per the above answer, VS 2010 SharePoint projects require a local installation of SharePoint. You can use external tools for doing your development, such as WSPBuilder, but I do not recommend this approach. You are best sticking to the MS tools.
Your options are:
Upgrade to Windows 7 x64 or Server 2008 R2
Run VMWare Server (free) which should enable you to run a 64-bit VM on a 32-bit host (I think? Not sure about this assumption actually), and create a VM with Win7 x64 or Win 2008 R2 for SP development.
You can use Win7 64bit as your dev environment
http://msdn.microsoft.com/en-us/library/ee554869.aspx

Resources