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
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 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.
I am using VS 2008 for development of a web application and IE 7.
The website as usually has some java script and some server side code files (different layers).
For some reason when I start the application in the debug mode (by hitting F5), the break points in the JS are not hit. I get the usual error as no symbols are loaded. But the break points in the CS files in the layers are hit.
If I use (CTLR + F5) and then attach the IE process to debug, then I am able to hit the break points in the JS file. But in this scenario I cant debug the CS files (I presume this is the expected bahaviour).
EDIT: In the IE (properties dialog), 'disable debugging' are unchecked.
why in the F5 mode I am not able to hit the debug points. The same used to work in the different machine not sure what is wrong in this one.
I just upgraded to Windows 7. On Win XP, I could set breakpoints in an ASP.Net project and those breakpoints would hit from any browser/tab on my machine. Using Windows 7, that doesn't work. The browser that launches when I hit F5 does, but no other instances/tabs do. If I try to explicitly attach to process to attach to another browser instance, it still doesn't hit.I need to debug this way because an error is occuring only when I enter the application by following an external link.
Basically what I am trying to do is have my webpage project folder located directly on my local machine (ex. Local #1). Our database is located on a server (ex. Server #1) . I am building my web applications on my local machine and then trying to debug them in Visual Studio 2008. Only every single time I click to debug my project I get a "Security Exception" error that looks something like the following...
"Description: The application attempted to perform an operation not allowed by the security policy. To grant this application the required permission please contact your system administrator or change the application's trust level in the configuration file.
Exception Details: System.Security.SecurityException: Request for the permission of type 'System.Web.AspNetHostingPermission, System, Version=126.96.36.199, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed."
I'm somewhat leaning towards the fact that I need to connect to the database to pull information from it and I don't have the proper permissions is the reason why this is happening but I've also read that it can be something that deals with improper configuration of my Web.Config file (i.e. I do not have something enabled).
Note #1: A co-worker of mine is having the same problem if he tries to put the project locally and then debug it. He has full administrative access to the DB and everything else.
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.
There are plenty other similar static methods defined within the class.
When does it fail: ONLY when the solution is compiled in 'DEBUG' mode. Everything works fine in 'RELEASE' mode.
What have I already tried:
1. Including a static constructor inside 'Utility' class - FAILED
2. Marking 'Utility' class with 'static' keyword: FAILED
3. Changing platform target from 'Any CPU' to 'x64': FAILED
As highlighted above, the issue is really not with VerifyPassword() method per se. Rather it is with the instantiation of 'Utility' type. That's why an exception is thrown from the constructor. Since 'VerifyPassword' is it is the first static method called, it appears in the stack. Just for the sake of proving that, I removed the call to VerifyPassword and returned 'true' instead. That way I was able to login to the application (no password verification), but failed at a later stage where I had called the Utility class on another method, namely Utility.ValidateSKUAdjustment(txtCurentMonthM1.Text).
First time i am going to work on (maintenance project) application that is already in production.The application was developed in ASP.net 3.5/C# 3.0(web forms) with jQuery,Ajax,Sql server 2005 and microsoft enterprise library 4.0.,WCF services. Questions (bear with me if my question is wrong)
1) Is it possible to use Visual Studio (2008 with SP1) to debug the remote application (i.e already in production)?.What are the tools do i need to use in order to keep track the things in case something went wrong?
2) Simply looking into Log file ,will solve the issues?
3) After having done with enhancements,is it possible to directly deploy the DLLs into production server.Won't it affect the running application?
what are the procedures i need to follow.Client is ready to provide any tools for my support.(What are the area do i need to aware to handle production system
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.
When i try to run my web application in visua studio 2008 a error window comes out that says: Unable to start program [URL]. The system cannot find the file specified. I googled but not got the solution for this problem. I have VS 2005 and VS 2008 both on my machine. I also unistalled VS 2008 and reinstalled it but that does not solve the problem.
I got these errors while trying to run a web application using vs 2008, The first error is this: >Application has generated an exception that could not be handled. >process ID=0x1130 (4400), Thread ID=0xe6c (3692). And when I press OK a second dialog reports this error:>unable to connect to the asp.net development server. I reinstalled, repaired and re registered msdbg2.dll and edited hosts file but still get this error. I need to debug an application but I can't. This error is on a 'Win 2003 server enrterprise service pack 1' with a vs2008 team system installation. What can I do to remove this error and run and debug my application?
I want to debug EditPanel.debug.js file of HTML Editor, but it never shows in VS 08 and Im sure it executes to that line.What I did to enable debuggingUnchecked both 2 checkboxes for disabling the debugging
Change following line
[ClientScriptResource("AjaxControlToolkit.HTMLEditor.EditPanel", "AjaxControlToolkit.HTMLEditor.EditPanel.js")] to [ClientScriptResource("AjaxControlToolkit.HTMLEditor.EditPanel", "AjaxControlToolkit.HTMLEditor.EditPanel.debug.js")]
I'm opening some project off of the codeplex website. When I do, it lists two types of files: *.cs and *.debug.cs me what the *.designer.cs" are?Also, when I build the application, it creates a "dll" in the "debug" directory. How do I make a dll get built in the "release" directory?
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.
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??