Visual C++ Setup Failed

0 views
Skip to first unread message

Randell Magtoto

unread,
Aug 4, 2024, 10:51:23 PM8/4/24
to pasihouperp
Ihave a Visual Studio 2010 solution with a few projects. I can successfully build with Build -> Build Solution or Build -> Build MyCompany.MyProduct.MyProject. After building I press CTRL+F5 and successfully run the start up project. This works as expected.

After I change a source file, save it and then again build (with either Build -> Build Solution or Build -> Build MyCompany.MyProduct.MyProject) it builds successfully. I am still able to press CTRL+F5 and run the startup project. This again works as expected.


The problem is in the following scenario:After I change a source file, save it and directly press CTRL+F5 then Visual Studio 2010 says BUILD FAILED and there are no errors. And it doesn't start my startup project (of course).


Try repeating the same steps by changing the location where you compile/run. Make sure your new location has less folders to traverse when compared to your old location. A lengthy path to the source code had resulted in a similar issue to me and I overcame it by choosing a shorter path.


I had this problem and had one warning but couldn't find any errors. Eventually I copied the build command from the output window into a command window and ran it manually - it spat out four errors after the warning. I have no idea why this worked.


I was working on a web site project that referenced a library project (in the same solution) when I ran into this issue. Build failed while the editor was highlighting syntax and navigating to the source. Very frustrating.


After cleaning solution, temp files, restarting VS, etc., I ended up excluding the 2 offending files, which allowed the solution to build successfully, then when I included them again everything built correctly.p.s. I later discovered an error in the website's masterpage codebehind (referencing an enum value that had been removed), which was not being displayed as an error. I've had errors in masterpage codebehind cause (apparently) unrelated problems before; I try to remember to check there when a simple solution doesn't present itself.


My issue arose from converting a functional vs2008 project to vs2010. All other projects in the solution came across fine, but this one would build the MIDL portion, then stop and fail. Detailed build setting revealed nothing, so finally I created a whole new project with all files the same. This worked. Then I compared the settings, and finally after changing the various parts to match, I discovered that the converted project had MIDL->General -> "MkTypeLib Compatible" set to blank. This was a valid setting in vs2008 apparently, but in vs2010, it apparently must be set to Yes or No (or inherit).


I had this issue today as well... after changing the verbosity of build to diagnostic like @Jac suggested, i discovered that the problem relies in one my resx files. Apparently, one image was corupted or was too big, i deleted it and it worked!


I faced that problem two days ago. I checked on Windows output and I founded there was a missing reference to VBIDE: Cannot find wrapper assembly for type library VBIDE. I showed all files on the solution explorer, expanded references and I found there was a reference to that assembly. I do not know how that reference came into my project and I was sure I did not need it. I just removed it and everything was fixed.


I am trying to use VS2010's 1-Click Publish feature to deploy a test site from my laptop to my server. I have the firewall turned off on both machines and the MS Deployment Service is up and running on both my laptop and the server.


Error 1 Web deployment task failed.(Remote agent (URL :8172/msdeploy.axd?site=LocationsTest) could not be contacted. Make sure the remote agent service is installed and started on the target computer.)

The requested resource does not exist, or the requested URL is incorrect.

Error details:

Remote agent (URL :8172/msdeploy.axd?site=LocationsTest) could not be contacted. Make sure the remote agent service is installed and started on the target computer.

An unsupported response was received. The response header 'MSDeploy.Response' was '' but 'v1' was expected.

The remote server returned an error: (404) Not Found. 0 0 Test.Web


I've had this one come up on a few occasions after having just successfully deployed a WebApp on a server running IIS 7.5. Obviously since a deployment/publishing was done successfully on the server just before this error came up, there was very little that could have gone wrong on the server setup/configuration (unless the previous successful deployment did something horribly wrong and removed some configuration parameters on the server).


After having rebooted the server, checked that Web Management service and Web Deployment service were running correctly, and verified from cUrl tool that a GET of the MsDeploy.axd was successful there was only one thing left to do. Restart Visual Studio. Magically post restart of VS publish started working again. All on its own. Magical stuff, this Web Deployment :)


