Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
When I try to attach the w3wp.exe process in order to debug asp.net process, a pop-up alerts me that this "can potentially harm your computer".
I just wonder why.
Are you by any chance NOT running visual studio as Administrator? Visual studio needs to be running as Administrator to attach to the ASP.NET worker process without popping up that warning.
EDIT: Looks like this issue is answered in this SO post
IIRC, some older trojans/viruses used debug attachment as a mean to hook into other programs/services.
Nowadays you get a warning. Focus here is not on the words 'harm your computer'. It asks you to check if the process listed is what you'd expect. Imagine that popping asking to debug chrome.exe or skype.exe when you was just idling. That would make me freak out for sure.
Related
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 7 years ago.
Improve this question
Today I run into a strange error.
When I start my program without Visual studio 2010 Express, start to running, but the gui not appear, and inpossible do stop it in task managger.
But if I run it in Visual studio, it work without any problem.
It do it with my all c# program,even what I write years before, but not any other program.
Tried to check, if a virus do it, but it can't find anything.
Operting system is Windows 7
It can be antivirus who stops execution of your application. Try to turn off it.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 6 years ago.
Improve this question
I'm trying to run my .exe file for a console app I made. When I go to /bin/debug/~~~.exe it won't run. However, it still manages to build from inside Visual Studio.
How can I get this to work?
I have experienced the same situation, my exe is just a simple Hello World console. After a lot of trials and errors, I figured out it is just my antivirus (Avast Free Antivirus) pausing it. Whitelisting my exe solves the problem. Hope it is your case too.
Its my antivirus which is blocking my application. After uninstalling everything is working properly.
Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 8 years ago.
Improve this question
i am currently developing an alternate shell for windows( to be replaced with explorer).
the problem is the program runs fine when run as a normal executable.
but when i set it as default shell for windows and re-log in into my user account the program runs for a few seconds and then it force closes.
is there anything i can do what might be going wrong?
BTW working on c# wpf.
You are always debugging a compiled program.
However, when you run it from Visual Studio, the debugger is automatically attached (so you can see exceptions, set breakpoints, etc).
You can do the same thing to an already running process by using the "Attach to Process" option in the "Debug" menu.
Other things to try:
Add try/catch blocks around areas that can blow up
Add logging, especially to the try/catch blocks
Put a "sleep" at startup if the program closes before you can attach the debugger.
Also, from #ScottChamberlin, you can directly ask that a debugger be attached from the running executable via System.Diagnostics.Debugger.Launch().
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I ran into a weird problem on a Windows XP system. My local service app logs its diagnostic messages into the Windows Event Log, so at some point those messages stopped being logged. I thought that the issue was in my code, but then I discovered that other processes can't log messages either.
So I was wondering, is there a limit on the Windows Event Log size?
PS. I guess I need to write this specifically -- I need to know/change the size from a command line or an API.
The limit and behavior depends on the log configuration. Please check in the log properties if "When maximum log size is reached" is set to "Do not overwrite events". If so, the events will not be logged. You can set the limit there as well.
UPDATE: It turns out the question is how to check the behavior described above programmatically. Please have a look at EventLog.OverflowAction, EventLog.MaximumKilobytes, and EventLog.MinimumRetentionDays properties, that should be enough.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
Currently i've tried the antivirus dll from this site:
http://antivirusscanner.codeplex.com/documentation
After installing this package from nuget i ran the code to scan (and clean) a file.
I got a 'virusnotfound' answer back, but that wasn't what i expected: I had no single antivirus program installed.
Does anyone know if this package contains some function to check if an antivirus program is installed? I want to know for sure if the code works fine.
To be fair, the response it correct: it didn't find a virus. That doesn't say whether or not it had the tools to look very hard. There are only 3 responses:
VirusNotFound
VirusFound
FileNotExist
of those, it sounds like VirusNotFound is the closest.
To check, you could perhaps use EICAR.