.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
david stephan
Gaurav Pal
Post New Web Links

Debugging Issues.

Posted By:      Posted Date: September 20, 2010    Points: 0   Category :ASP.Net


 So I am debugging a method, and going into debug mode one of the things I use are hovering over vaiables and Watch to see the variable values at some point in time. However, now I seem to be getting nothing when I hover over and the watch shows:

the name 'textInCommand' does not exist in the current context

 But, and here's the part I dont understand, it compiled correctly and although it isnt showing me the variable values, when I add this value to another (ie += on a string) it adds correctly.


Any Ideas?



View Complete Post

More Related Resource Links

Debugging Issues in Windos 7 & Visual Studio 2008

I have Strange issue.I have Windows 7 and Visual Studio 2008.When I try to debug a web application by inserting BreakPoint. It will go fine for few seconds or couple of  minutesAfter that the debugging stops automatically. But were else if did not insert Break point in the application the webpage is alright. (I can see debugger still running)Does any one have come across the same issue please shed me some light.Thanking you in advanceNathanI had the same issue in the XP after installing IE 8. The below line solved the issue but this wont work for windows 7Add a DWORD value called TabProcGrowth with a value of 0

Issues with SQL CLR deployment and debugging


We're having 3 issues.  I've posted a ticket with Microsoft phone support, but am posting here as well in case I can shortcut that support process, and so it will be documented for other users.  I'm running Windows XP, Visual Studio 2008 and Visual Studio 2010, and SQL Server 2008 with Management Studio version 10.0.2531.0:

1) In Visual Studio 2010 on my machine AND my coworkers' machines: If we try to deploy any SQL CLR project to a large database, the deploy hangs Visual Studio for a long time, and eventually returns but fails to deploy the objects to the database.  No error message is thrown.

