Tuesday, January 18, 2005

"Queen of Hill Stations" - OOty Trip writeup

It is really a long weekend, its called "Pongal" in Tamilnadu and "sankaranthi" in Karnataka.
Whatever it is named, we have holidays for 3 days.
Visiting the home town is a common scene for outstation ppl like me, but am not like that, I love travel , adventure and Driving!!!!!!!, Ameen khan another room mate also form chennai, we r on similar wavelengths, he too loves travel , adventure and driving, getting people with similar thoughts seems a bit difficult.

The plan to make use of this holidays was charted out 2 weeks before and my friend suggested Ooty!!!!!!!!
Ahhhh what a place to be in, at this point of the year, its not an off-season nor a peak-season, its called a second season, no huge rush nor any harsh rains.

Our plans started taking up shape as we neared the D-day.
We a group of 9 guys started of in 5 bikes, mine is a black victor, a CBZ, pulsar, yam135, and a black fiero started from bangalore on 14-Jan-2005, Friday.
My bike has completed its 6000 and its the first long trip above 250 kms at-a-stretch ride, and I was determined to get to know its full potential in the winding 36 hairpin bends of ooty.

Our actual plan was to start at 5:00Am, myself and ameen khan were on the dot, picked up rajesh (on his pulsar) from indranagar, went to koramangala and picked up 2 more guys mayank and gaurav.
Headed to banshankari (opp to family mart) this is our proposed meeting point to start the journey, Sudheep (CBZ) and abhijeet r still in their house in cox town and Kris (yam135) still not to be found.
Atlast we found the 3 guys turning in at 6:30Am.
Without wasting a second, we started of on the kanakapura road, ameen and gaurav on ameens fiero, myself and kiran on my Victor.
We were heading for quite a distance and found the other 3 bikes missing form the vision, so was waiting near a tree, we got a call form kris and felt sorry to hear Kris bike going flat.
We found a puncture shop near the tree and informed them to get the wheel, rajesh had removed the wheel by then and got it to the shop, got the tube back into shape in half an hour,
It was a nail a really big nail that was in the tyre.
It was around 8:00Am we again started the trip form the kanakapura road.
Reached kanakapura, had our breakfast there and headed straight to mysore via mallavalli.

From mysore we headed straight to Ooty road via Masinagudi, bandipur mudumalai.
Before entering Bandipur, we spotted a Resort (nilgiris resort), the food was awesome, had a south indian style meals, rested for some 15 mins and started our journey again into the jungle roads.
The jungle stretch was the ultimate riding, we spotted a lot of Deers and elephants on the way
The next awesome road was after the mudumalai jungles, the road was a straight layer of bitumen, it seemed as if it was freshly done.

The major Fun part of the steep ascend in the nilgiri hills was about to start, we encountered the first hairpin bend, the winding ride sent a chill through the spine, we stopped at every hairpin joint to capture the beauty of nature, also we cant count the number of tea's that we had on the way, we havent had so much in our life time, wherever we find a tea shop, the engines would come to a halt, it seemed as if the engines started doin this automatically.

Reached ooty at 5:00pm, rode upto our hotel in charring cross (Hotel Glanton Manor), we booked the rooms a week in advance, and we had a warm welcome from the hotel with 1 big room for 6 people and a another small room for 3 people.
We had a good sleep on friday night, woke up at 7:00 next morning on Saturday, visited parsons valley dam, pykara and other places.

The places were exciting and am falling short of words to describe the scenic beauty.
We started or journey back to bangalore on sunday and reached bangalore at 6:00Pm.

In totality the trip was an exciting one with 9 guys and 5 bikes roaring the roads.

Tuesday, January 11, 2005

OOOOTY Bash..........

A sudden plan to go to ooty was planned for the 14th of Jan 2005, 8 guys form HP and myself, all having a long weekend, dosent do justice to it, if we were to waste them sitting in our homes like a couch potato.

So why not plan a trip, a long trip, definitely 300Kms is not long, but is definitely long going by Two wheelers.

9 ppl, 5 bikes, am sure the trip is gonna be awesome XP for all...........
Couple of them are my old frnds, and i have some new faces to get acquainted.......

1 more to the team should make it 10, else there will be a bike goin all alone (hoping i can pick up some chick on the Way).

Rest of the write up after the trip......

Unexpected Errors in Managed Applications

This Article features "handlinh Unexpected errors in managed applications.
Click on the link above to Read more................

In this installment of the .NET column I am going to present a handful of tips for dealing with unexpected errors. While it is common practice to catch exceptions to deal with expected failure cases, it is also common for managed applications to encounter errors for which the application is completely unprepared. In an ideal world you will establish clear policies for how your application discovers and responds to unhandled exceptions, reduced security permissions, and other related edge-cases, but in practice these are often overlooked.
Error handling infrastructure is a deceptively complex topic, and you can easily be overwhelmed by details, so I'll address a few relatively simple operations that are broadly applicable for dealing with unexpected err....................................................
http://msdn.microsoft.com/msdnmag/issues/04/06/NET/default.aspx

Monday, January 10, 2005

FxCop is a code analysis tool that checks .NET ............

