Hi I recently got a new machine with Windows 10 and the Just in Time debugger is not working for me, like it used to in Windows 7. No error window at all is opened when my program crashes. I'm using Microsoft Visual Studio Community 2017 and I have checked that the Just In Time debugger is installed and that all options are turned on in Tools/Options/Debugging/Just-In-Time. Like it says you should do to enable Just In Time on this page:
Due to some reason I have uninstalled Visual Studio 2005 and trying to reinstall again, but I am getting below error, I tried give folder permissions, and also tried repairing c drive through C:->Properties-> Tools, but nothing helps me, I am still getting same error.
Kindly help me to resolve.
Error 1310. Error writing to file C:\Program Files (x86)\Microsoft Visual Studio 8\SDK\v2.0\QuickStart\aspnet\samples\data\Web.Config.encrypted. Verify that you have access to that directory.
Thanks for help, since it was not working out in any ways, i did the installation by choosing different folder (instead Visual Studio8 i choose as Visual Studio 88). Hope this help other facing this problem.
First of all, I should say that I have successfully installed MSVC 6.0 on my home PC (which is running Windows 10), applied SP6, and it works fine.
I went through exactly the same process on the PC at our church (to try and trace a problem whilst running a MFC program), and the (basic) installation of MSVC 6.0 goes through most of the process and enters the stage where I think the message is something like "Updating your system settings". It never exits this stage. I repeated the installation but got the same result. Has anybody experienced this and/or can suggest what the problem might be ? (The PC is a Lenovo 10GSS18300 Think Centre M700 if that is any help). Many thanks in advance !
MSVC 6.0 ? Because it's the last version that I've got and it works !! When you say 'free', is it REALLY free or on a subscription basis (which, on my usage,I couldn't justify. Microsoft aren't noted for giving things away for 'free' !!). Can you give me the link to the 'free' version then ? Thanks for your reply BTW !!
I downloaded "Visual Studio Community 2017" ( I assume that is what you intended). I installed it and tried to open an existing project by File/Open/Project/navigating to the folder and selecting the .dsw file. However, it returns an error dialog "<Project name>.dsp has been corrupted and cannot be opened". Tried this on other projects and get the same result ! What am I doing wrong ?
P.S. Just discovered that "this a 30 day trial (for evaluation purposes only) Your trial will end on 30th May". Have I installed the wrong product ?
I have now uninstalled Visual Studio Community 2017 and started a re-install - not being familiar with 'workloads' I installed originally without selecting 'Desktop development with C++'. I suspect that this may be why I had problems opening an existing project. I'll follow your advice on registration - thank you !!
Near the bottom of this page, there is a "solution", and I quote
"I always do dism.exe killing to continue installation for this case. It "works" always, but I don't know what is happened next time Today update (15.6.2) hangs again, nugget's update hangs too."
So I found dism.exe in Task Manager, ended the task, and the installer completed. Whew !!
Have now found that I should have included MFC support, so reran installer and selected MFC component. The download completed OK, but the first package to be installed is 'Microsoft.VisualStudio.Graphics.EnableTools' AGAIN !! Killed off dism.exe again, and the installation completed OK. Clearly, this will recur every time I install a new component. Why hasn't Microsoft fixed this bug - it seems to have been going on a while ?? !!
I'm not sure it was there from the beginning or came with one of the updates... but lately VS can't copy DLL to target directory after compilation, because it locked by... VS itself...
I'm on my way to waste time and investigate it, but would be very glad to any info before that...
(No, there is no other instance of VS. No, reset to IIS - it's a web application - does not help. No, it does not happening after all run)
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
Last Visit: 31-Dec-99 18:00 Last Update: 15-Jul-18 14:32