Edited by Nancy Michell
MSDN Magazine January 2002
View Complete Post
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.
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,
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?
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?
this is my aspx and cs code , let me know whether it is correct or not??
onload and performance on navigation of record show be good.
Plz help me
<CR:CrystalReportViewer ID="CrystalReportViewer1" runat="server" AutoDataBind="True"
DisplayGroupTree="False" ReuseParameterValuesOnRefresh="true" HasToggleGroupTreeButton="False" Height="1039px" ReportSourceID="CrystalReportSource1"
<CR:CrystalReportSource ID="CrystalReportSource1" runat="
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.
MSDN Magazine April 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
Good navigation makes for happy users, and happy users are good for your business. See what makes users happy this month.
Dr. Charles B. Kreitzberg and Ambrose Little
MSDN Magazine March 2009
This month we explain how pseudo variables and format specifiers provide a wealth of information for use in debugging.
MSDN Magazine December 2008
This month, a better design-time experience for Web apps, Scott Guthrie's blog, extending Extend Lutz Roeder's Reflector, and more.
MSDN Magazine March 2008
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.
MSDN Magazine November 2007
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
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.
MSDN Magazine May 2006
In my childhood I spent several weeks a year in Holland with my extended family. As a young American boy I was fascinated with the electric Dutch trains, something we didn't see in my hometown of Dallas, Texas.
MSDN Magazine October 2005
MSDN Magazine September 2005
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.
MSDN Magazine July 2005
Navigation is central to a well functioning Web application and it can be implemented numerous ways using today's technologies. This article highlights some of the key details of the new navigation controls that are part of the upcoming ASP.NET 2.0, and talks about how to design and implement one of these navigation controls today. This article contains a simple Web site that demonstrates the use of these navigation controls, pointing out some of the key items such as a breadcrumb control and things to watch for along the way. The article then describes how to implement a breadcrumb control today.
Dave Donaldson and Steven DeWalt
MSDN Magazine June 2004
There is a whole host of new goodies in upcoming release of Visual Studio 2005 that will enhance your debugging experience. One such improvement will make it easy to visualize types within the debugger. This article discusses those improvements and covers debugger attributes and type visualizers. In addition, the author shows you how to extend the display of your own types with custom attributes and how to plug in an assembly to visualize.NET types built into the framework.
MSDN Magazine May 2004