FxCop is a code analysis tool that checks .NET managed code assemblies for conformance to the Microsoft .NET Framework Design Guidelines.
It uses reflection, MSIL parsing, and callgraph analysis to inspect assemblies for more than 200 defects in the following areas:

Library design
Localization
Naming conventions
Performance
Security

FxCop includes both GUI and command line versions of the tool, as well as an SDK to create custom rules.

Download FxCop 1.312
FxCop for .Net 1.1
FxCop self-extracting installer (3.7 MB, 12/09/04)
FxCop .msi installer (3.8 MB, 12/09/04)

Wednesday, January 05, 2005

Microsoft .NET Application Blocks


.NET Application Blocks are distinct pieces of code, created by the
Microsoft Patterns and Practices Team, that demonstrate the best practices on how to accomplish a specific task using .NET. They are ready made code that you can use/extend to make your lives a WHOLE lot simpler.
I like them as they are extensively tested and reviewed (which hopefully minimizes security issues).


User Interface Processes Application Block v 2.0

http://www.microsoft.com/downloads/details.aspx?FamilyId=98C6CC9D-88E1-4490-8BD6-78092A0F084E&displaylang=en
The User Interface Process Application Block provides a simple yet extensible framework for developing user interface processes. It is designed to abstract the control flow and state management out of the user interface layer into a user interface process layer.

Smart Client Offline Application Block
http://www.microsoft.com/downloads/details.aspx?FamilyId=BD864EB5-56B3-43A5-A964-6F23566DF0AB&displaylang=en
The Offline Application Block, is intended to serve as an architectural model for developers who want to add offline capabilities to their smart client applications.

Authorization and Profile Application Block
http://www.microsoft.com/downloads/details.aspx?familyid=ba983ad5-e74f-4be9-b146-9d2d2c6f8e81&displaylang=en
The Authorization and Profile Application Block provides you with an infrastructure for role-based authorization and access to profile information.

Logging Application Block
http://www.microsoft.com/downloads/details.aspx?FamilyId=24F61845-E56C-42D6-BBD5-29F0D5CD7F65&displaylang=en
This block is a reusable code component that uses the Microsoft Enterprise Instrumentation Framework (EIF) and the Microsoft .NET Framework to help you design instrumented applications.

Aggregation Application Block
http://microsoft.com/downloads/details.aspx?FamilyId=9058F345-E5FE-42FC-B40B-14EBDD182F48&displaylang=en
The Aggregation Application Block is a .NET Framework extension that allows you to easily manage and coalesce information from various service providers and other systems and present that information to users.

Caching Application Block
http://microsoft.com/downloads/details.aspx?FamilyId=B55164C9-94C8-4077-AA29-AFE4074746DE&displaylang=en
The Caching Application Block has been designed to encapsulate Microsoft's recommended best practices for caching in .NET applications

Configuration Management Application Block
http://www.microsoft.com/downloads/details.aspx?familyid=85cb1c53-8ca7-4a92-85e3-e4795bd27feb
The Configuration Management Application Block is an easy to use mechanism through which you can read and write application configuration data.

Data Access Application Block v 2.0
http://www.microsoft.com/downloads/details.aspx?FamilyId=F63D1F0A-9877-4A7B-88EC-0426B48DF275&displaylang=en
The Data Access Application Block encapsulates performance and resource management best practices and can easily be used as a building block in your own .NET application. If you use it, you will reduce the amount of custom code you need to create, test and maintain.

Persistent Asynchronous Invocation Application Block
http://microsoft.com/downloads/details.aspx?FamilyId=794EC811-B5EA-46AE-BAA4-69A3DEADD38E&displaylang=en
The Microsoft Asynchronous Invocation Application Block manages asynchronous communication between a Web client and one or more foreign service providers (FSP).

Updater Application Block
http://www.microsoft.com/downloads/details.aspx?familyid=c6c17f3a-d957-4b17-9b97-296fb4927c30
In medium to large organizations, it is common to want to keep all instances of a desktop application up to date with the latest version of executables, libraries, and other files. The Updater Application Block provides an extensible framework that companies can use to create updateable applications

Exception Management Application Block
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=8CA8EB6E-6F4A-43DF-ADEB-8F22CA173E02
The Exception Management Application Block provides a simple yet extensible framework for handling exceptions. With a single line of application code you can easily log exception information to the Event Log or extend it by creating your own components that log exception details to other data sources or notify operators, without affecting your application code. The Exception Management Application Block can easily be used as a building block in your own .NET application.

Sunday, January 02, 2005


Hi...Guys this is meee... Posted by Hello

My Site is Up...........

I wanted to host my site on new year 2005, after burning some midnight Oil for a couple of days before new year......
finally got my site revamped and have hosted it with Brinkster.

Now my site has some cool and new looks.......


Windows Service Administration with ASP.NET

Just came across a good blog, while searching for an idea to implement something in remoting for my project.

http://dotnetjunkies.com/WebLog/bsblog/archive/2003/11/12/3504.aspx

Wishing all a Happy New Year 2005

Hi all......

With a New Year tats not too impressive nor festive, dur to the recent tsunami hits.
Not in a mood to Party.........

Just slept in my house, after wishing my frnds a happy new year 2005 at 12:00