I have my project in VS2005, its is working fine last few years, But now durning development i face problem regarding breakpoints, here Im unable to get stoppage at breakpoints, I have change setting of security in Internet options add localhost as trusted site, but still its remain the same.
I also try Attach to process.... option from the debug, here webDev.WebServer process of running site is disable. Now Im totally unable to debug my project.
I am using VS2008, SP1. I am unable to put breakpoints in my client side javascript code. Wherever I try to put the breakpoint, I am getting the message: "This is not a valid location to put the breakpoint". I have the js intellisense working fine. I also unchecked the two "Disable Debugging" checkboxes on IE. Due to this problem, I am unable to debug the js in VS 2008.
When I try to set breakpoints in a JavaScript code file, I get the warning, "The breakpoint will not currently be hit. No symbols have been loaded for this document."
This is a fairly large project that was working normally under VS 2008. I just installed VS 2010 Pro Academic, and this is one of the new problems that have appeared. It's running under Win 7 64-bit, IE 8, and both of the IE "disable script debugging" options are turned off. Debugging is enabled in the web.config file. The JavaScript code in question is being executed normally, and inserting "debugger" in the code works as expected. While running under debugging, you can open the corresponding script document from the Solution Explorer, Script Documents, and insert breakpoints just fine. Attaching to the IE process (from the Debug menu) doesn't seem to make any difference.
Basically, everything I can think of looks normal, and yet I can't insert breakpoints into the original source code with VS 2010. The problem is reproducible on more than one JavaScript source file. I rebooted and consults The Great Google, all to no avail.
This is a real headache for development. Has anyone else discovered a fix for this?
(UPDATE: I spent a few hours and created a new project, and copied all of the files from the original to the new one. Now, I can set breakpoints n the new project, but still can't in the original. Something's different between the two, but it isn't clear what it could be.)
I have a asp.net mvc project in VS2010. In it I have a view called main.aspx that contains alot of javascript that frequently needs to be debugged. I can set the break point in the aspx page's javascript at edit time in VS2010. It appears as a mapped breakpoint. When I launch the debugger/IE browser, the javascript break point never gets hit. If I add a debugger; statement to my javascript I can launch a new visual studio instance and debug javascript. Unforunately, this requires a second visual studio instance and I have to set breakpoints all over again when I do it this way. Also, I have to remember to remove the debugger; statement when I am finished debugging. Is there a better way to get client side breakpoints working in Visual Studio 2010/IE?
I had the strangest bug yesterday while trying to debug in vs.net 2005....
I had an '05 web application. I clicked the "Run" button to start debugging, and the webpage popped up fine. I could run through the pages fine. Everything seemed fine....UNTIL!
Until I tried to start inserting breakpoints into my code. The application ignored them. In addition, I noticed my little green visual studio "Start Debugging" arrow (which is normally greyed out while in debug mode) was green. It was as if visual studio completely detached itself from my website I was trying to debug.
After playing around with it for a while, I realized I also had a vs.net 2008 solution open as well. My '08 solution wasn't in debug mode or anything, it was just sitting there open. I just happened to close it, not thinking anything of it, and presto! My 2005 debugger started working again!
So basically, I can't debug an '05 solution (or at least a web solution, as that's all I tried) while I also have an '08 solution open.
We've currently migrated our Classic ASP web to ASP.NET. Our greatest hope lies in using the Visual Studio for debugging. But this hope was destroyed devastatingly.There are lot of issues we encountered:No syntax highlightingNo breakpoints (message: "This is not a valid location for a breakpoint.")No Intellisense We cannot find the reasons. But we think VS can't resolve our include links correctly. (In our case we remove all inludes and the page was highlighted again.)That's why we have a lot of questions:Can VS2008 handle includes (<!-- #include file="myinclude.inc" -->) at all?Are there any constraints we need to know? Maximal lines to include? Including<% .. %> or <script language="vb" runat="server"> .. </script>? What settings have to be made?
I'm working on a VS2010 Solution containing an ASP.NET Website Project and 8 c# class libraries. All projects are set to compile under .NET 3.5
When I set a breakpoint somewhere in the class libraries, the debugger breaks correctly and everything is fine. If I then stop debugging, modify code in the class library, and start debugging again (which of course rebuilds the libraries which were modified) the debugger ignores the breakpoints.
Has anyone else experienced anything like this? I'm lost and it's extremely frustrating to not be able to debug after making even a single line change and rebuilding.
Visual Studio 2010 Ultimate Windows 7 Professional 64-bit
In Visual Studio 2008 while debugging an ASP.Net website I set a breakpoint in the codebehind page. I refresh the page or submit to call the method, the breakpoint is hit. Then I delete the breakpoint and continue execution. I make a change to the codebehind page and save it. I submit or refresh again and the deleted breakpoint is back! It is hit again, and I delete it again. I have tried delete, disable, nothing works it keeps coming back if I make a change to the page. It is extremely annoying and unproductive. The only way I have found to make the breakpoint permanently go away is to use the Debug menu Delete all breakpoints item, which is obviously less than ideal. I have been able to reproduce this on other developers machines also. What is going on here? Is this by design? Is it a bug in VS? How do I keep these zombie breakpoints from resurrecting?
nfortunately, I can't get my breakpoints to work when in debug mode in Visual Studio 2008 (ASP.NET 3.5, Windows 7, IIS7). The website compiles and opens in debug mode, but the breakpoints themselves generate the following error message:"The breakpoint will not currently be hit. No symbols have been loaded for this document."There are some recommended solutions online, but for various reasons, either they haven't applied or I haven't been able to make them work. I've been trying to find the solution for about 12 hours now, and I'm getting desperate.(Note 1: This problem is specific to this website. I do have other websites that I open in VS2008 where the breakpoints work fine.)(Note 2: There is only one website/project associated with this problem. This website does not have multiple projects.)
I had a dropshadow extender attached to a gridview. I was getting an error: Microsoft JScript runtime error: Sys.ArgumentException: Value must not be null for Controls and Behaviors. Parameter name: element So I removed the extender and I have a break point on: If Not Page.IsPostBack Then And it never stops there anymore. Page comes up though. I have restarted VS and rebooted. The app consists of a WebSite and WCF.
I work for a financial company that has many branches all over the world. Their network security is no 1 on their network priority list. Even the workstation I use is locked down pretty tight, so I don't have the ability to change or install anything. The firewalls are also pretty much very well controlled and I can't really do much, outside of the network, other than browse the web.
My problem is related to all of this...I wanted to create a web app that queries the Google Maps api to get info about the location clicked on a map, by using their reverse geocoding api.If I type the following into my browser, I get the results I require:
When I use that url within my app, I get an "Unable to connect to remote server" error. I can only assume that this is related to our restrictions on the firewall, as if I publish the page to my web site (outside the company network), and run it, it works perfectly.
I decided that I would build a small web service with the required code in it to return the data I need. I have written the web service and published it to my site. When I test it by browsing to the asmx file location on my site, I get the usual info presented about the web service.
My problem is that when I try adding the web service to my mapping app, I get the following error, and the "Add Reference" button is disabled:
There was an error downloading 'http://www.carrollsoft.za.bz/mailclient/service.asmx'. Unable to connect to the remote server.A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed...I thought that web services were supposed to be able to get around firewalls, because they use port 80? Our proxy server isn't on port 80, so I added the following to the web config on my mapping app, but I still get the same error:
I am developping an MVC3 RC2 application and just after hitting F5 on my asp web application, I am getting this error message program '[7780] w3wp.exe: Managed (v4.0.30319)' has exited with code -2 (0xfffffffe).So I am totally unable to debug my application
I have used Visual Web Developer (versions up to 2010) with no problems for several years. Starting last week I am no longer able to run or debug any ASP.Net application locally. I am running Windows XP, IIS 5.1, IE8, Visual Web Developer 2005, targetting .Net 2.0. I am not able to Start Debugging or Start Without Debugging for any project. When I attempt to Start Debugging, IE browses to [URL] instead of to the project I am attempting to run. When I Start Without Debugging, IE opens to about:blank and then when I close that window another IE window opens to [URL]
Maybe irrelevant, but I had the same problem with IE7 and VWD 2010 (versus IE8, VWD 2005). IIS is set to .Net version 2.0. I have the same problem whether I add a virtual directory to my project in IIS or not.
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.
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 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.
I'm getting this error: "Unable to edit file .... The style sheet must be part of the current project and the project must be a web site or web application project." I have tried it with the CSS file defined in the Site.Master file as relative (,,/,,/xx.css) and full path (e.g. c:....) I get the same error in both cases and I am unable to edit the CSS file.
Downloaded Microsoft Visual Web Developer 2010. I cannot find aspnet_regsql.exe anywhere on my pc, searching to download it. Google searched, search in msdn, microsoft, still cannot find this file to download. where I can download this file from?
I have installed visual studio 2010, but I got some problem in connecting to my sql2005.
Whenever after I choose the Server name and database name for new connection, it shows a message that unable to add data connection.
Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version= 10.0.0.0, Culture=nertral, PublicKey=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
I moved my site to a Windows 2008 server, reinstalled VS2005 and now I am unable to debug my application. When I click start debugging, the button is greyed out until the browser launches and then it returns to normal. In other words VS is just launching the app without attaching to it. I have tried running as administrator and played around with the authentication settings to no avail. I am running with Forms authentication.
Recently I've upgraded from Visual Studio 2008 to Visual Studio 2010, however I'm having various problems when uploading my compiled web site to the live area. I'm doing exactly the same as I would have done with Visual Studio 2008, however, now I receive errors such as:
{filename}.aspx is not a pre-compiled file masterpage.master does not exist
All these errors don't make sense. Has anyone encountered these problems before, and was a solution ever found?
I have not been able to open css files in VWD, I must have sone something I don't know. I can open them in wordpad, and WebDevelopment Server still displays properly so the file is not currupt. Is there a setting I messed up in web.config or somewhere else?
