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.
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 have had a website up and running for over 3 years with SAP .net connector 3.0 in 32 bit format. Unfortunately the Windows 2003 server that was hosting this application has failed. Our network team has created a new Windows 2012 server, and request the website be re-written in 64 bit. I have successfully added the reference to the x64 version of sapnco dll's, but now when I try to compile website, I'm getting an error on my page directive.
The error is "ASP.NET Runtime error: Object reference not set to instance of an object"
None of the code itself (ECCDestConfig.vb and code behinds) does not show any errors. This error is appearing on the page directive of ALL my .aspx web pages in this project, even pages that don't call SAP.
I have set the configuration manager to use x64 as the active solution platform.
I am really stuck - and could use some help.
SAP .NET Connector needs Microsoft Visual C++ runtime of a specific version, which depends on both the .NET framework version and the version of the Operating System (32-bit or 64-bit).
According to the SAP official documentation, you need one of the followings:
NCo 3.0 32-bit (x86), .NET 2.0 (also 3.0, and/or 3.5): Microsoft Visual C++ 2008 Redistributable Pack (x86) (mscvp80.dll)
NCo 3.0 64-bit (x64), .NET 2.0 (also 3.0, and/or 3.5): Microsoft Visual C++ 2008 Redistributable Pack (x64) (mscvp80.dll)
NCo 3.0 32-bit (x86), .NET 4.0: Microsoft Visual C++ 2010 Redistributable Pack (x86) (mscvp100.dll)
NCo 3.0 64-bit (x64), .NET 4.0: Microsoft Visual C++ 2010 Redistributable Pack (x64) (mscvp100.dll)
Problem solved. I used VB in Visual Studio 2013 with the 64 bit SAP .nco . The problem was I had created a "website" not a new "project. Once I did, and loaded the SAP DLL's as references to the project, and changed the configuration to use x64, new web pages I added did so without error. I might note, I aslo installed SAP GUI 730 on the same server. Its working now, both interacting with SAP and a separate SQL database,
Thanks for your answer
To be able to execute the x64 dlls in VStudio, it must be verified that the project is being compiled also in x64. You have to go to Tools, Options ..., Projects and Solutions, Web Projects. And check "Use the 64 bits."
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
I have already using Visual Studio 2010 for my project. Now I have to work with a Visual Basic 2006 legacy application. Can I install VB 2006 Enterprise Edition on my system?
Will this affect Visual Studio 2010?
Yes. Visual Studio 2010 and Visual Studio 6 will happily install side-by-side.
You can run multiple versions of Visual Studio on the same machine. I currently have VS2003, VS2005, VS2008 and VS2010 installed and am using all of them.
Where you may get into problems is with something like hooking up the older ones to TFS. This can be done, as I have VS2003 and VS2008 connected to TFS2010, but my VS2005 won't work as it whinges about the provider for some reason.
Another area to watch out for is IIS. As you have already installed VS2010, IIS may be defaulting to .Net 4.0 so if you start deploying .Net 2.0 apps then the websites may not work without some adjustment of things like app pools.
But if you are just using them independently of each other then you should be fine. If you're really paranoid, consider creating a VM and installing the old VS on it.
EDIT
I see from your edited post that you were talking about VB6. This also can be installed alongside any of the later versions of Visual Studio.
I am trying my hands on source code of WIX 3.6 to debug something as well as learn something.
On executing make.bat (present in root folder of WIX source) file, first i got NAnt not found. So I downloaded NAnt and updated make.bat file. On executing the file again I am getting this error
NAnt 0.91 (Build 0.91.3881.0; alpha2; 8/17/2010)
Copyright (C) 2001-2010 Gerry Shaw
http://nant.sourceforge.net
Buildfile: file:///D:/wix36-sources/wix.build
Target framework: Microsoft .NET Framework 4.0
Target(s) specified: inc
[readregistry] Registry Path Not Found! - key='Software\Microsoft\VisualStudio\VSIP\10.0\';hive='Microsoft.Win32.RegistryHive[]';
[readregistry] Registry Path Not Found! - key='Software\Microsoft\VisualStudio\VSIP\10.0\';hive='Microsoft.Win32.RegistryHive[]';
[property] Target framework changed to "Microsoft .NET Framework 2.0".
[property] Read-only property "dir.hhw" cannot be overwritten.
[property] Read-only property "hhw-found" cannot be overwritten.
BUILD FAILED - 2 non-fatal error(s), 2 warning(s)
D:\wix36-sources\wix.build(65,4):
Build file 'D:\wix36-sources\test\wixtests.build' does not exist.
I have .Net framework 4.0 installed on my local. Also I searched through registry for the registry key mentioned in the error and didn't found. Am I using right version of NAnt?
Do you have all of the prerequisites as described in the documentation?
In order to fully build WiX, you must have the following Frameworks and SDKs installed:
NAnt (0.90 or later)
The following components from the Windows SDK for Windows Server 2008 and .NET Framework 3.5, Visual Studio 2008, Microsoft Windows 7 SDK, and/or Visual Studio 2010:
x86 and x64 compilers, headers and libraries
IA64 headers and libraries are optional, but they are necessary for IA64 custom action support
If you want to be able to build optimized IA64 binaries, you'll need both the Windows SDK for Windows Server 2008 and .NET Framework 3.5 SDK AND Visual Studio 2008 installed; or the Microsoft Windows 7 SDK AND Visual Studio 2010.
HTML Help SDK 1.4 or higher [installed to Program Files or Program Files (x86)]
The missing registry key seems to be related to the VisualStudio SDK - you don't need this for basic WiX.
If you have all of the prerequisites, try passing the -debug switch to Nant for more detailed debugging output.
To solve this problem:
[readregistry] Registry Path Not Found! - key='Software\Microsoft\VisualStudio\VSIP\10.0\';hive='Microsoft.Win32.RegistryHive[]';
[readregistry] Registry Path Not Found! - key='Software\Microsoft\VisualStudio\VSIP\10.0\';hive='Microsoft.Win32.RegistryHive[]';
If you used Visual Studio 2010 SP1 you need Visual Studio 2010 SP1 SDK