.NET And .NET MVC Application Debugging Available In MonoDevelop?
Nov 2, 2010
I've tried to debug sample ASP.NET and ASP.NET MVC applications in MonoDevelop 2.4 (on Mono 2.8 on Windows 7) but breakpoints doesn't work.If debugging MVC Application MonoDevelop prints the following into the output:
Mono.Debugger.Soft.VMDisconnectedException: An exception of type "Mono.Debugger.Soft.VMDisconnectedException" thrown.
at Mono.Debugger.Soft.Connection.SendReceive(CommandSet command_set, Int32 command, PacketWriter packet)
at Mono.Debugger.Soft.Connection.Type_GetInfo(Int64 id)
[code]...
I have a vb.net web application in visual web developer 2008 with a dll file and i need to debug a method in that dll. I also have project source files for the dll file itself. How could i make the web application use the source instead of the dll file so that i'd be able to debug it? I've tried debugging the dll project itself, but it's not a very good solution, because it seems the dll depends on the web application settings and data and it would simply be too much work to get it working.
I'm hoping someone else has experienced this and has some suggestions. The actual dcms process goes pretty quickly, but in between projects it hangs after printing: Building: XXX.YYY.ZZZ (Debug) After a few minutes (been 10 so far on this current run), it jumps to:
Then hangs again for another few minutes. This is a sln file with 29 csproj projects in it that was originally created in Visual Studio 2010. I'm wondering if there is a better way to set this up - potentially a native MD file format?
I installed monodevelop, and so far everything is working fine.I was just wondering if you had any tips or must dos for any person who is using monodevelop for c# / asp.net programming Feel free to recommend open or closed source tools that are useful with mono develop Settings I should change / modify to get a better coding experience?
We are trying to add a new page to a running web application. such that a new dll and aspx file are being added. I've setup break points in the code file and Built the application transfering the dll to the remote machine bin file and the aspx page to a folder within the web application. Note this folder is not in the same folder hierarchy as it built in. I'm not sure if thats the problem. Basically we are appending new functionality to a web application.I've copied the correct Remote Debug Monitor to the server and have it running.
When publishing my web application and then running it will return the error
"Could not load file or assembly 'BaseApplicationName' or one of its dependencies. An attempt was made to load a program with an incorrect format."
However if I run the application through debugging (f5) it runs correctly.
I guess what it comes down to is
what differences are there when running an application through debugging vs publishing it that would cause a problem like this?
When publising I have it set to delete all existing.
History of how it started... I added the 32 bit Oracle.DataAccess dll to my 64 bit system. It would not work and crash giving the same error as above but with the Oracle.DataAccess name instead of the baseApplicationName. I have since removed all references to it and removed the dll to try and get it to run without it once again.
I have two systems (System A & System B) both are windows xp.
System A is 32 bit operating system with more Memory so I Installed Visual studio here.
System B is 16 bit with low memory and some peripheral(Finger Print Reader, Thermal Printer) attached.
Now I need to develop a application for System B. Peripherals are attached with system B Only so i need to debug the application which is running in system B. But I cannot install visual studio in system B. Now how can I do that?
I'm having a hell of a time trying to debug things. Basically I want to step through each line of code to see whats happening. But when I try to step to the next line of code, 9 times out of 10 it just finishes all execution instantly without letting me step.
For example if I set a breakpoint in the thread code, that breakpoint gets hit, and I might be able to step to the next line or 2 of code, but after that the next step just jumps to the end of everything as If I had pressed F5 (continue). I assume this is happening because the context gets switched from my current thread to the main thread (or some other thread), and Visual Studio gets confused and just finishes execution, ignoring my breakpoints.
I know about the Threads window, and I have tried many different combinations of freezing and flagging different threads, but nothing accomplishes what I want. I basically want to just keep hitting F10, and step through EVERY LINE OF CODE, regardless of what thread it's in. Im surprised this isnt the default behavior.
I have a server running Windows Server 2003 R2 Standard Edition (Service Pack2) and our IIS server is hosting about 20 different asp.net websites. I've never noticed this in the past, but when I debug an application and it stops at a breakpoint, the other websites hang as well. If I try to go to any of the other websites, then I just get a while page that's loading until i pass the breakpoint or I stop debugging.Does this have anything to do with application pools and if so, how do i fix it? Or if it does not, any ideas on how to fix this issue? I find myself debugging my apps often and I can't bring down all other applications when I do it.
I got a probem when debugging web application using VS 2008. Here is the situation:I marked two breakpoints, one in the Page_Load event and the other on the button click event. When the debugger hit the breakpoint in the page_load event, everything was fine but when it hit the breakpoint in the button click event, VS 2008 suddenly stopped debugging. It seemed that the IIS worker process was terminated.I really don't understand this situation.
My new office project is based on an MVP design and is in VB.NET (.NET 3.5), using multiple libraries (like EntLib, internal corporate framework, etc.). The number of DLLs used as references is so huge (almost 50) that when I try to build/debug the application in VS2008, it takes almost 3-4 minutes to get the website running successfully.Wanted to know if there are any settings/areas which upon some modifications can help me reduce the build time? and what exactly can be the major reasons behind this long loading duration?
Whenever I stop debugging an ASP.NET IIS web application it seems to take very long before VS2010 becomes responsive again (2 or 3 minutes). This happens when I close Internet Explorer 9 (which stops the debugging session), stop debugging in VS (which closes the browser) or when I detach the debugger from the debugging menu (which leaves the browser open).
My CPU time for devenv.exe goes up to 25% during this period of time. I use the professional edition (no intellitrace). Starting without debugging performs ok when I close the browser. I have some add-ins and extensions installed like TestDriven.NET, Resharper, PowerCommands, Productivity Power Tools, VisualSVN,...
I get this error when I hit F5 in VS 2008. I have checked that Windows authentication is enabled on the site and it is. I can mannully attach the debugger to the IIS process and it works. What could be wrong? I have tried alot of things without success.
I'm trying to debug my web application on my localhost machine in Visual Studio 2010 and I keep getting this error: "unable to start debugging on web server. The Microsoft Visual Studio remote debugging monitor(MSVSMON.exe) does not appear to be running on the remote computer."
Is there a way I can turn this off as I'm not trying to make any attempts debugging remotely.
I am running Visual Studio 2010 (as Admin), IIS 7 on Windows 7 x64. I am able to run the ASP.NET web site in IIS 7 without debugging just fine, but when I press F5 to debug it, I get: Unable to start debugging on the web server. Could not start ASP.NET debugging. More information may be available by starting the project without debugging. Unfortunately the help link is not helping me much and leads down a heck of a large tree of things. I checked the following:
Security requirements — I don't recall having to do anything special before. The worker process in IIS7 is w3wp.exe. It says that if it's running as ASPNET or NETWORK SERVICE I must have Administrator privileges to debug it. How do I find out if I need to change something here? Web site Property Pages > Start Options > Debuggers > ASP.NET is checked. Use custom server is set to the URL of the site (which works fine without debugging). Debugging is enabled in web.config. Application is using ASP.NET 3.5 (I want to move to 4.0 eventually but I have some migration to deal with). Application pool: Classing .NET AppPool (also tried DefaultAppPool). Surely it shouldn't be that hard to install IIS, VS, create a web site, and start testing it?
In our ASP.NET application we perform some initializations upon the Application Start event.When the application is started in visual Studio 2010 with 'Debug->Start new instance' the ASP.NET Development server does not start new, and my Application's Start event is not fired.My workaround is to manually stop the development server - is there a setting to force this automatically?
my client/iis (not sure which) usually times out after about 30s - 1 minute while im debugging (stepping through code) which not only causes me to lose my spot and have to start over (usually stepping faster, making more mistakes) but the IIS Debug session closes completely and I have to warm up the entire session again.
What's the best way to get more time out of a debugging session?
Debugging a vanilla 3.5 Web Site (not app) on IIS 7.5 Classic Pipeline
I tried to running a website in debug more (F5), and I get the following error message. Note, that I am using a local IIS 7 server on windows 7 64 bit machine.
I have an SMTP contact form here URL...contact that is just not working. I have checked twice with my Web hosting service about SMTP credentials and all is fine. I have asked three other people to check my SMTP code and each tells me the code works on their servers (gmail, for example).I have started to debug my code and get an unrelated JS error which, I am told by one JS top dog, is irrelevant to the form problem I have.
I assume, therefore, that the problem lies deep in the code. In order to debug it, do I just select each file from App_Code, bin, Scripts, etc, - the whole Solution Explorer - and select Debug?
Yesterday I've installed IE8 but now my debugging and breakpoints does not work in VS 2005! How can I make it work again? Is it a special browser setting?
First of all, this is my first attempt at a silverlight app and it's a prototype. I have a pre-existing solution with multiple projects. One of those projects is a web portal that has a services directory and publish a .asmx. I added the silverlight app to my solution.When I run the silverlight prototype, it gives me the message: "The silverlight project you are about to debug uses web services. Calls to the web service will fail unless the silverlight project is hosted in and launched from the same web project that contains the web service." That's fine. How do I do that? When I run the silverlight app directly, it runs in the browser as
"C://file/.../PrototypeTestPage.html"
I tried taking that HTML file and adding it to my portal and then navigating to the HTML file. That just gives me a blank page. After the page loads, the browser shows a "Waiting for localhost..." as if it's making the service calls, but my breakpoints on the service calls aren't being called. Can someone give me some pointers?
