|
|
|
|
|
| | Total Hits: 103 | Today: 0 | Author: Stephen Toub | Rating:  |
| | 
I have a bunch of custom types that, for one reason or another, need to implement IDisposable. I want to make sure that the other developers on my team using this class always dispose of my types correctly. What can I do to warn one of my teammates if he forgets to call Dispose?... |
| | Total Hits: 105 | Today: 0 | Author: John Robbins | Rating: |
| |
Isn't it funny how the Microsoft® .NET Framework is thought of as an environment where you don't have to think about memory? Of course, what's one of the number one issues that continues to plague managed applications today? Memory! Why? When the garbage collector runs to reclaim memory, the common language runtime (CLR) suspends all the threads in the application—and no work gets done. When you're not getting any work done, you have a performance problem.
No matter how much you care abou... |
| | Total Hits: 59 | Today: 0 | Author: Stephen Toub | Rating: |
| |
I have a bunch of custom types that, for one reason or another, need to implement IDisposable. I want to make sure that the other developers on my team using this class always dispose of my types correctly. What can I do to warn one of my teammates if he forgets to call Dispose?... |
| | Total Hits: 50 | Today: 0 | Author: Microsoft Corporation | Rating: |
| |
Every developer or support engineer debugs applications at some stage in his or her career, yet debugging is often viewed as an arcane and difficult topic. While it is often difficult to determine why an application is hanging, leaking memory, or crashing, there are techniques you can apply to make the debugging process more productive and efficient. The Production Debugging for .NET Framework Applications guide aims to equip you with the mindset, tools, and techniques that will help you success... |
| | Total Hits: 144 | Today: 0 | Author: julesr | Rating: |
| |
In Classic ASP one might debug some code using VB Script.
and the comment/uncomment the code accordingly. This was a bit of a pain during the development process. In ASP.NET, one can use the Trace feature which simplifies matters somewhat. Page-level tracing can be set in the Page directive on the ASPX page.... |
| | Total Hits: 194 | Today: 0 | Author: Scott Mitchell | Rating: |
| |
Debugging Web applications can be a difficult process due to the logical, physical, and temporal differences between the mishmash of technologies that comprise such an application. For bugs that arise from the HTML and script received by the browser or in the transfer or request of a page's markup, developers often adopt archaic debugging techniques, such as using View Source and Notepad to scrutinize the contents received by the browser. With increasingly complex Web pages carrying dozens of in... |
| | Total Hits: 65 | Today: 0 | Author: Steve Lasker | Rating: |
| |
Walks through the process of debugging any custom design-time control when it is being used with the Microsoft Visual Studio .NET designer, and describes the chain of events that take place when you work with controls in the design surface. (13 printed pages)... |
| | Total Hits: 154 | Today: 0 | Author: Dotnet Galaxy | Rating: |
| |
Use Performance Monitor to determine if the leak is managed or native. To do this, you want to examine the values of Process:PrivateBytes and .NET CLR Memory:# of Bytes in All Heaps. If PrivateBytes and # of Bytes in All Heaps grow consistently, you are dealing with a managed leak. If you are debugging IIS, you will need to modify the Registry and cause ASP.NET to call DebugBreak rather than recycle the process. You do this by setting
HKLM\Software\Microsft\ASP.NET\DebugOnHighMem
to a val... |
| | Total Hits: 264 | Today: 0 | Author: Utpal Chakraborty | Rating: |
| |
Before Web development was popular and most applications were stand alone programs debugging strategies depended a lot on how and where they were being developed. When developing in C/C++ printf(...) was a favorite debugging tool on both UNIX and DOS environments for programmers. That changed when Integrated Development Environments--IDEs--like Borland's Turbo C++ and Microsoft's Visual Studio came along. These allowed stepping through code and watching local and global variables in a GUI as eac... |
| | Total Hits: 109 | Today: 0 | Author: James McCaffrey | Rating: |
| |
If you're encrypting user data with Secure Sockets Layer (SSL) over HTTP and you want to test your Web applications programmatically you'll find that the techniques are not widely known. In this month's column I'll show you how to set up a test SSL server and write test automation that verifies the functionality of a simple but representative Web application. The Microsoft® .NET environment provides powerful tools to test ASP.NET Web applications that use the SSL security mechanism. To illustrat... |
| | Total Hits: 96 | Today: 0 | Author: James McCaffrey | Rating: |
| |
As Web applications have become more complex, testing them has become more important. There are many testing techniques available to you. For example, in the April 2005 issue of MSDN®Magazine, I describe a simple JScript®-based system that can test a Web app through its UI by using the Internet Explorer Document Object Model. That technique is effective but has several limitations. Some of my colleagues asked me if it was possible to use the .NET Framework to write more powerful but still lightw... |
| | Total Hits: 83 | Today: 0 | Author: John Robbins | Rating: |
| |
Recently I was moving along with my ASP .NET Web site de-sign and was quite pleased to see just how much easier ASP .NET made the whole process. Being a good boy, I went through the design process and was about to start development when I noticed a small problem. A prototype I developed to test a theory would hang when I used the standard Debug.Assert. If you hearken back to the February 2001 Bugslayer column, you'll remember that I talked about the TraceListeners, which do the actual output for... |
| | Total Hits: 240 | Today: 0 | Author: Chris Sully | Rating: |
| |
Bugs are a fact of the programmer's life. How can we deal with them efficiently? In this series of two articles I'm going to look at two main areas of finding and fixing errors in your program - Tracing and Debugging. We shall look both at the inherent supporting features provided by the .NET framework and ASP.NET and the additional tools provided by VS.NET over the course of the two articles. Part I shall focus on Tracing, Part II on Debugging, though as I've already stated these are overlappin... |
| | Total Hits: 249 | Today: 0 | Author: Chris Sully | Rating: |
| |
Bugs are a fact of the programmer's life. This is the second of two articles examining how we may deal with them efficiently within .NET. In part I we looked at the process of collecting information about a programs execution (tracing). Tracing is really a part of the overall activity of debugging: finding and fixing errors in your program. In part II of this series we'll focus on debugging and in particular on the tools available to the programmer to simplify the task.... |
| | Total Hits: 74 | Today: 0 | Author: Doug Seven | Rating: |
| |
This past week, I've been doing the keynote presentation for the Microsoft Visual Studio .NET Academic fall road show. One of the things we noticed university students seem to have in common is knowing more than one programming language. So we decided it would be great to demonstrate how the .NET Framework and the Common Language Runtime (CLR) enable not only cross-language integration of assemblies, but also cross-language inheritance and debugging of assemblies. During the keynote, I opened Vi... |
| | Total Hits: 53 | Today: 0 | Author: MSDN | Rating: |
| |
To debug a .NET Framework application, the compiler and runtime environment must be configured to enable a debugger to attach to the application and to produce both symbols and line maps, if possible, for the application and its corresponding Microsoft Intermediate Language (MSIL). Once a managed application is debugged, it can be profiled to boost performance. Profiling evaluates and describes the lines of source code that generate the most frequently executed code, and how much time it takes t... |
| | Total Hits: 90 | Today: 0 | Author: MSDN | Rating: |
| |
The ASP.NET page framework provides extensive support for debugging Web applications. However, because Web applications are distributed, there are some special issues associated with debugging them. In general, you debug Web applications the same way you do other types of Visual Studio applications. You can set breakpoints, start the debugger, break into code, examine variables, and perform all the functions associated with the Visual Studio debugger. For details, see Using the Debugger.... |
| | Total Hits: 122 | Today: 0 | Author: Chris Kinsman, Jeffrey McManus | Rating: |
| |
Debugging ASP.old applications was generally only slightly less painful than a trip to the dentist. There was a way to debug ASP.old applications, but it was poorly documented and essentially required Visual InterDev and a team of crack technicians, as well as favorable weather conditions and a whole lot of luck to work correctly. Many ASP.old developers got into the habit of using code as a way of creating breakpoints in their code.... |
| | Total Hits: 132 | Today: 0 | Author: Patrick A Lorenz, Saurabh Nandu | Rating: |
| |
This is the second of two articles that survey the main enhancements to Visual Studio 2005 and ASP.NET 2.0. This article will focus on changes to the internal architecture of ASP.NET and the implications for debugging and compiling with VS2005. In particular, topics covered include testing and debugging, code separation, precompilation, multilanguage support and deploying web sites.... |
| | Total Hits: 103 | Today: 0 | Author: MSDN | Rating: |
| |
During the Troubleshooting ASP.NET series, Author has done over quite a few different troubleshooting techniques using different tools. By now, you should have noticed a pattern; these techniques have all involved troubleshooting an ASP.NET application in a production environment. Why is that? Most ASP.NET developers will catch pervasive problems during the development or testing phase. The really nasty problems typically rear their head after an application has been moved to production.... |
|
|
|
|
|
|
|
|
|
|
|
|
|