Installing VS.NET on a 64-bit Computer - visual-studio

I am trying to install Visual Studio .NET on a Windows 7 64-bit computer. When I run the setup, I get this error message:
"Unable to install Visual Studio .NET on a 64-bit operating system."
Searching Google tells me other people have run into this, but I don't see any solutions. Has anyone found a way around this?

No, you can't install VS.NET on a 64-bit computer. You can install it on Windows 7 x86.
I was certain I saw claims that it worked on Windows 7 x64, but I've since become convinced that won't work.
If you really need it on a 64-bit computer, create a 32-bit virtual machine and install it there.

Related

Building OpenCV 3.4.1 on Windows 10 targeting Windows XP

I have an application that uses the OpenCV libraries. This application has to be installed on an old PC running Windows XP 32 bit. When running the application I got the error:
Kernel32.dll unable to import InitializeCriticalSectionEx
According to my searches, to fix this issue, I have to tell the compiler that the library will be used on Windows XP by setting the variable _WIN32_WINNT to 0x0501. I'm trying to apply the solution found in this entry in github, but I'm not very experienced with compilers and I'm having hard time to locate the files CMAKE_CXX_FLAGS and CMAKE_C_FLAGS. Can anyone explain me exactly what file I have to modify?
I'm using Visual Studio 2017 and Cmake on Windows 10.
I tried to use the toolset v140_xp in Visual Studio, but without success. At the end of the day, I got an old PC with Windows XP, installed Visual Studio 10 and tried to compile. The problem was that the latest version (3.4.1) won't compile for Windows XP. AFAIK, the most recent version of OpenCV that compiles for XP is 3.2. Probably it is possible to cross-compile it on Windows 10 using the v140_xp toolset, but I did not try as I already got the old XP with Visual Studio 10.

Visual Studio 2015: x64 vs x86 for running app in emulator?

I'm running Windows10 Pro fresh install, Visual Studio 2015 fresh instal with UWP, WP8 SDKS and Cordova tools instaled. Hyper-V is enabled. According to Control Panel, my processor is an Intel Core i7 with x64 architecture.
I'm trying to run the HelloWord Cordova project on a Windows phone emulator (Windows10, tried various devices). Surprisingly, it works when I select x86, but if I choose x64, I get the following error: bootstrapper could not connect to machine
Still, even after deploying x86 app to emulator, I get other problems in some rare cases (trying to declare a share target and trying to share Edge link to my app crashes WWAHost.exe), so if possible I'd like to try x64 to see if it solves these problems as well (probably not, as I got same problem on device HP Elite X3/ARM).
Can someone explain me why my processor is supposed to be x64 and that I can't deploy my app to the emulator actually only works by selecting x86?
Can someone explain me why my processor is supposed to be x64 and that I can't deploy my app to the emulator actually only works by selecting x86?
It's because the Virtualization is x86 (It's a x86 virtualized system). You can find it under C:\Program Files (x86)\Microsoft XDE\<VersionNumber>\XDE.exe.
Task Manager:
And when you are deploying the app to the Emulator, you are actually deploying your app to the x86 virtualized system. So it won't work if you select x64.

VS2010 express on 64Bit windows - can it compile 32bit binaries without the win7 sdk?

i can't find this information anywhere. I know that if you install vs2010 express on a 32bit os you need the win7 sdk to build 64 bit, but is it the same the other way round?
EDIT - I am interested in the c++ version, but I guess it's probably the same for others
thanks
oli
By default VS2010 Express will only target Win32. It doesn't matter if you are running Win7-64, MSVC++ Express uses the 32-bit tools unless you install the SDK.
From MSDN:
64-bit tools are not available on Visual C++ Express by default. To enable 64-bit tools on Visual C++ Express, install the Windows Software Development Kit (SDK) in addition to Visual C++ Express.
I have been able to successfully build and deploy C# apps from a Win 7 64bit machine onto machines running 32 bit Windows XP, Vista and Win 7 without any extra SDK. So far I have had no issues.
Regards
AJ

Visual Studio 2008 x86 install on windows 7 64 bit

I am getting an error when the setup autorun executes.
It states that it is not compatible with the 64 bit operating system and does not allow me to install it. Is the VS installer 16 bit? The error also mentions this but I am not sure if it's true.
How can I by-pass this?
If I cannot, can some one suggest another VS that I should purchase? is there a 2008 (or higher) 64 bit version that I should run on windows 7?
I've never had any problems installing VS 2008 Team Suite on Windows 7 x64 RTM. You might have a corrupt installer. Also you may check if this helps.
Not a great help to you, but I am running Visual Studio 2008 Standard edition on Windows 7 64-bit without any issues. My installation was from an MSDN subscription media but it shouldn't make a difference.
There is no 64-bit version of Visual Studio 2008 currently.
There is someone here with a similar problem, you could try their solution.

Side-by-side assemblies, Windows 7, and Visual Studio 2005

I have a Windows 7 machine with Visual Studio 2005 SP1 installed. Using this, I build an application which loads a DLL at runtime compiled with VS2005 SP1 but on Windows XP. This fails, with the following error:
"...\foo.dll": The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail.
The DLL loaded is compiled against the debug CRT. The answer to this question hints that vcredist_x86.exe only contains release-versions of the CRT. I'm not sure if that is relevant in this case, since both my machine and the machine on which the DLL was compiled on both have the full VS2005 SP1 installed.
Should I attempt to rebuild the DLL on Windows 7 (I'd prefer not to), and will that cause the DLL to become unusable on the Windows XP machine?
Problem solved. The problem was that the Windows 7 machine did not have the KB971090 update which was installed on the Windows XP machine which built the DLLs. I had to explicitly tell Windows Update that I wanted to receive non-Windows updates in order to be able to install the update.

Resources