Our continuous integration machine is using CruiseControl.Net and is running on XP Pro SP3. We're currently building x86 solutions in VB.NET from from VS2012 IDEs using the MSBuild.exe found in C:\Windows\Microsoft.NET\Framework\4.0.30319.
We had no problems until recently when code was recently added in one of the VS2012 solutions declaring a function that uses the Iterator keyword (as in Public Iterator Function (...)) and now MSBuild spews out a long list of errors for the declaration line. My understanding is that the Iterator keyword is newly supported for VB.net. Do we need an update for MSBuild or the VB compiler or something to get this to build on an XP machine?
[edit] Just noticed the VB compiler on the dev machines is v11.0.50938.18400 while the version on the integration machine is v 10.0.30319.233. I'm guessing that points to the problem. Next question: how do I get (or can I get) the 4.0 framework with the v11 compiler on to the cruise control machine running XP?
http://msdn.microsoft.com/en-us/library/hh162058.aspx
What's New in MSBuild 12.0 ?
MSBuild is now installed as part of Visual Studio rather than as part of the .NET Framework. The current MSBuild version number is 12.0. If you want to install MSBuild separately, download the installation package from MSBuild Download.
http://www.microsoft.com/en-us/download/details.aspx?id=40760
I'm not a big fan of this (moving it from the framework install). But it is what it is.
But you have an issue now.
Supported Operating System :
Windows 7 Service Pack 1, Windows 8, Windows 8.1, Windows Server 2008 R2 SP1, Windows Server 2012, Windows Server 2012 R2
Related
I'm learning PHP and I'm a newbie in apache, mysql,etc.
I tried to install WAMPServer (The current newest version 2.5) but I get the error:
msvcr110.dll is missing.
I have followed some instructions given here: WAMP shows error 'MSVCR100.dll' is missing when install
However, none of the advice worked for me. I have already installed Visual C++ for windows 32 bits and Visual C++ Redistributable for Visual Studio 2012. After that I installed Visual C++ 2008, it didn't worked either.
And even after that I installed vcredist_x86.exe. This gave me an option to repair my Visual C++, and so I did.
In all my tries I restarted my computer.
I didn't install Visual c++ for windows 64 bits because my os is running a 32 version.
Any ideas?
Thanks for your attention,
berga007
Please make sure you have the latest version of all of these Microsoft C/C++ Redistributable runtime libraries. You dont need the whole compiler, just these C/C++ runtime libraries.
The 2008 Redist (32bit) is used by wampmanager even if you installed the 64bit WAMPServer.
The 2010 Redist is used by some versions of Apache ( depending on compiler used ).
The 2012 Redist is used by some versions of Apache ( depending on compiler used ).
FOR WAMP 32bit
Microsoft Visual C++ 2008 SP1 Redistributable Package (x86)
Microsoft Visual C++ 2010 SP1 Redistributable Package (x86)
If you are using WampServer 2.4/2.5 32bit and therefore Apache 2.4.x
Microsoft Visual C++ 2012 is required And select vcredist_x86.exe
Due to the naming convention used by Microsoft dowmloading these libraries can get a little confusing so download them one at a time and install that download before downloading the next and installing that.
To check that you have all the required runtimes, launch 'Programs and Features' by
Start -> Control Panel -> Programs and Feature
For a 32bit system it should look something like this, ignore the fact that mine has what look like multiple versions of the same library, its just because when you download a newer version it does not remove the older revisions :-
32bit System example
UPDATE FOR 2018 (WAMPSERVER 3.x)
You need the following Visual Studio Redistributables:
2008
2010
2012
2013
2017
Get both the x86 and x64 versions if you're on a x64 machine.
Also, make sure you set skype to NOT use port 80, otherwise WAMP won't start when Skype is open.
I'm developing an application for a friend. I use Visual Basic 2012 (64-bit) and Windows 7 (64-bit).
I took a demo down to him to try it out to see what more features he wanted, and it was running ok.
When I got back the next week after implementing the new features, it refused to run on any of his Windows XP (32-bit) machines.
Error code:
MyApplicationName.exe is not a valid Win32 application
I tried it at a computer running Windows 7 (32-bit) which still worked all fine.
So, any ideas why it suddenly stopped running?
VS2012 will not generate an EXE that can run on XP when you use the default project settings. What matters is the .NET Framework version you target. If that's version 4.5 then there are two problems.
First one is that .NET 4.5 is not available for XP. Second one is important for this exception message, the compiler will mark the version of Windows that's required to run the EXE in the file header. That version number has always been set to 4.00. Until VS2012, it is now set to 6.00, the version number of Vista. XP will instantly reject your EXE with the "is not a valid Win32 application" message, even before it will tell you that it doesn't have .NET 4.5 installed.
Fix your problem by targeting .NET 4.0 or earlier. Project + Properties, Application tab, Target framework setting.
Try using corflags with /32bit+ and see if it works.
More information:
http://msdn.microsoft.com/en-us/library/ms164699.aspx
I'm trying to install Testacular (using nmp) on a Windows 8 Professional (64 bit) laptop, but it fails when it tries to install socket.io as part of this process. The error I get is
Could not load the Visual C++ component "VCBuild.exe".
To fix this, 1) install the .NET Framework 2.0 SDK, 2) install Microsoft Visual
Studio 2005 or 3) add the location of the component to the system path if it
is installed elsewhere.
I apparently have .NET framework 3.5 installed (it's checked under the add/remove Windows components bit in Control Panel), although I've not managed to find a vcbuild.exe. I tried installing an old copy of VS2005 but this resulted in a different error about an invalid project (.vcproj) file.
Can anyone suggest how I might get this working? Weirdly it installed fine on my work computer, which is very similar to the one on which it won't install (they're both 64 bit Win 8 Pro).
I ran into the same issue. I fixed this by adding this to environmental variable PATH: C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\vcpackages so that it can find vc build.
In Visual Studio 2010, the command line tool vcbuild.exe is replaced by msbuild.exe. So, please make sure you have right Visual studio.
I developed the project in visual studio 2010. That exe file is not supported for other PC's.
which dotnetframework to be installed? other than dotnetframework is there any other requirements needed?
Are you sure it's not the CPU type you specified during compiling (x86 vs x64 CPU). If you compiled in 64-bit and a user only has a 32-bit processor (x86), your code won't run.
The .Net Framework should work on any PC-based system, but be sure to include it in your deployment or setup package. (you can provide Excel, .NET Framework, and many other packages with your package.)
You should also try to find out what error messages your users are receiving -- which will point you in the right direction.
I am getting a few errors trying to download the new VS2012. Its a fresh install of windows 8 (did the windows update). I have tried not selecting all (no C++, lightswitch, blend, office tools)
I tried different mounting tools for the .ISO but no luck. VS2010 is still working. Running x86. Log file
Errors:
Critical: Microsoft Visual C++ 2012 x86 Minimum Runtime - 11.0.507 Cannot find the requested object.
Microsoft Visual Studio 2012 Pre-Clean Tool Cannot find the requested object
Microsoft Visual C++ 2012 x86 Additional Runtime - 11.0.507 Cannot find the requested object.
Microsoft Visual C++ 2012 Core Libraries, Team Foundation Server 2012, Microsoft Framework 4.5 Multi-Targeting pack.... and a few other ones cannot be found. Thanks!
Downloaded the web installer, and that seemed to work. It seems that the iso was corrupted as the MD5 did not match.