After upgrading to the latest version of TortoiseSVN (1.5.2.13595), it's context menu is no longer available.
When attempting to run it manually, I get this error:
The application has failed to start because its side-by-side configuration is incorrect.
Please see the application event log for more detail
The application log shows this
Activation context generation failed for "C:\Program Files\TortoiseSVN\bin\TortoiseSVN.dll".
Dependent Assembly Microsoft.VC90.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.30411.0" could not be found.
Please use sxstrace.exe for detailed diagnosis.
I remembered I'd seen this thing before just after posting to SO
It seems that later versions of TortoiseSVN are built with Visual Studio 2008 SP1 (hence the 9.0.30411.0 build number)
Installing the VC2008 SP1 Redistributable fixes it
Confirmed working on windows 7 x64.
Related
I've downloaded a straightforward VS 2012 solution and for some reason am having trouble with the references in it-- they're all marked with yellow exclamation points, even core .Net libraries.
This isn't a problem in any of my other VS 2012 projects. I've scrubbed and redownloaded the solution several times, each with the same result.
I'm using VS 2012 Professional, update 3, and I have the .Net 4.5 runtime installed. So I think I'm caught up on the latest platform and tools.
I updated all the NuGet packages in the solution but that didn't help. Would anyone know what I can look at to see where the problem is? (I downloaded this same solution on another box and have no problems whatsoever. Both machines are running Windows 7.)
Popped open the Solution and got the following errors:
Warning 2 The command ""C:\****************\Downloads\PluralsightSpaJumpStartFinal-master\PluralsightSpaJumpStartFinal-master\.nuget\nuget.exe" install "C:\*************\PluralsightSpaJumpStartFinal-master\PluralsightSpaJumpStartFinal-master\SPAJumpStart\packages.config" -source "" -RequireConsent -o "C:***************\PluralsightSpaJumpStartFinal-master\PluralsightSpaJumpStartFinal-master\packages"" exited with code 1. SPAJumpStart
Warning 1 Package restore is disabled by default. To give consent, open the Visual Studio Options dialog, click on Package Manager node and check 'Allow NuGet to download missing packages during build.' You can also give consent by setting the environment variable 'EnableNuGetPackageRestore' to 'true'. SPAJumpStart
Looks like the references are tied into a custom nuget package, including the normal .net 4.5 references. Enabling the 'EnableNuGetPackageRestore' option should fix the issue.
Yeah, a question regarding this error exists. But I think it's quite different situation from the one the OP was in.
I just created a MFC application in VC++ 2008 (pro version) and compiled it. The compilation failed because of the error
RC2176 : old DIB in res\MyApp.ico; pass it through SDKPAINT
I must've missed something because VC++ created the icon that is not compiling. Any clue would be appreciated.
UPDATE: I forgot about this issue for a while. I fixed the problem by following solution to this question - Can't open resource editor in VC++ 2008
Answered already in the linked question: error RC2176 : old DIB in res\icon3.ico; pass it through SDKPAINT?
If you would install and integrate a more recent (same or later release date than VS 2008) SDK with VS 2005, that also resolves it. You can also go to C:\Program Files\Microsoft Visual Studio 8\VC\bin (or your equivalent of the path) and replace the files rcdll.dll and rc.exe with the ones from a more recent VS, WDK or SDK.
Side-note: the version of rcdll.dll and rc.exe must match, that is you need to copy both at once from your source (be it VS, WDK or SDK). For me any version starting with 6.0 or 6.1 worked. That's any version starting from the compilers that accompanied the Vista SDKs and VS versions or later.
Did you install Service Pack 1? Also, if you install a newer Windows SDK and use it in your environment, this could very well cause a conflict of some kind.
This is a build server running Cruise control version 1.6.7981.1.
I am basically running a test by pointing an existing (seldom used CC build) to our new TFS 2010 server.
This fails with the error listed in the title.
I am clearly missing a step or two...
I assume that CC must be using TF.exe for source control access? And it must be using the 2008 version. And the update adjusts this somehow? Or performs some other update? Maybe I can do whatever the update is doing myself? Or configure CC to use the 2010 version of TF.exe?
Maybe it's just a question of installing the 2010 client tools (and hopefully this is backwards compaitble). I am trying that next.
I don't know much about CC but the forwards compatibility update is for Team Explorer, which contains a subset of the VS IDE. There are 2 versions one for 2005 and one for 2008. I'd check in "Add remove programs" to see which version is installed. You'll need to make sure that either VS 2005 SP1 or VS 2008 SP1 is installed (depending on which version of Team Explorer is installed) before installing the update.
I am trying to deploy a Visual C++ application (developed with Microsoft Visual Studio 2008) using a Setup and Deployment Project. After installation, users on some target computers get the following error message after launching the application executable: “This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix the problem.” Another user after installation could run the application properly. I cannot find the root cause of this problem, despite spending several hours on the Visual Studio help files and online forums (most postings date back to 2006). Does anyone at Stack Overflow have a suggestion? Thanks in advance. Additional details appear below.
The application uses FLTK 1.1.9 for a GUI library, as well as some Boost 1.39 libraries (regex, lexical_cast, date_time, math).
I made sure I am trying to deploy the release version (not the debug version) of the application. The Runtime library in the Code Generation settings is Multi-threaded DLL (/MD).
The dependency walker of myapp.exe lists the following DLLs: wsock32.dll, comctl32.dll, kernel32.dll, user32.dll, gdi32.dll, shell32.dll, ole32.dll, mvcp90.dll, msvcr90.dll.
In the Setup and Deployment Project, I add the following DLLs to the File System on Target Machine: fltkdlld.dll, and a folder named Microsoft.VC90.CRT with msvcm90.dll, msvcp90.dll, mcvcr90.dll and Microsoft.VC90.CRT.manifest.
The installation process on the target computers getting the error message requires having the .Net Framework 3.5 installed first.
Any suggestion? Thanks in advance!
Add the Visual C++ Redistributable to your Deployment project and be sure to run Setup.exe instead of the MSI when installing. This will invoke the VCRedist bootstrapper to ensure your PC has those pieces before installing your app.
Dependency Walker only shows static (link time) dependencies - it cannot possibly know about dynamic dependencies such as COM objects.
I had a similar problem after the ATL security updates last year. My app needed a later version of the C++ runtime libraries than the deployment project included.
Try running Windows Update on the target machines after installation, or download and install the latest (28 July 2009) C++ redistributable package directly.
http://support.microsoft.com/?kbid=973551
That solved the problem for me. I haven't fixed the deployment project yet though.
This is the error Dependency Walker gives me on an executable that I am building with VC++ 2005 Express Edition. When trying to run the .exe, I get:
This application has failed to start because the application configuration
is incorrect. Reinstalling the application may fix this problem.
(I am new to the manifest/SxS/etc. way of doing things post VC++ 2003.)
EDIT:
I am running on the same machine I am building the .exe with. In Event Viewer, I have the unhelpful:
Faulting application blah.exe, version 0.0.0.0, faulting module blah.exe,
version 0.0.0.0, fault address 0x004239b0.
Open the properties sheet for your project, go to the Configuration Properties -> C/C++ -> Code Generation page, and change the Runtime Library selection to /MT or /MTd so that your project does not use the DLL runtime libraries.
The C/C++ DLL runtimes used by VS2003 and up are not automatically distributed with the latest version of the OS and are a real pain to install and get working without this kind of problem. statically link the c-runtime and just avoid the total mess that is manifests and version specific runtime dlls.
I've had this problem. The solution has two steps:
1. Compile your program in "Release" mode instead of "Debug" mode (there's usually a combo-box in the toolbar)
2. Download from Microsoft their Redistributable Package of runtime components. Make sure to download the x86 edition for 32-bit computers and the x64 edition for 64-bit computers/OSes. Install this package on the target computer, and your application should run fine
P.S. This is a SxS thing
P.P.S. Alternatively, use a different compiler (like GCC, for example with Dev-Cpp) to compile your program's source, and your headaches will disappear.
Sorry to bump an old question, but I was able to get around this exact issue and thought I'd post a solution in case someone else needs it...
Even after installing Microsoft's redistributable DLLs I was getting this error, the fix was to copy the
C:\Program Files\Microsoft Visual Studio 8\VC\redist\x86\Microsoft.VC80.CRT
folder into the application's directory on the target PC. After that, no more problems.
BTW, the DLL that was giving me issues was a 3rd-party DLL that had never had problems before on over 100 other computers... go figure.
Run Event Viewer: it'll have more information.
Probably you've attempted to run your program on a machine that doesn't have the VC redistributables installed, or you're attempting to run a debug build on a machine that doesn't have Visual Studio installed (the debug libraries aren't redistributable).
I have had the same issue with VS 2008-built debug binaries on other winxp sp3 machines.
I first tried installing the client machine with vc redist package,as it seemed sensible. Annoyingly, it didn't work.
I tried copying all the dependent dlls to the application's directory - still didn't work
After being struck over this issue for hours, I found that the latest VS builds require manifests and policies to link with the dlls. After copying them into their respective "C:\WINDOWS\WinSxS\" folders, I got it working.
The problem was caused due to the fact that the vc redist package did not install debug versions of dlls, they somehow thought its up to the programmer to figure out.