I'm running my .NET 4.0 (C#) project in debug mode after I start VS2013. It runs just fine.
The second time I start it from VS, I get the Dialog box that says "Error while trying to run project: Unable to start program C:\path\to\file.exe"
The process is still alive in the Taskmanager when I dismiss the dialog box.
From Windows Explorer, I can run the program just fine. And after closing it, the process is gone too from the Task Manager.
A rebuild doesn't help.
Is this a common problem with a known solution?
I had an issue similar to this and I had to clear the component cache instruction can be found Here.
Hope this helps.
For my case, it cause by Platform target, you could force choose it to x86 or x64 which your project is:
Each Project's Properties > Build > Platform target
As I pointed out also here, the only solution that worked for me was to disable the ConEmu integration:
ConEmu → Settings → Integration → Default term → disable Force ConEmu as default terminal for console applications
Some users reported that it was enough for them to disable the Aggressive mode in that same settings tab; that wasn't the case for me though.
The topic is old, but this might help someone else.
So in my case I made a file in Visual Studio with .cp extension (accidentally deleted the last 'p') this made visual studio just "include" the the file and not mark it as a compilation unit, thus not compiling it, I looked the *.vcxproj file in a text editor and found out about this, so if you open the project file in a notepad or something just find your file at the bottom usually and change from <Item .../> to <ClCompile .../>
I was getting similar errors. I just had to restart visual studio. Sometime couple times a day.
I had a similar error and resolved it by cleaning the solution. Right-click the solution name in Solution Explorer and choose Clean Solution.
I found a solution here:
Please check "Use Managed Compatibility Mode" under Tools|->Options->Debugging->General.
I'm Brazilian, I don't speak English very well. I did this translation on google translator.
I know the topic is old, but it can still help someone.
I had this same problem in the following situation, I have a dual boot computer (linux debian 11 and windows 10). Inside debian, on my NTFS D disk, I created a folder to perform programming tests. After accessing that same folder with windows, I created a new project in visual studio inside that same folder that I had created in linux. The creation of the project went without problems, however when I tried to run the project (F5), I received the same error from this topic. I tried all the solutions I found on the internet, and nothing worked. I gave all permissions to my admin user and it still didn't work. Then I realized that even going straight to the folder where the application's executable was and clicking directly on it, I still received the access denied error message. So, I took the project out of the folder I had created in linux, and it worked. So, what I could conclude, is that because the folder where my project was was created in linux, for some reason, my windows didn't trust this folder, so it didn't allow running executables from inside that folder, even this one executable having been created by visual studio from within windows.
Just simply create a folder name as "projects" in c drive and copy paste the newly created project in it. Run the project by doing clean & Build or Rebuild method . It will work
open the folder which contains the solution in visual studio.
again, open your *.sln file by double clicking it inside the solution explore once opened try running the solution or rebuild the solution. once rebuild gets completed, it will open without error from next time.
My way of solving the error : error while trying to load project : Unable to start program and c:\Path\to\file.exe was simply by
First restart Visual Studio
Click the build icon
Select the rebuild option
Run the Program or Debug the Program
This was a weird one. Going to put what happened to me here because it might happen to someone else. Everything was fine with the app until suddenly after some fairly insignificant code changes I suddenly started getting this error. Visual Studio was compiling the executable just fine. But, the moment I tried to run it (either from Visual Studio or directly) the executable file would be automatically deleted right out of the Debug folder. Super odd--never seen anything like it. I began to get suspicious that perhaps an anti-virus or the OS was somehow identifying a checksum or some signature in the executable as "dangerous". Or perhaps some obscure compilation bug was corrupting the executable. So on a hunch I made another innocuous change (added a couple of lines of code to color code some text in a rich text box) and the problem went away.
While trying to debug an asp.net website in visual studio 2013 professional I am having a weird issue. The website is simple but uses flat files and folder structure and files in it for performing some operations. There are two important folder in this website that contains 100 thousands of files and images. When I try to start debugging and do not remove files from these two folder then VS crashes and restart, but if I remove files then VS proceeds normally. The files in these folders are csv, txt and image files. What I can understand is that VS goes through all these folders and files before starting the debugger, hence somehow I need to tell VS to not to consider these folders. I am not able to find anything related to it. Please help. Thanks in advance.
Perhaps take a look at your Event Viewer first and see if you can find anything regarding VS crash.
Also you can try running Visual Studio from the command line devenv.exe /log and then load your solution. If crash still happens, then go take a look at following file %APPDATA%\Microsoft\VisualStudio\<version>\ActivityLog.xml. Perhaps you would find some more details about the crash.
If you happen to be using ReSharper, you might want to disable it and see if that would make any difference. ReSharper likes to index source files in the background which could lead to some usability issue in VS.
Answering for anybody who faces similar problem.
For some reason I dont know why, when starting degugging visual studio was scanning each and every folder, even the folders which doesnt contained any code file, this was making VS very slow due to very high number of files and out of memory exception was being thrown. Since in my case these folders doesnt contained any code file, but still were needed to run the application, I made them hidden from window explorer. This solved the problem as now vs ignores them, while still the program can output report and read reports from these hidden folders.
I kinda accidently deleted a huge project I started years ago and have been working on it several days per week since.
I had 2 backups. A DVD backup and an External HDD backup. The external HDD has failed, and for some reason the damn DVD cannot be read anymore. The DVD looks to be in perfect condition, but will not work in any PC I put it in.
I've downloaded some free C# programs to help me get back my source code (I still have the app installed). So far, DotPeek seems to be the easiest to work with for me. But this project is so big, there's almost 3,000 class files and I can't just copy paste into a new project. It'll take me years!
How can I convert this back into a Visual Studio Solution/Project?
I am using DotPeek 1.2 To create a visual studio project you can just right click on the Assembly in Assembly Explorer and click Export to Project...
When I am trying to debug (F5) in visual studio the compile hits 100% and sits there and takes forever to start my program that I want to debug. Also when the program does start it takes just as long for the program to close and the Visual Studio to start responding. Does anyone know why this happens?
Project is C# wpf, I use to have a silverlight project that did the same thing. I moved all the code to a new project and now my silverlight project works better now.
No special debug option, the same options that come with a new project.
The project is on the local C drive hooked up to TFS 2010.
No Static Analysis or ReSharper that I know of.
My Solution has 14 projects in it. 1 wpf and the rest are dll's and tool exe's.
No Anti-malware, and I disabled antivirus just to make sure it wasn't eating my lunch.
I unplugged my network cable and that did not help any of the network timeouts.
Disable any symbol servers Did not help.
I have found out that if you delete the .SUO file that things get fast it has been removed. It is next to your .sln file. My .suo file was 4.5 mb.
From Google all I can find is that the .suo file is some kind of user settings file but doesn't seem to do any harm when deleted, it just gets recreated.
Found that when doing an import on settings you can get your .suo file to go up in size... the size of the .suo file might not be the issue however a corrupted one might be the issue. I imported setting and made my .suo file go up to 5.7mb and my compile works ok, I deleted it however again because I don't want it to get corrupted.
I'm not really sure how to dig out this question.
What I want, is to create an image file that has my C# program, user manual and video tutorials in it. When the CD already started there will be a pop up form of choices which contains Install Program, View User Manual or View Video Tutorials. How can I do that?
It's similar when you're installing the Visual Studio 2008 or 2010.
Sorry for the title.
I don't know what tags should I put here.
If you put a file called autorun.inf onto a CD, you can have that CD launch a program when it's inserted. From here, you can create a program that contains the menu you'd like, so that when the user inserts the CD your menu pops up. It's not nearly as hard as it may seem.
I believe that you need two files: setup.exe (your program) and autorun.inf (a text file that tells windows which program to run when you put the disk in)
http://en.wikipedia.org/wiki/Autorun.inf
The autorun.inf file should have this text:
[autorun]
open=setup.exe
icon=setup.exe,0
label=My install CD