After this, everything works fine. Assuming the Web Management Service is setup correctly (mine is configured to accept remote connections, the firewall port was opened, and the user I'm uploading with was added to every single Site that I want to deploy to (using the IIS Manager Permissions icon in each Site node in the IIS Manager)).


We found the issue was because WebDeploy was installed before the Web Management Service feature was enabled on a Windows 2008 server. After Web Management Service is installed, uninstall Web Deploy fully. Then resinstall and make sure all components of the package are selected.


Basically I always install Web Deploy 3 from the Web Platform Installer. This is the first mistake. For some reason this only installs half the stuff you need. If you have installed this, uninstall it and download the Web Deploy installer. Then choose "Complete" install.


This can be the first test to see if you can reach the Web Management service on the server at all.In other words: When chome worked (it responded with a blank page), then you have hole through to the service on the server.


If you are using an SSL certificate you should go into Management Service under the IIS Manager section of Server Manager and stop the service, select the correct certificate and then start the service again. This is what worked for me (I was getting Forbidden message).


I click refresh and it reloads with the empty visual (stuck in a loop). I click continue with autosave off but then i cant save anything, and when i try to manually save it, it shows the screenshot and reloads back to the visual still being there. is there a fix for this?


Do you have any filters associated with the visual that you are trying to delete? I see there are no columns added to the axis, but if there are filters scoped at the sheet level, try to delete the visual associated filters first before deleting the visual.


I pretty much followed the advice above and got it installed. Drivers only first. Then stepped through it piece at a time till I hit NSight Compute. I got the install file for that from -compute then finished out anything left, but did G-force Experience Last.


Do you already have an Nsight compute installed and try to install again from cuda toolkit ?

Anyway, a workaround for this is to download Nsight compute standalone installer from -overview/nsight-compute/get-started#latest which I think you already know.


I have the same issue here.

At first, the CUDA installer asked me to install Visual Studio, then I installed VSCode and Visual Studio Community, but the CUDA installer finally failed to install Nsight Compute.

So, I continued to install the standalone version of Nsight Compute and rebooted my computer, but the CUDA installer showed it failed to install Nsight Compute again, which made no sense because I had installed that application already.


I have been trying for 2 days to install CUDA and all seems to work fine except for the visual studio integration. (i use the latest version of vs2017 community). I have tried reinstalling vs2017, didnt work, i tried installing vs2015 community, didnt work either, i comepletely deleted every cuda related file or visual studio related files (not the projects duh) and installed vs2017 yet again from scratch only for it not to work. I tried printing the log files but i cant get anything meaningful out of them. I searched all around the interned and i cant find any solution. Could someone please help a poor fella out?


Brand new computer. Got the cuda_9.1.85_win10_network. Started it and was told to install Visual Studio. Did that ( a wooping 14GB install ). Tried cuda_9.1.85_win10_network again. It downloaded loads of stuff and failed!?. Turns out it fails on VS integration and deletes everything. Got my hands on cuda_9.1.85_win10 (stand alone) and managed to install it when VS integration was unchecked. But loading the sln files and trying to compile just gives loots of errors. I got it a bit further by copying files from the place the CUDA installer unpacks files ( C:\Users\devtest\AppData\Local\Temp\CUDA ) and into VS support folders. At this point I can compile about 20% of the sample projects (with VS - I will give linux a go before quiting).


I had the same problem and finally I could find a solution. Visual Studio integration failed every time. I tried all possible combinations and nothing worked (Visualstudio 2010, VisualStudio 2017, Cuda 9.1.85, 9.0, 8.0, 7.5). I also tried reinstall windows 10 in all possible ways. Fortunately the method sugested by @oregonduckman and orangesherbet0 worked for me (CUDA 9.1 cannot install due to failed Visual Studio Integration - CUDA Setup and Installation - NVIDIA Developer Forums):


I had the exact same problem, but since I was on a notebook with an Intel GPU and a Nvidia GPU it was sufficient enough to stop all Nvidia Processes and to disable the Nvidia GPU in the device manager. After that I could successfully install the Visual Studio Integration. No software uninstallation or restart required :)

3a8082e126
Reply all
Reply to author
Forward
0 new messages