-1
Suddenly my application started giving this error:
This started this week, along with a problem I’m trying to solve in another post. I’m beginning to think they have correlation. This gives, give ok and give F5 again works, IE, to run my application by VS2013, I have to press F5 twice. The first one is a mistake and then the second one works. Has anyone been there and want to share? On hold.
3
I disabled the Enabled Visual Studio hosting process, rode. How it generated a Warnings of the visual, I returned to enable. I drove without the debug and when I returned everything as it was before, I no longer gave the problem. Including the problem I reported in another post. I ran 4 times in a row and did not give more the problem. Zipei and already sent to the homol of the company. Anyway I thank all.
Browser other questions tagged c# visual-studio
You are not signed in. Login or sign up in order to post.
Only with this information I can not help, but certainly has to do with those things that I say to everyone and people ignore. People do the simple thing too, they don’t test all the possibilities, but it seems to work. One day the problem starts to appear because the code was wrong. In this specific case it is likely that some file has been opened and not closed. There’s the right way to handle this, but I see an insistence on doing it the wrong way. Obviously I could only affirm with certainty and give more details if I had sufficient details in the question.
– Maniero
I disabled the
Enabled Visual Studio hosting process, rode. How it generated aWarningsof the visual, I returned to enable. I drove without the debug and when I returned everything as it was before, did not give more the problem. Including the problem I reported in another post. I ran 4 times in a row and did not give the problem anymore. Zipei and already sent to the homol of the company. Anyway I thank you all.– pnet
Before you negativize or imagine that the code is wrong, notice that the error is one released by Visual Studio. Look at the title and style of the window, it is not an exception launched by the AP application, possibly it is not an error of the AP code. If you usually code in C# and use Visual Studio, you should notice the difference. @pnet, it is possible that Visual Studio was not able to overwrite a file or delete a directory during build; maybe the application was already running or a window of the Windows command prompt was occupying the directory.
– Caffé
I already suffered with this type of instability in Visual Studio (the application once compiled worked perfectly) and I decided to reorganize some reference in the project... Unfortunately it’s been many years and I can’t remember exactly what it was - I remember it was a project that used a lot of Activex... See here as several people have had similar problems for several different causes.
– Caffé
@Caffe, that could be it. Because when running the application, after all it should close everything, however, even though the application is finished, still the visual running. I have to go manually and Kill in the VS(when it should be automatic):
Application.Current.Shutdown();This is the command I give.– pnet