2) In Visual Studio 2010 on my machine AND my coworkers' machines: if we create a new SQL Server Project, add a new User Defined Function that simply returns a scalar value, put a breakpoint in that function, attach to the sqlservr.exe process from Visual Studio 2010, and then run the function from SQL Server Management Studio, the breakpoint is not hit and the function hangs until the debugger is stopped, at which point SQL Server Management Studio indicates that the query was cancelled.  We can work around this by debugging in Visual Studio 2008, but it's a hassle (i.e. start a different project debugging in Visual Studio 2008.  Open the files you want to debug in the same Visual Studio 2008 instance (even though they were created in

Issues with SQL CLR debugging using VS2010 and SQL 2008 R2

I upgraded a VS 2008 SQL CLR project, which worked perfectly, to VS 2010 SP1.  However, I did not have to debug the CLR routines until today.  Now, whenever I attempt to debug a change to my code, the deployment succeeds (the new function is listed in the database), but the debugging never occurs because although it says that is successfully attached (“Auto-attach to process '[1696] [SQL] stx3-desktopx64' on machine 'stx3-desktopx64' succeeded”).  It also says that it was “Canceled by user”, which it certainly was not.  I have also tried simply debugging on a different machine, which had NO changes made at all to the project, and it generates exactly the same messages.  I have also changed the target from Any CPU to x86 to x64 to no avail.  Both test machines use a local SQL instance that is x64, as is the version of Win 7.  I read one article that suggested manually deploying the routine would help, but it changes nothing.  Every debug attempt results in the same messages after 20-30 seconds of waiting.  On VS 2008, t

VS2010 Professional .NET 4.0 Remote Debugging ASP Website Project


Trying to remote debug ASP website from VS2010 Pro to Windows Server 2003 machine.  Specifically, trying to debug a Web Service, but breakpoint says, "The breakpoint will not currently be hit. No symbols have been loaded for this document."  This happens for all compiled code though.  I have read this is due to missing PDB files and the work around is to manually copy them, as noted here.  Problem is, I cannot find any PDB files for my project, except referenced libraries, which I can remote debug.


  • web.config has <compilation debug="true">
  • Debugger is attached to wewp.exe process on remote server
  • Installed VS2010 remote debugger from DVD (as I can remote debug referenced libraries)

This is beyond frustrating.  I migrated my code from VS2008 .Net3.5 to VS2010 .Net4.0 to take advantage of the inherent multithreading framework.  Debugging works when using local host and was stable until deployment to test server.

Thanks in advance,


HttpHandler works with Visual Studio Development Server debugging, but not otherwise


Hi all,

I'm new to HttpHandlers.  I am writing an HttpHandler that reads uploaded files directly from the request stream to provide progress that can be queried using an AJAX request.  For large files, this seems to be faster than having ASP.NET load the file contents into Request.Files and then streaming the file from there to wherever it goes (Linq to SQL into a VARBINARY column in an SQL Server database.)

My HttpHandler works perfectly when I'm debugging using the Visual Studio Development Server, but doesn't work otherwise.  The application pool for this application in IIS 7 is set to run in Classic Mode, and the Handler Mappings screen in IIS says that I must manage managed handlers in system.web/httpHandlers. 

I set up in my applications Web.config file.

<add verb="GET,POST" path="*.upload" type="Namespace.For.UploadHandler, AssemblyForUploadHandler"/>

It works great, so long as I don't debug with the "Use Local IIS Web server" option.

What else do I need to do to get this to work?


Debugging ASHX after deployment



I'm finished with a part of my ASHX handler and need to test it against the software that'll be calling it using HTTP POST. The software required an https url so I created an internally hosted site in IIS and published the project there. 

Question now is how do I do any debugging on the script to see what data is coming out of it before the data goes back into the software that's calling it? Do I set something on the project itself to be able to step into the published DLL? 

IE 8 Issues with Chinese/Japanese Characters


On my web application, I display information in different languages. Everything works fine in IE compatibility mode and FireFox but it shows boxes for chinese/japanese languages. I am pretty much having the same issue as described here



Thanks for your help.

IntelliTrace: Debugging Applications with IntelliTrace


Justin Marks shows how to use the IntelliTrace feature coming with Visual Studio 2010 Ultimate, which gives developers powerful new debugging tools to "turn up the dial" and collect the complete execution history of an application, get deeper levels of information and quickly find bugs.

Justin Marks

MSDN Magazine April 2010

Parallel Debugging: Debugging Task-Based Parallel Applications in Visual Studio 2010


In Visual C++ 10 and the Microsoft .NET Framework 4, Microsoft is introducing new libraries and runtimes to significantly ease the process of expressing parallelism in your code base, together with new tool support for performance analysis and debugging of parallel applications. In this article, you will learn about debugging support in Visual Studio 2010, much of which is focused on task-based programming models.

Stephen Toub, Daniel Moth

MSDN Magazine September 2009

Windows With C++: X64 Debugging With Pseudo Variables And Format Specifiers


This month we explain how pseudo variables and format specifiers provide a wealth of information for use in debugging.

Kenny Kerr

MSDN Magazine December 2008

Concurrency: Tools And Techniques to Identify Concurrency Issues


Efficient parallel applications aren't born by merely running an old app on a parallel processor machine. Tuning needs to be done if you're to gain maximum benefit.

Rahul V. Patil and Boby George

MSDN Magazine June 2008

Toolbox: Easy Web Debugging, Extending Reflector, and More


This month, a better design-time experience for Web apps, Scott Guthrie's blog, extending Extend Lutz Roeder's Reflector, and more.

Scott Mitchell

MSDN Magazine March 2008

.NET Matters: Debugging finalizers


Find out how to use finalizers as a way to warn developers who use your custom types when they are garbage collected without having been disposed of correctly.

Stephen Toub

MSDN Magazine November 2007

Event Tracing: Improve Debugging And Performance Tuning With ETW


Event Tracing for Windows (ETW) provides general-purpose, high-speed tracing of events raised by both user-mode applications and kernel-mode device drivers. Learn how ETW can improve your development and debugging work.

Dr. Insung Park and Ricky Buch

MSDN Magazine April 2007

CLR Inside Out: Investigating Memory Issues


Memory issues can manifest in a wide variety of ways. This column shows you how to collect the data you need to determine what types of mem¬ory issues you are experiencing.

Claudio Caldato and Maoni Stephens

MSDN Magazine November 2006

Bug Bash: Let The CLR Find Bugs For You With Managed Debugging Assistants


Managed Debugging Assistants are new to the .NET Framework 2.0 and help you to discover serious bugs quickly. Learn how to harness their power.

Stephen Toub

MSDN Magazine May 2006

Debugging: Root Out Elusive Production Bugs with These Effective Techniques


Errors happen. But in production, error logs often provide little or no help in pinpointing the exact line of code in which the problem originates. You can't usually isolate the root cause by modifying code in a production environment because recreating the exact same environment is very difficult due to the large number of potential software and hardware configurations. This article provides some concrete steps you can take to get at the heart of the problems in your production code.

Matt Adamson

MSDN Magazine July 2005

ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend