Friday, April 8, 2011

Historical Debugging (Intellitrace) on Visual Studio 2010 Ultimate Part-1

Visual studio 2010 Ultimate comes with one of most interesting function Historical Debugging which will change the way you debug. Let’s see what is Historical Debugging and How its works.

How historical Debugging works?

As as developer you have already faced some situations like Your tester reports a bug and you are not able to reproduce that bug in your local environment or you have very long steps to reproduce it and sometimes it reproduces under special condition and some times it does not. At that time this historical features comes into existence. With Visual Studio 2010 Ultimate Microsoft has introduced a new debugging tool intellitrace. It keeps a trace of important points of your program and its allow you to go back at that time to see what happened at that time. Isn’t that cool? that is just like rewinding your recording to edit your video.

How we can enable Intellitrace on Visual Studio 2010 ?

To enable it you need to go to the Tool->Options->Intellitrace->General just like following.

IntelliTracedialog in Visual Studio Dialog

There is a check box called ‘Enable Intellitrace’. You need to check that checkbox to enable IntelliTrace (Historical Debugging). There are two radio buttons

1) IntelliTrace Event Only- This option will enable historical debugging for the events only. So it will only keep track of events only. Not all the parts of code.

2) Intellitrace events and Call Information: This option will enable historical debugging for events and inner called like method and other stuff. It records method level call but due to that your application performance can be effected. You will not get high performance from your application.

There are some advance options are also given in the options dialog box like following when you click advance in above dialog.

Advance of historical debugging in advnace.

Here you can specify the location of the IntelliTrace Recording and Maximum size of disk space for each recording.

In Intellitrace Events options you can specify which kind of events you want to trace. I have enabled it on ASP.NET Project so I have options for ASP.NET and ADO.NET Enabled by default like following. But You can select events like file,Environment events and lots of options are available so you can specify that as per your requirement like following.

IntelliTraceEventsTypes

In Modules options you can select for which system modules you want to enable intellitrace if You can also add your own modules here with string pattern like following.

IntelliTraceModule

So,Now we all set for the Historical debugging(IntelliTrace) in Next Post I will demonstrate how historical debugging will work. Hope you liked it.. Stay tuned for more..

Shout it
kick it on DotNetKicks.com
Share:
Thursday, April 7, 2011

Important milestone achieved. This is my 400th Blog post

When I started this blog before four Years I was not serious about blogging. I was just started this blog to register domain against my name. After a while I was inspired by great community bloggers like ScottGu,Pinal Dave,Jacob Sebastian and some other friends like Vivek Patel. Then I started blogging seriously but at that time I was not aware of how to blog. I was just writing whatever I like or whatever I have found. I have no idea of syntax highlighting, blogging technique and SEO. Day by day I learned a lot and started working on things and as a Result of it Today I got 400th Blog post on my this blog.

I would like to thanks each and every reader and my fellow community blogger to helping me achieve this. Without them I could not achieve this.

Still I have seen there are lots of exceptional developers who are not writing blog. I would like to recommend that please read my blog post “Why a developer should blog?”. I must say once again that If you are doing great work then you should share it with the community and get their views of what you are doing.

On this occasion I would love to share some thoughts on blogging like following.
  1. Do not write blog to increase your blog post or get any recognition . Instead of this write your blog for self pride and community.
  2. Do no worry about who is going to read this blog. How you can increase your readers instead of that keep writing blogs and one day you will achieve whatever you like to do. Read your blog post once you posted it on your blog and it will give you great joy and satisfaction.
  3. keep inspired by your fellow community bloggers and try to improve your blogging.
  4. If you are technical blogger then Keep your post to give a complete solution of a problem because if readers will not get complete solution then they got frustrated with you.
  5. Learn and explore new things and share you experience on you blog.
  6. Always be good listener and you will learn a lot.
  7. Nobody knows everything. We all are learning everyday something so keep doing mistakes but learn from those mistakes and try to not repeat the same mistakes again.
Statistics of my blog:

On this occasion I would like to share my statistics of blog below are my statistics of blogStastics

Once again I would like to thank the readers and all the fellow bloggers without them it was not possible to achieve this. Keep blogging.. Stay tuned for more..

Shout it
Share:

Checking whether page is secure or not in ASP.NET or JavaScript

Recently in one the project we require to check whether page is secure or not as we are going to open a new popup window from that page and that why we need to pass https protocol if we have that page secure. I have search lots of things on internet and I have found following ways of finding whether page is secure or not in ASP.NET or JavaScript.

In ASP.NET There are two way of doing it. Either we can use current request to check whether it is secured or not or we can use server variables to check whether it it secure or not just like following.

HttpContext.Current.Request.IsSecureConnection
Here in above code If this returns true then Page is secured otherwise it is not Or you can use following server variable to check the protocol.
Request.ServerVariables["SERVER_PROTOCOL"];
In JavaScript you can document.location.protocol to check whether page is secure or not. Just like following.
document.location.protocol=='https:'
So you can see its very easy to check whether page is secure or not. Hope you liked it… Stay tuned for more..
Shout it
kick it on DotNetKicks.com
Share:

Support this blog-Buy me a coffee

Buy me a coffeeBuy me a coffee
Search This Blog
Subscribe to my blog

  

My Mvp Profile
Follow us on facebook
Blog Archive
Total Pageviews