What needs to be done to build for Windows XP using the latest version of WAF and MSVC 2015? In the GUI, you can set the platform toolset to "Windows XP." Can this be done in the wscript?
Related
Is it possible to install Agent on windows XP?
I know it is possible to install on Linux - could not find a way to install on Windows XP
I only need to run the build on the XP machine
Using Azure DevOps Server 2020
For Self-hosted Windows agents, currently supported Windows OS versions:
Client OS: Windows 7, 8.1, or 10
Server OS: Windows 2008 R2 SP1 or higher
Windows XP is no longer supported as the host of agents.
To view more details, you can see "Self-hosted Windows agents".
Solution
Using Jenkins which can install agent on windows XP.
Set Web-hooks to connect to Jenkins server
Problems
Very Slow GIT pull/clone/push on Windows XP
PowerShell Scripts are limited to Windows XP PowerShell version
Git Version Limited to Git-2.10.0-32-bit
LFS version Limited to git-lfs-windows-v2.8.0 (GO lang limition)
Windows credential must use git-credential-winstore - GIT CREDENTIAL ON WIN XP
I hope this will help anyone needs to use XP
I have developed an application with Visual Studio 2012. I have also created a setup.exe with Install Shield 2010 Premium for my application. My development environment is Windows 8 64-bit, the application is compiled under Release Win32. The developing language is C++.
After building setup.exe, I ran it on another computer that is running on Windows 7 64-bit. An error message box pops up saying MSVCP110.dll is missing or not configured to run on Windows. Any ideas as to why this may be?
I tried installing Visual C++ Redistributable for Visual Studio 2012 (http://www.microsoft.com/en-au/download/details.aspx?id=30679), but it still gives the same error.
Any help would be appreciated.
MSVCP110.dll is really part of VC++ Redistributable package.
Try to install both versions of them: x86 and x64 if your machine is 64 bit.
For 32bit machine you need only x86 package.
I am creating msi file using visual studio. But i need to know how to test .Net Framework and SQL server are installed before doing installation of msi.
Is there any settings (Or) any windows installer are available.
Windows Installer proposes use the Bootstrapping for these purposes. You pack your MSI to Setup.exe and set needed prerequisites, in your case .NET FW 4 and SQL. When user starts Setup.exe, it checks if .NET and SQL are installed, if not installs them and then run the your MSI. You could include the installation files of .NET or SQL in your setup.exe or set link from where installation downloads it.
There is more information about Windows Installer Bootstrapping.
Is it still possible to WHQL-certify drivers for Windows XP, given that it has reached its end of life?
If so, which version of the Windows Logo Kit do I need?
Windows Logo Kit 1.6 won't install on my Windows XP Service Pack 3 machine.
In particular, when I try to install Windows Logo Kit 1.6 on Windows XP with Service Pack 3, I'm unable to install any of the components, with the detail text being:
http://pastebin.com/rWRfMiZy
e.g. things like:
REQUIRED COMPONENT: "EULA" unavailable due to status = Not Installable
ISSUE: Unsupported OS SKU
DETAIL: Current OS: Windows XP (Supported OS: Windows Longhorn Server)
ISSUE: Unsupported CPU Architecture
DETAIL: Current CPU: x86 (Supported CPU: x64)
Yes, you can still certify hardware for XP (but not systems). WLK 1.6 is the correct version and should install on XP. See this.
What happens when you try to install it?
EDIT: It's been a while since I was involved with WHQL testing, so ignore the information above. That link is wrong. I've done some further investigation and here are the facts:
The kit can be installed on and run from a Windows 2003 server only. That is the controller/master box that runs, controls and collects the test info. It also makes the submissions. You need a second test box running the OS you're certifying for. It runs as a slave to the server.
The only way to certify for XP is to certify for Vista, 2003 or Win7, and then you are automatically approved for XP.
I am trying to run NUnit in Visual Studio 2003 on 64-bit Vista but with no success.
I have set the Debug Mode of the Project to "Program" and the Start Application to "C:\Program Files (x86)\NUnit 2.4.8\bin\nunit.exe". The Test Project is set as the StartUp Project. All the code is in .NET 1.1. Unlike .NET 2.0 the processor architecture cannot be targeted (when a 1.1 executable is loaded on an x64 machine it is run in the WoW64 as a 32-bit process and utilises the 32-bit framework).
After I hit Debug > Start I receive the error window "A project with an Output Type of Class Library cannot be started directly". I am stuck and cannot get NUnit to run.
The nearest related question on stackoverflow dealt with getting NUnit to run on Vista x64 in Visual Studio 2005 "Nunit.exe cannot work on Vista 64bits if x86 build (stackoverflow.com/questions/208985/nunit-exe-cannot-work-on-vista-64bits-if-x86-build).
Additionally NUnit did not install a nunit-x86.exe from the NUnit-2.4.8-net-1.1.msi image.
My Development Environment
Vista x64 with SP1
Visual Studio 2003 (version 7.1.3088)
.NET Framework 1.1 (version 1.1.4322 SP1)
NUint 2.4.8 (installed from NUnit-2.4.8-net-1.1.msi)
I found the issue - and it had nothing to do with Vista x64.
I had set the Debug Mode of the main Project to "Program" and the Start Application to "C:\Program Files (x86)\NUnit 2.4.8\bin\nunit.exe" and not the Test Project.
Even though I had set the Test Project to the StartUp Project the Debug Mode in the Test Project was still set to the default "Project" and not to the "Application". I switched the debugging configurations around; so the main Project was set to "Project" and the Test Project contained the NUnit debugging configurations.
Summary: NUnit does run on Vista x64 in Visual Studio 2003.
IF your app is a 32-bit app, then you have to use nunit-x86.exe, it is built for testing a 32-bit application on a 64-bit system. See detail explanation here: http://www.nunit.org/index.php?p=nunit-gui&r=2.4.2