I'm trying to create a quick debugger, wherein I can attach my application to a running .net process and execute scripts from there. I'm using C#.
How will I do it?
Thanks :)
You can attach to a process in Visual Studio and use VS tools for debugging. What does your application do that would require it to be attached to other processes outside of VS?
http://msdn.microsoft.com/en-us/library/c6wf8e4z.aspx
Related
I have a legacy solution in C#, .net 1.1 and Visual Studio .NET. My solution consists on many projects. Once I run in debug mode my initial project, then I attach to other processes. When I try to attach to a process, Visual Studio IDE crashes and I need to start IDE again. It's a pain!
Anyone has some idea on how to get rid of this?
I'm not sure if there's a fix, but a way around it is to limit the number of processes you're attaching to.
Start with just connecting to one, then increase the number if stable.
To identify which project is running on each port you can run
IIS6
c:\windows\system32\cscript c:\windows\system32\iisapp.vbs
IIS 7
C:\windows\system32\inetsrv\appcmd list wp
I recently installed DevExpress on my machine, when running it's demos
I found that the it was able to run the project on http://localhost:xxxx.
My question is:
What DevExpress is doing behind the scenes to run a project on localhost without Visual studio?
I found this question, however it only clarifies how can the project "run" manually without Visual Studio. DevExpress is programmatically running the demo project without my manual help.
Any idea? Kind folks?
Consider running the below command
iisexpress /path:c:\myapp\ /port:9090
I have written a windows service application which is installed on my PC. There is a problem with it, so I want to debug that service.
Can you tell me how to debug the windows services?
Please read: http://msdn.microsoft.com/en-us/library/7a50syb3(VS.80).aspx
The easiest way to debug code that you've written as a service in .NET is to separate all the functional code from the service into a separate assembly and then create another project, as a console or WinForms application that uses the separate assembly to run the service code.
If you have Visual Studio on same machine, use it to list the process and attach a debugger to it. You can also use remote debugging but it can be a pain to configure.
The easiest way is to add System.Diagnostics.Debugger.Launch() to the point you want to start debugging. Visual Studio will need to be running as Administrator. When the code is executed, a dialog will pop up asking which instance of Visual Studio you want to use to debug. If you've got Visual Studio already open with the relevant project loaded, choose that one.
I am in the process of learning C#. I downloaded and installed Visual Studio 2010 Express with C#. The problem is it has all these templates that are a little overwhelming at the moment: ASP.NET website, Library, WCF, etc.
I just want to code something very simple that takes input from the Console and outputs to it. I am making do with WCF but that's really inconvenient. It is faster for me to load up ideone.com, type my code there and compile than doing it from own my machine.
Is it even possible to create simple programs like that in C# using VS2010 Express?
Thanks everyone who answered. I installed Visual C# and now I can create console applications. But now the command window closes immediately after it's done doing whatever it's doing. Can I have it output to the IDE like I would with Java on Eclipse or Netbeans?
You can create simple apps by choosing Windows Application (if you want a GUI) or Console Application (if you just want to take input from console as you describe in the question) as project types.
Regarding the question of the console window immediately closing, the quick-and-simple fix for this is to have
Console.ReadLine();
at the end of program execution -- it'll do all it needs to do, then wait for (any) keyboard input before closing the window.
"But now the command window closes immediately after it's done doing whatever it's doing. Can I have it output to the IDE like I would with Java on Eclipse or Netbeans?"
Try running without debug mode (Ctrl+F5 or Shift+F5 or some other binding depending on your keyboard setting). The program will wait for you to press a key to exit.
If you want to output it to the IDE, you could use System.Diagnostics.Trace.Write, which writes to the trace output in the bottom on the IDE. I do not believe there is a built in stdout view in Visual Studio... but it seems like a great idea for a feature...
Are you there, Microsoft?
Visual Studio can be extremely overwhelming. What you should remember is that it's a tool for professionals, ultimately. However, if you want to make a Console app, it's quite simple.
Open Visual Studio
File
New
Project
Other Languages
Visual C#
Windows
Console Application
Done.
Yes, Visual Studio Express is a very good free tool for creating applications. Of course it doesn't have all of the features of Visual Studio, but I use it at home for several reasons.
What you want is the "Console Project" template
I'm developing a simple console application in Visual Studio 2008 and want to run it in the output window inside Visual Studio 2008, instead of having a separate command prompt window come up. Is there a way to do this?
If you run the console app in the post build step it's output will go to the output window. The inability to do this easily has been on of my biggest peeves with VS (any version)
ctrl+F5 seems to "start without debugging" in the debugging menu.
Does it actually have to be a console application? If you make it a WinForms app (even though it doesn't create any GUI elements) you'll get the console output in the Output window. However, you then can't read from console input, and obviously you won't get any output at all if you run from a real command line or in explorer. For simple test applications this may be fine, of course!
The only way I know of is to add it as an external tool and tick the Use output window checkbox when you define the tool.
It is a fairly old question, but as there is no answer marked as solution yet, try the answer given over here: Having the output of a console application in Visual Studio instead of the console