Visual Studio 2010 New Features in Debugging – Exciting & Innovative

(Note: This blog post was originally published under my old domain(codesmiles.com), here. Web Archive link. (This post is part of my Visual Studio 2010 series) This article talks about Visual Studio 2010’s new features related to debugging, applicable from beginner to expert(based on Visual Studio 2010 beta 2). Visual Studio 2010 comes with powerful debugging features. Debugging is an area where an improvement brings great relief to developers, and increases developer happiness. Visual Studio 2010 seems to highly enhance debugging support, and can change some basic ways we used to debug applications, let us have a look.[more] Export/Import Breakpoints By using Export/Import breakpoints in Visual Studio 2010, you can debug a portion of the application and export the current set of breakpoints and import it back whenever you want to debug the same portion of application, no matter what breakpoints you have currently placed in your code. This feature will enable you to have different set of breakpoints for each scenario or portion of application that you may need to debug. This is one of the features that I highly wished to have. An example scenario… consider your web page/windows form has basic CRUD(Create/Read/Update/Del) options, you are currently working on

The (not much utilized) Debug->Exceptions… window technique

(Note: This blog post was originally published under my old domain(codesmiles.com), here. Web Archive link. The Debug-Exceptions… window is a useful tool that at times saves lot of time when debugging. Even though this exists (i think)from Visual Studio 2003, I Still find people struggle a bit with the situation I am going to explain next.[more] As you know Visual Studio highlights the exception code line when it is not handled. Sometimes we purposely don’t handle exceptions in a method and let the exception thrown to calling functions.   Usually we have a multi-project solution that typically has layers like Business logic, Data access layer, UI, etc. Imagine that you make a call from the UI to a local function and it calls another function in BLL and the call goes deep into layers of your project architecture. Now, when it is not sure if each of the methods getting called handles exceptions in it or doesn’t throw identifiable exceptions. For instance.. private void Function_A() {     try     {         BLLFunction();//this calls few other functions..     }     catch (Exception ex)     {         //handle exception     } } Function_A() calls BLLFunction() and it again calls few other functions,

Gmail ignores dots..a gmail secret..

(Note: This blog post was originally published under my old domain(codesmiles.com), here. Web Archive link. It is bit old but still a surprise for many. What is your gmail id? is it your.name@gmail.com ? so in the login page you will give your.name as your Username, right? But instead try “yourname” as username… Gmail allows you to login.[more] Surprised? Gmail ignores dots in email ids a.b.c@gmail.com is same as abc@gmail.com If you receive an email ignoring dots in your gmail id then it will show as above… More in this link… But there is a small problem in this.. you register in a third party site with “.” in your Gmail id and after some time you decide to ignore dots in your email, now you try to use the third party site’s forgot password option and if you didn’t remember that you have used “.” when you registered, then you may lose your account in the site. This is because for other sites your.name@gmail.com is different from yourname@gmail.com.