.net - Sitecore 6 Debugging With Visual Studio 2008?
Jul 24, 2010
I'm trying to debug sitecore 6 asp.net code using visual studio 2008 (Windows server 2003 OS), concretely i am trying to get breakpoints to work. I tried setting the breakpoint and then on VS, debug-> attach to process.. -> IIS web server process, but nothing happens when i browse to a certain aspx where a breakpoint is located at the beginning of the Sitecore.Web.UI.WebControl.DoRender method
I tried setting on the website properties home directory->configuration->debugging and check both client-side and server-side debugging but nothing changes. Tried stopping the website, recycling the appPool and restarting, reataching the debugger and nothing happens
I have upgraded a Visual Studio 2005 Web Site in a 32 bit server to Visual Studio 2008 maintaining the same 2.0 framework in a 64 bit server with Windows 2008 R2 Server. The Web Site has several class libraries.
After porting to Visual Studio 2008 2.0 Framework using the Upgrade Wizard, I found that I was unable to hit a break point in the Project code behind files while I was able to in the class libraries. The bin folder has the dlls and the corresponding pdb files for the class libraries. I did start the Web site as an Administrator and made sure whole bunch of IIS7 properties are properly set.
I tried to rebuild the solution as a Web Application in Visual Studio 2008 and gave up that approach as I faced hundreds of error messages pointing to missing references and namespaces inspite of adding whole lot of references and namespaces to the Web.
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.
I am having a problem with my Visual Studio 2008 debugger on Windows 7. When I press F5, my Visual Studio web server freezes, and the Visual Studio status changes to "Not Responding".
I have a solution I have been working on over the last few weeks with a 3 or 4 projects in that used to build and begin debugging in under 10 seconds.The solution contains 3 dll's and 1 mvc project.
As of today, it takes about 2 minutes to start debugging, it keeps pausing on "loading symbols for ccpCodeProvider.dll".
I'm debugging on the internal vs development server, and I haven't changed anything since yesterday?I haven't ever used symbols before, and I'm not trying to debug the framework or anything, I just want my stupid web project to run.I created a new solution from scratch and added a random console app, and that also takes forever to debug.
I have an asp.net project in visual studio 2008I press F5 and the "test page" does not launch and I don't understand why.Looked at the properties for the site and "start action" is correctly set to "use current page"Similar question. assuming it automatically launched above, how does one open a 2nd instance of the current debug site (seems like their ought to be a "launch site" button?edit: I went back and launched VS as admin and it did launch the site. Maybe this is a security issue?
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?
I have alway tested/debugged my web applications by using f5 to "Start Debugging". Recently (yesterday) I have begun to start without debugging then attach the debugger to the webdev process if I needed to set breakpoints or anything. So far I haven't noticed much of a performance increase when not using the debugger. I am curious about how others save time when running locally.
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 run the start debugging option...it runs successfully. but still is shows start debugging option is shown in the Visual studio 2005 IDE. And one more problem is ::I applied break points in one page and run the application. but those break points are not detected....
suddenly, with my Visual Studio 2008 I can no longer debugging my web applications (ASP.NET 3.5). I obtain this error: Unable to start debugging on the web server. Click Help for more information. Auto-attach to process [8360] w3wp.exe' on machine 'DELL' failed. The weird thing is that I haven't done special changes to my IIS.
Is there any tool for Visual Studio 2008 which can reformat ASPX code to make it more presentable (eg insert line breaks, format the lines so they wrap when necessary, etc)?
is there an easy way to debug an application in vs 2008 without actually logging onto my machine as different users? its a winforms app in 3.5 on xp...i know how to do the whole "run-as" option when the program is done and built, but for testing its getting really annoying! maybe something like impersonate that web apps have...anything like that for winforms?
can Visual Studio 2008 be All-In-One tool to integrate source code continuously from team members, build, unit test?
Having used Visual Studio Team Edition 2005, unit testing each method within VS itself. I strongly believe that it is feasible to add-on tools. Example ankhsvn tool to use SVN from Visual studio [URL]
In my investigating i have come across number of tools(shown below) to use with Visual Studio 2008 professional
Development tool:- Visual Studio 2008 professional using Subversion as source control tool. Continuous Integration:- Hudson or Cruise control Build tool:- NAnt Testing:- NUnit, Selinium As Visual Studio 2008 can be used for unit testing I think NUnit is out of consideration.
In the same way i would like to have any other tools/add-ons to Visual studio to implement continuous integration, building and unit testing. This process should be automated such a way source code between team members is continuously integrated, built and unit testing is done as configured.
Objective is to use few number of tools as add-on to Visual Studio or achieve most from Visual studio itself (example unit testing). Visual Studio should be all in one tool.
I am aware that Team Foundation Server best suits my requirement, but it is out of scope due to its cost.
I have a site that I am developing with VS 2008. I have a breakpoint set in my code behind file. This file is vast as some of it was created with Iron Speed 7.0. What I'd like to do is limit the debugger to the one file. That is, no matter where the code goes it skips over code in other files, and automatially breaks when execution returns to the file I put the break point in. The code is too vast to step a bit at time and choose to step into or out of bit of code. I want it to just debug the current file.
