In this blog post I am going to explain how you can customize the complete view of the debugging window during debugging of application. By complete view means, where you can add own Properties, can customize the result, manipulate the data, hide properties which may not need during debugging etc. In one of my previous blog post, I have explained how we can customize the view of the debugging windows using DebuggerBrowseable and DebuggerDisplay attributes over Few Tips on Customizing Debugging Window View in Visual Studio . But, both these two attributes are limited to customize the view for a specific class and they can only show you the information for the particular class members . In this blog post you will see how we can create new view for some existing debugging view using “DebuggerTypeProxy” attributes. From the below snaps you can understand what kind of customization we can do inside a debugging window.
I have just encountered one issue while start the debugging one of my Silverlight 4 application. Silverlight 4.0 with VS 2010 was working fine few weeks back, but today when I started debugging to test one of my application, I got the error message as below.
I thought, It may be the problem with the Silverlight version which is selected for this project. I checked the Silvelight “Target Silverlight Version” from the Project Properties. But the Silvelight version was correct.
Published Date : September 12, 2010
Published Date : September 14, 2010
Published Date : September 22, 2010
Published Date : September 24, 2010
Published Date : September 19, 2010
Published Date : September 7, 2010
If you want to check all previous Weekly Archives, Please read https://abhijitjana.net/blogbox/ Section.
ASP.NET Tree view control rendered as HTML Table – TR –TD elements. Each of the node are been represented as hyperlinks. Some times you may not want that fields as hyperlink and you want to be those nodes should be represent as static text. Many of the developer did the same using font style or css style change of the node, but it can be done very easily. In this small blog post I am going to describe how you can represent a tree view node as simple text instead of hyperlink.
This can be done very easily using Tree Nodes, SelectionAction properties. SelectionAction having 4 different values, they are.
Select is the default option which marked node as hyperlinked and on selection of the node, it raised SelectedNodeChanged event. For Expand Option, TreeNodeExpanded event will be raised while expanding the node. “SelectExpand” raised both the SelectedNodeChanged and TreeNodeExpanded events. Now if you don’t want to make the node as simple text, just change the SelectionAction properties to “None”.
In my few previous blog post I have explained how we can customize the Debugging windows view during debugging of application using “DebuggerBrowseable “ attributes and “DebuggerDisplay” , then I have also explained use of “DubuggerHidden” attribute which tells the Visual Studio debugger that the method is hidden from the debugging process and while debugging. In this blog post I am going to explain one similar features of “DebuggerHidden” attributes, named “DebuggerStepThrough”
Marking a piece of code using DebuggerStepThrough attribute tells the Visual Studio debugger that, the code block will be stepped over from debugging process. you can mark methods, properties with DebuggerStepThrough attributes where you don’t want to stop your code to break.
If there is any break point inside a code section which is marked as “DebuggerStepThrough” attributes, that code block will be marked as “[External code]” in stack Trace. Where as “Debugger hidden” attributes didn’t marked is External code.
Today I have given an Online session on “ASP.NET 4.0 – In Depth” with Abhishek in a community event organized by DotNetFunda.Com. Thanks to all the attendees. As we were running out of time, we will continue the same in a different session on rest of the topic. All the nominated users will get an email for next session details.
Things that we have covered already :
- Basic Introduction of ASP.NET 4.0 Features
- Visual Studio 2010 Enhancement Session for ASP.NET 4.0 (With Demo)
- Server Control Enhancements (With Demo)
- Search Engine Optimization (With Demo)
Whatever we have covered till now, ready to download
We have lots of things to cover and probably we will fix a time later in the up coming weekends and update you the same.
Below topics we will cover in out next sessions
1. State Management improvement in ASP.NET 4.0 ( With Demo)
2. Deployment in ASP.NET 4.0 ( with Demo )
3. Client Side improvement ( With Demo )
4. Dynamic Data ( With Demo)
Apart from those topic I will discuss few tips and tricks of ASP.NET 4.0
We will be update soon with our next session date and time. Thanks again for joining.
“Track Change” one of the best interesting features in visual studio which indicates the code changes with a color indicator at the beginning of the line. Generally we know about the two color indicator “Green” and “Yellow” which are used indicting the color change till VS 2008 along with those VS 2010 introduced another new color “Orange” which indicates some additional track change for undoing file after save. In this blog post I am going to explain how those color indicator helps developers to track the code changes.
In Visual Studio 2010, there is three color indicator
This color indication has newly introduced in VS 2010. This color will come when user does an undo after a save operation for that current file. Orange color indicates that current changed line is different from the saved version of the file.
DubuggerHidden attribute tells the Visual Studio debugger that the method is hidden from the debugging process and while debugging. This is quite helpful when you don’t want to go to stepping inside of a method while debugging.
When you mark a method with DebuggerHidden() attributes, It’s explicitly tells the debugger not to step inside of that methods and no break point will be hit over that method. Now I am going to explain the same using a Example with Intellitrace debugging.
I will be speaking in a .NET Community session organized by http://dotnetfunda.com on ASP.NET 4.0 . Below is the more details about the session
ASP.NET 4.0 introduces number of features that improve the core ASP.NET functionality and many changes that allow developers to have a strong controls over the application. These enhanced features makes ASP.NET 4.0 more effective for the web developer than the already existing versions of ASP.NET.
The agenda of this session :
- What’s New in ASP.NET 4.0
- Improvement in Visual Studio 2010 for web development
- Empty Website project and Cleaner Web.Config
- MetaKeyword and MetaDescription enhancements
- Controlling ViewState mechanism
- Controlling ClientID generation for asp.net controls
- CompressionEnabled Session
- CSS Improvements and CSS Friendly Menu Control
- ListView rendering mechanism, Enhancement in Listview control
- Enhancement in RadioButtonList and CheckBoxList
- SEO Friendly URL (Web Form Routing)
- Permanent Redirection mechanism
- Improvements in Code Expressions
- Overview of Dynamic data
- Caching mechanism (Output Caching, Object caching etc.)
- ASP.NET Applications / Database deployment.
- Q & A
Scheduled Date: 19-Sep-2010 (Sunday )
Scheduled Time: 2.00 PM to 4.30 PM
Live meeting URL: https://www.livemeeting.com/cc/mvp/
Is Paid?: No, It’s FREE Session
Is Registration required ? Yes . Please register here http://bit.ly/d6aVYM .
Disclaimer : https://abhijitjana.net/disclaimer/
Published Date : August 29, 2010
2. IIS Articles Archives
Published Date : September 1, 2010
Published Date: September 3, 2010
If you want to check all previous Weekly Archive, Please read https://abhijitjana.net/blogbox/ Section.
In this post I have explained how you can use Obsolete attributes to mark some methods which are not no longer in used or may be remove in future release of the class. During the development cycle we may need to change the name or declaration of certain methods which may be using by some other developers. In this case if you changed the name or declaration of that method, application may crash in different point of times as it’s being used by other developer in the application. In this case you can use System.ObsoleteAttributes class to generate compiler warning and indicate the method as Obsolete.
In this blog post I have going to list out all of my IIS articles that I have published over last few years. Why I am going to do such post ? Because, I have been asked many question on IIS and different debugging options related with IIS and ASP.NET Applications by many readers. Many times I have had given reference of my different articles. This post will be the single reference for all of those articles. In this blog post I have given link and small overview of all of my IIS articles, so that I can refer a single articles to who ever wants to learn about IIS.
This article describes details of IIS configuration, Virtual Directory creation, Application Pool Creation, Application Pool settings, IIS Request processing for ASP.NET .