When I ran Vista (x64) Prem with IIS7 and VS2008 sp1, I could press F5 and start debugging a web application and the debugge would run as long as I needed. I got a new PC that has Win 7 (x64). Now, the debugger will run 30-60 seconds and then quits. The web application still runs but the debugger shows that it is not in debug mode and the breakpoints are no longer hit. I know you can attach to the w3wp process and debug that way, but has anyone found a way to keep the debugger running for as long as you need when you press F5??
Debug-Start Debugging/Debug-StartWithoutDebugging OR Project ASP.Net Configuration launches Dreamweaver. It started lastnight, I had both Deamweaver and VWD 2008 express open at the same time - (I was looking at JQuery in the Microsoft and Dreamweaver enviroments simultaniously). After the first tie this happened, I closed down Dreamweaver (CS3) and it opened when I tried to run my VWD project. I reinstalled VWD 2008 express, IIS and disabled Dreamweaver (renamed the exe). Dreamweaver still came up.
I have deployed a web service on my development machine and i am connecting it through my asp.net application, both web service and asp.net application are on same machine but web service is hosted on IIS.
I have 2 sollutions (1 CMS, 1 Customer specific with controls). The customer controls are coppied (with xcopy) to the CMS location. In the web.config of the CMS the specific controls are registered.The controls are useing functions from the CMS dll as well.How can I debug those two solutions as it where only one? I tried to start the CMS in debug mode with breakpoints in de CMS and customer controls, in this case only the breakpoints in the CMS are used. If I run the customer controls in debug mode only the braekpoint in this solution are used.The CMS is running on my local IIS 7.
I am using VS2010 and am working on an ASP.NET web application for .net 4.0.
I have created a file called StringUtilities.js and placed it in a subfolder of my application called Scripts.
The entire content of the file is listed here:
In one of my .aspx pages I have the following code:
On a button's "OnClientClick" (for example) I call the method encodeText() and everything works fine.
Today I added the method updateImage() which calls StringUtilities.js - updateAttribute() method, also added today.
If I open that unit in VS2010 and place a break point in the source code for the new method it turns white and says:
"The breakpoint will not currently be hit. No symbols have been loaded for this document.".
What gets even stranger (this is so hard to exaplain)....
Before today I did not have the method updateAttribute() in that .js file. So even though my source editor is showing all of my new source code changes, if I trace the previous method that did exists - htmlEncode(), the trace lines in the editor are highlighting where the lines "used" to be. which is near the top of that file as if my new code was not there.
I have VWD Express and I can't debug lower layer methods in the application the debugger doesn't step into breakpoints that are set in these layers. what do I do? I need to debug lower layer assemblies most of the time.
I have vs 2003 & 2010 on same machine. But my application is in asp.net 1.1 so I have to work on VS 2003. (I dont have to migrate to 4.0).
I have followed this link http://msdn.microsoft.com/en-us/library/aa239576(v=vs.60).aspx but still it is not working.I put a break point on page load of my first login page. when I hit F5, the control comes to visual studio and make that line yellow but stays for few seconds only and then leave the contol and visual studio automatically.I'm not able to debug it. Don't know what the problem is.
I am developping an MVC3 RC2 application and just after hitting F5 on my asp web application, I am getting this error message program ' w3wp.exe: Managed (v4.0.30319)' has exited with code -2 (0xfffffffe).So I am totally unable to debug my application
The default ASP.NET web server that launches from within Visual Studio (Casini) is a little buggy on my development machine, so I like to publish to a local IIS instance on my dev machine and look at the web application there. However, I'm not automatically in "Debug Mode" when I launch the application this way.
I know that VS 2010 has an "Attach to Process" debug feature, but I'm not sure exactly how to use it. What do I need to do to be able to debug a local IIS ASP.NET web application from within Visual Studio? Specifically:
What settings do I need to change in the configuration of my web application?
What "Package/Publish Settings" do I need to change?
Is there anything I need to change in IIS?
Is there anything special I need to do in the "Attach to Process" screen?
Background Information: I'm running Visual Studio 2010 on Windows XP SP3 with IIS 5.1 and .NET 4.0.
I should add that I've tried attaching to aspnet_wp.exe, but when I go to a page that I know has a breakpoint in it, I get the following message when I hover over the "open circle" breakpoint:
The breakpoint will not currently be hit. No symbols have been loaded for this document.
I have a solution with some projects. There are several break-points in different projects. I want to trace the first thread hit one of these break-points and continue tracing that single thread despite of other threads entering the same code-blocks.
I know this is possible through defining a condition on the break-point i.e, thread name = ... or thread Id = ... but my case is a heavy loaded asp.net application and as soon as I attach to w3wp.exe many threads will hit the break-points. I need some thing like a ThreadLocal<break-point>.
I got a problem regarding CSS in my pages. I managed to apply styles to my page using css and everything looks fine in the Design view. I ran it on IE8 and everything is working fine. Now after I returned to Visual Studio, added some rules to my CSS, and noticing that everything is working fine in the Design view, I ran it again in IE8 and nothing has changed. The rules I added was ignored and it looks the same. I ran it on Firefox and Google Chrome and it's working fine.
But if I ran my project in IE8 through IIS7.5, everything is working fine so it means, the problem is within visual studio 2010.
I am a new in asp.net world (and in asp). I have a problem in asp.net page.... i wish to debug this page to try the error but I don't I can not debug I have downloaded all proj from "Team Fondation" and then I have took all page in check-out. The server, where I develop is the WEB serve test.
This is weird: When I try to debug ASP.NET web application, Visual Studio 2010 gives me this message "Script debugging of your application is disabled in Internet Explorer", but in my IE 7 (Internet Options --> Advanced), both "Disable Script Debugging" checkboxes are not checked.
I'm developing a large application in C# Visual Studio. It's reached the point where it takes about a minute to build the entire thing. In order to speed the debugging process, I want to be able to run the program with a debugger without building the entire thing. This seems like a very basic thing one should be able to do, but I've been unable to figure out how to accomplish it.
I have found the area in Options under "Projects and Solutions/Build and Run" where you can specify what VS should do "On Run, when projects are out of date:". I've tried changing it to both "Prompt to build" and "Never build," but it still always builds my entire project whenever I start debugging.
At the moment, I'm circumventing this by starting the program from its executable and attaching the debugger to it, but this is a bit of a hassle and it feels like I should be able to get VS to understand I don't want it to build when it debugs.
I'm developing a class library for a standalone software tool. The example class library I'm using as a template, which worked in VS2008, does not in VS2010. It compiles alright, but the external program does not get past the splashscreen when launched from VS2010 in release or debug mode. The project uses .NET 2.0 and I'm on WinXP.
I used to be able to attach to my w3wp process and Debug my web application, but this is not working anymore. I have no idea what changed to break this. I'm using Visual Studio 2008 SP1. And I'm debugging in IIS, not using ASP.NET's own server (i.e. I don't Run my project, I simply attach to a running process (w3wp).
My breakpoints simply have the "breakpoint will currently not be hit. The source code is different from the original version."
What I have tried:
Did a solution Clean. Did a solution Rebuild. Made sure that compilation debug=true in my web.config file. Deleted the bin folder Restarted Visual Studio Restarted IIS Restarted my Computer Added a simple Response.Write to ensure that the latest DLL is being used. It is. Made sure that Debug ASP.NET is checked in my project properties. It is. Made sure that all my projects are compiled in my build configuration. They are.