Verify That You Have Access to This Location and Try Again Vs2010

Mar 24th, 2017,07:59 AM

Hello.

3 days ago I migrated from Windows 8 to Windows 10. After that, I accept been facing a problem. When I try to code I receive this error: "Could non re-create "obj\x86\Debug\CARS.exe" to "bin\Debug\CARS.exe". Showtime retry 10 in 1000ms. The process cannot access the file 'bin\Debug\CARS.exe' because it is beingness used past another procedure."

I just exercise non know how to solve this, and so I am looking for help.

Cheers in advance.

Nelson

Mar 24th, 2017,08:34 AM

I've used VS 2010 on several Windows 10 machines so there is no specific incompatibility. That said, I know I'm not alone in having seen a similar effect to yours at times with diverse versions of VS on various OSes. It may be the project rather than the IDE, and then do you run into like issues with other projects? If so so y'all might want to repair VS.

Mar 24th, 2017,08:41 AM

Hi,

To answer the header question... Yes it is. Really, since VS2010 was released long before Windows 10 your question ought to be the opposite way round, however the answer is notwithstanding yeah it is.

As to the problem you lot're having, you lot need to exist sure 'bin\Debug\CARS.exe' is not in employ, this means it'due south not running, you lot're not reading from, or writing to information technology while you're trying to copy information technology. Although the error says some other program information technology could be the bodily programme with which yous're trying to re-create it.

Poppa.

Mar 24th, 2017,08:57 AM

1) Employ the "Clean Solution" option.
2) Close VS
iii) Delete the bin folder... or at least the contents of the bin folder
4) Open up VS, open your project, run it

-tg

Mar 24th, 2017,09:09 AM

I ran into this a few months ago. Information technology was the vshost process locking the exe after a debugging session because it didn't release the handle properly.

Did you do an upgrade or a clean installation of Windows 10? The problem only appeared on machines that been upgraded. The only solution that worked was to wipe the hard deejay, do a make clean install of Windows 10 and then install VS2010. Microsoft couldn't provide any other solution.

Mar 24th, 2017,09:17 AM

Quote Originally Posted past Grant Swinger View Post

I ran into this a few months ago. Information technology was the vshost procedure locking the exe later on a debugging session because it didn't release the handle properly.

I've had lots of issues with that vshost procedure mostly with VS2005 and VS2008 that it reached a point where I always turn that off (for both debug and release builds) in the project properties every bit before long as I create a projection.
Even though I'thou using VS2015 for everything today, by always turning that off I've never had these issues with it since.

That being said, I do accept VS2010 running fine on a couple of Win10 computers (one was upgraded, other was clean install), but I don't take any projects that has vshost turned on either.
Bluntly I don't see whatsoever do good to having that vshost process even run, it only seems to create problems.

Mar 24th, 2017,09:19 AM

Quote Originally Posted by Grant Swinger View Post

Did you exercise an upgrade or a clean installation of Windows 10? The trouble simply appeared on machines that been upgraded. The just solution that worked was to wipe the hard disk, practise a clean install of Windows 10 and then install VS2010. Microsoft couldn't provide any other solution.

Wow... that's pretty farthermost... especially when all that needs to be done is shut VS downwardly, articulate out the bin folder and re-start VS.

-tg

Mar 24th, 2017,x:03 AM

That was the first affair we tried but information technology would just prepare the problem until the next debugging session and then information technology was back once more.

Mar 24th, 2017,11:10 AM

This is a really crazy mutual problem with VS 2010, and a few years agone someone would ask about information technology almost once a week. As far every bit I know, MS never best-selling it equally a bug and no one ever found a reliable solution. I had it happen to 1 of my work projects very frequently, and learned to continue Process Explorer open up and so I could get toss the handle since it took minutes to restart VS.

I've about never seen it reported for later versions of VS, so "upgrade to a new VS" might be the only reliable solution.

Mar 24th, 2017,07:31 PM

Merely at the moment Microsoft seem to exist pushing VS2017, the Community version is free and so why non effort that ?

If yous find information technology works well plenty y'all might consider upgrading to the Ultimate version.

Poppa.

Mar 25th, 2017,07:26 AM

Thanks to all of yous that replied my question.

It seems the problem is solved. I red, I do not remenber where, that renaming the .exe file in the Bin would solve the issue. I did it and, so far, the problem is gone.

On the other hand. information technology also seems that the time to upgrade has arrived.

By the way, I did an upgrade directly from Microsoft site.

Thank you again.

Nelson

Mar 25th, 2017,03:49 PM

Quote Originally Posted by necalabria View Post

Thanks to all of you that replied my question.

Information technology seems the problem is solved.
Nelson

That'south good news, maybe you'd consider marking this thread as resolved.

(Top of this page. find the 'Thread tools' tab)

Poppa.

Mar 26th, 2017,08:23 PM

Hullo Poppa,

When I wrote reply # 11 I marked the thread as resolved.

You can see that in the championship.

Thank y'all.

Nelson

Mar 26th, 2017,11:43 PM

Quote Originally Posted by necalabria View Post

Howdy Poppa,

When I wrote respond # eleven I marked the thread equally resolved.

You can meet that in the title.

Cheers.

Nelson

How exactly did y'all practise that? Did you use the Thread Tools menu? I ask because information technology's normally the instance that subsequent posts include the "[Resolved]" prefix in the title but that seems not to be the case hither.

Mar 27th, 2017,06:38 AM

Quote Originally Posted by necalabria View Post

Hi Poppa,

When I wrote respond # xi I marked the thread every bit resolved.

Y'all can see that in the title.

Thank you.

Nelson

Oh... OK, I wonder why information technology'd not showing as resolved in following posts ? Not even this i, as yet.

Poppa.

Pendleton Hises1939

Verify That You Have Access to This Location and Try Again Vs2010

[RESOLVED] Is windows x uniform with visual studio 2010 ultimate

Re: Is windows 10 compatible with visual studio 2010 ultimate

Re: Is windows x compatible with visual studio 2010 ultimate

Re: Is windows 10 uniform with visual studio 2010 ultimate

Re: Is windows 10 compatible with visual studio 2010 ultimate

Re: Is windows 10 uniform with visual studio 2010 ultimate

Re: Is windows 10 compatible with visual studio 2010 ultimate

Re: Is windows 10 uniform with visual studio 2010 ultimate

Re: Is windows 10 compatible with visual studio 2010 ultimate

Re: Is windows 10 compatible with visual studio 2010 ultimate

Re: Is windows 10 compatible with visual studio 2010 ultimate

Re: Is windows 10 uniform with visual studio 2010 ultimate

Re: Is windows ten compatible with visual studio 2010 ultimate

Re: Is windows 10 compatible with visual studio 2010 ultimate

Re: Is windows 10 uniform with visual studio 2010 ultimate

Posting Permissions

Post a Comment for "Verify That You Have Access to This Location and Try Again Vs2010"