Learn More about JUST CODE at Telerik site
In this post, let us have a look on different ways of error inspection using Telerik Just Code. List of inspection can be performed are as follows.
- Identical if and else clauses
- Obsolete casts
- Empty statements
- Assignments with no effect
- Unused private members
- Unused parameters
- Unused variables
- Unused namespaces
- Unreachable statements
I have a very simple code as below,
And if you would see carefully there is a compile time error in the code because of string value assignment in integer type variable.
Telerik JUST CODE reports above error in many developer friendly ways and at the same time helps developers to resolve the issue.
If you are having JUST CODE installed you will get error messages in different ways. JUST CODE provides inspection details in many ways. They are listed as below,
ToolTip below the highlighted code
If you hover over line causing error, in the tooltip you will get the error message.
ToolTip in the Marker Bar
At the right hand side you will find Marker war.
If you hover over marker you will get the error detail as below,
In Error List
At the bottom you will find r error list. All the error and warning will be listed there.
In next post we will see some other features of Just Code. I hope this post was useful. Thanks for reading.
Follow @debug_mode
Discussion
Trackbacks/Pingbacks
Pingback: Dew Drop – August 13, 2011 | Alvin Ashcraft's Morning Dew - August 14, 2011
Pingback: DotNetShoutout - August 15, 2011
Pingback: Link Resource # 16 : August 12 – August 15 « Dactylonomy of Web Resource - August 15, 2011
Pingback: Code Navigation and Search with Telerik Just Code « DEBUG MODE…… - September 18, 2011
Pingback: Monthly Report August 2011: Total Posts 17 « debug mode…… - December 4, 2011
Pingback: Code analysis using Telerik JustCode « debug mode…… - January 13, 2012