A converted vc++ 2003 project asks for msvcpd71d.dll when compiled on vc++2008 - visual-c++

After running the conversion wizard for a VC++ 2003 project - which ends with no errors - I get VC++ 2008 to sucessfully compile the project. Then, when launching the exe, a message pops up saying that the program cannot start because MSVCP71D.dll is missing. Any ideas on why a project compiled on vc++ 2008 would ask for MSVCP71D.dll ?
TIA
Update: I am trying to compile the ARToolkit using VC2008.
http://sourceforge.net/projects/artoolkit/files/artoolkit/2.72.1/ARToolKit-2.72.1-bin-win32.zip/download

What binary files came with the project? You seem to be linking against a static library or DLL that was built with VS7.1 -- hopefully you can rebuild that file in VC9 there.
Also, for what it's worth, note that the D at the end of "MSVCP71D.dll" indicates that it's looking for a debug build of that DLL.
The ARToolkit has several libraries in the lib folder, some of which with that same "d" suffix indicating a debug build -- those libraries were most likely built in VS2003 given your results. I'm not sure if you can rebuild in VS2008 from the lib/SRC directory, but that might be a start.

Looks like you need to build it as "release" so that the application does not look for that debug library at run-time.

Related

Error: msvcp90.dll is missing on running an application built in visual C++

I have a project which I am trying to run (in both normal and debug modes) but every time I run it, it throws the error:
The program cannot start because MSVCP90.dll missing from your computer. Try re installing to fix your problem.
After going through lot of posts about the same problem I've tried the following things but nothing seems to work.
Found this .dll file in C:\Program Files\Microsoft Office Servers\15.0\Synchronization Service\Bin\Microsoft.VC90.CRT and copy pasted it in C:\Windows\System32\. Checked that the environmental variable path has system32 in it.
Checked in the project properties and have set the Embed Manifest option under Manifest Tool-> Input and Output as Yes for Debug as well as Release modes
The project I am building depends on 3 other projects (they are in same solution) and have set Embed Manifest as yes for all of them. Another .exe built for same project built on other machine runs perfectly fine on my machine but the one that I build on the same machine does not work.
Thanks in advance for your help.
Your best bet is to install the "official" Microsoft Redistributable on all target PCs that will run your app:
http://www.microsoft.com/en-us/download/details.aspx?id=11895

DNN Errors 7.02.02

