.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

Bugslayer: .NET Internationalization Utilities

Posted By:      Posted Date: August 21, 2010    Points: 0   Category :ASP.Net

As you saw in last month's column, . NET internationalization support is excellent and allows you to move your application to a world audience quite easily. Before you jump into this month's discussion, you may want to go back and read the March column.

John Robbins

MSDN Magazine April 2004

View Complete Post

More Related Resource Links

Bugslayer: Measuring the Impact of View State


Bloated view state can be a real performance bottleneck for your Web app, but it can be difficult to diagnose. John Robbins creates a handy tool that records and reports the view state size for pages in your ASP.NET applications.

John Robbins

MSDN Magazine November 2007

Bugslayer: Wait Chain Traversal


Windows Vista has a new API called Wait Chain Traversal (WCT), which allows you to determine when and why a process is deadlocked. Read on.

John Robbins

MSDN Magazine July 2007

Bugslayer: Minidumps for Specific Exceptions


This installment of Bugslayer covers the use of ADPlus to create a minidump of your Microsoft .NET Framework 2.0 pro¬cesses on specific exceptions.

John Robbins

MSDN Magazine November 2006

Bugslayer: Strengthening Visual Studio Unit Tests


Visual Studio 2005 brought so many new features to the table that it can seem almost overwhelming. One of the most exciting additions is the new unit testing features found in the Test menu on the main menu bar.

John Robbins

MSDN Magazine March 2006

Bugslayer: SUPERASSERT Goes .NET


Those of you who have been reading this old Bugslayer column over the last nine years have branded into your frontal lobe a single word: ASSERT! Anytime you can have the code tell you about a problem instead of having to find it by slaving away with a debugger is a huge timesaver.

John Robbins

MSDN Magazine November 2005

Bugslayer: Unhandled Exceptions and Tracing in the .NET Framework 2.0


By now, you've certainly heard about the big changes coming in Visual Studio® 2005, but when it's time to move your code over it will be the small things that trip you up. In this column, I want to cover two of the many excellent changes that you could easily overlook as you make the move to the new runtime and development tools.

John Robbins

MSDN Magazine July 2005

Bugslayer: Mini Dump Snapshots and the New SOS


In debugging some large Microsoft® . NET Framework-based ap-plications over the last few months, I've been spending more time looking at mini dumps than at live processes. This is mainly because in those large applications problems surface when the apps are running in production and not on test systems.

John Robbins

MSDN Magazine March 2005

Bugslayer: Three Vital FXCop Rules


In the June 2004 installment of the Bugslayer column, I introduced the amazing FxCop, which analyzes your . NET assemblies for errors and problems based on code that violates the . NET Design Guidelines.

John Robbins

MSDN Magazine September 2004

Web Q&A: Font Sizing, Internationalization in JScript, and More


Font Sizing, Internationalization in JScript, and More.

Edited by Nancy Michell

MSDN Magazine June 2003

Bugslayer: SOS: It's Not Just an ABBA Song Anymore


Hidden deep inside the Microsoft .NET Framework 1.1 you'll find Son of Strike (SOS). If your app is a pure managed code, your development and debugging tasks are easily handled by existing Microsoft tools. If you're on border between managed and native code SOS is your man.

John Robbins

MSDN Magazine June 2003

Windows XP: Escape from DLL Hell with Custom Debugging and Instrumentation Tools and Utilities, Part


Building on his article published in the June issue, which demonstrated several ways to get process and DLL-related information from APIs such as PSAPI, NTDLL, and TOOLHELP32, the author presents some unusual ways to get system-oriented info that you can easily integrate in your own toolkit. There are three tools included as samples: LoadLibrarySpy, which monitors an application and detects which DLLs are really loaded; WindowDump, which retrieves the content and a detailed description of any window; and FileUsage, which redirects console-mode applications to tell you which process is using any opened file.

Christophe Nasarre

MSDN Magazine August 2002

Windows XP: Escape from DLL Hell with Custom Debugging and Instrumentation Tools and Utilities


DLL conflict problems can be tough to solve, but a large number of tools are available to help. There are also many Windows APIs that you can use to build custom debugging tools. Three such tools are discussed here and provided as samples. DllSpy lists all the DLLs loaded in the system and the processes that are using them. ProcessSpy enumerates the running processes and exposes the DLLs they are using, and ProcessXP displays the list of concurrent running sessions for Windows XP.

Christophe Nasarre

MSDN Magazine June 2002

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