I have just download the DNN package no source and source version too opened it in visual studio 2012 in building it is showing these errors.
I unblock the zip folder before extracting. It works fine when I configure it through netmgr.exe option IIS. I want to do that from visual studio. P.S I am using windows 8.1
Error 1 Could not load file or assembly 'DotNetNuke.Web.DDRMenu' or one of its dependencies. The system cannot find the file specified. C:\Users\Umair\Downloads\DNN_Platform_07.02.02_Install\admin\ControlPanel\RibbonBar.ascx 8
Error 2 The file '/DNN_Platform_07.02.02_Install/DesktopModules/DDRMenu/Menu.ascx' does not exist. C:\Users\Umair\Downloads\DNN_Platform_07.02.02_Install\admin\ControlPanel\RibbonBar.ascx 9
Error 3 Unknown server tag 'dnn:MENU'. C:\Users\Umair\Downloads\DNN_Platform_07.02.02_Install\admin\ControlPanel\RibbonBar.ascx 13
I don't think you're supposed to even try to compile the website they distribute. It should come with everything already compiled for you. Disable building for the website project from the build options dialog to get rid of spurious errors if you have other projects you'd like to compile in the same solution.
I'm not all too surprised there's a few errors in there (It's DNN, what did you expect?)

Build failed for JSONCPP with Visual C++ 2010

I am building JSONCPP on Visual C++ 2010. But it is failing giving the error message:
Unable to start program
'D:\json-cpp-master\makefiles\vs71../../build/vs71/debug/lib_json\lib_json.lib'.
The system cannot find the file specified.
Why is it happening?
I encountered this problem 3 hours ago and figured out that it's named json_vs71_libmt.lib.
Next step is linking it with VS Project.
You'll also need to add
D:\json-cpp-master\include\ to ProjectProperties->Configuration Properties->VC++ Directories->Include Directories
D:\json-cpp-master\build\vs71\debug\lib_json\ to ProjectProperties->Configuration Properties->VC++ Directories->Library Directories
json_vs71_libmt.lib to ProjectProperties->Configuration Properties->Linker->Input->Additional Dependencies
After that it works perfect for me.
Hope this'll help.

Various issues installing igraph in Visual Studio 2010 and Cygwin/MinGW ("sys/time.h not found")

I couldn't get igraph to work with Visual Studio 2010 (supposedly many known issues), and so decided to try installing it in Cygwin. ./configure went fine. But make gave this error:
f2c/dtime_.c:16:23: fatal error: sys/times.h: No such file or directory
Makefile:2190: recipe for target `libf2c_la-dtime_.lo' failed
make[3]: *** [libf2c_la-dtime_.lo] Error 1
I tried installing it in MinGW and get the same error when I make. Should I be providing "sys/time.h" or a path to it? Where is sys/time.h? Using Windows 7.
Edit
The problems in Cygwin and MinGW was due to the wrong version of gcc being used by my clean installation of Cygwin (and a characteristic of MinGW). Solution here: Installing/compiling in Cygwin/MinGW - How to set the include "path"? (symbolic link?)
The problem in Visual Studio 2010 was due to building in "Debug" instead of "Release". One of igraph's creator, Gábor Csárdi, graciously provided an excellent step-by-step guide below that identified and resolved it.
Igraph actually does work with Visual C++ 2010 Express, we test this before releases, and I have just tried it. You need to do the following steps.
Download the source package specifically created for Visual Studio.
Uncompress the file into My Documents\Visual Studio 2010\Projects.
Open the igraph.sln solution file in igraph-0.6-msvc\igraph-0.6-msvc directory from Visual Studio.
Visual Studio offers to convert the solution file to the current format, do that. Just click on Next, Next and Finish.
On the toolbar, change 'Debug' to 'Release' to make release builds.
Choose Debug -> Build solution and wait until the library is built.
To test it you can open the solution file in the igraphtest directory, convert it as well, choose 'Release' builds, and then build it and run it from the command line. It is a simple C++ program that uses igraph to create a graph and write it into the file out.txt.
You don't have to set up include and library directories at all, everything is set up properly in the solution file, both for igraph and igraphtest.
is there an sys/times.h file?
I have a vague memory that I had to make that symlink on a system once.

How to install MSVCR90D.DLL

How do I install MSVCR90D.DLL? I have a small test DLL(debug mode) that I created a setup project. In my setup project, I included merge modules & policy for vc90_debugcrt_x86.msm, etc. When I install the DLL on my VM, dependency walker still reports that MSVCR90D.DLL cannot be found?
Thanks in advance.
See here.
Preparing a Test Machine To Run a
Debug Executable
Microsoft does not officially support deploying debug runtimes outside of dev/test environments but you can make it work if you need to. Sounds like this is a vanilla test environment installation, though.
Just copy the MSVCR90D.DLL file into the same directory as your own dll. Then both your dll and dependency walker will find the MSVCR90D.DLL file.
You may need a couple of other files like msvcp90d.dll or msvcm90d.dll but dependency walker knows if you need them for your purposes.
MSVCR90D.DLL is the debug version of the Visual Studio Runtime Libraries. Normally, if you're deploying that code, you would build it in Release mode and also provide/install the Visual Studio Runtime Redistributable. As far as I know, the only way to obtain the debug dlls are through a Visual Studio install.
The py2exe utility that converts Python scripts into executable Windows programs seems to have a similar problem here. Maybe the section "Bundling the C runtime DLL" helps you to find the solution.

Resources