2. BrowserSwitch : it switched your default browser with a Click
3. Windows Indexing : Make sure you index your entire hard drive so as to make searching easier
4. Dextop Manager : Provides Multiple dextops just like on the Mac
5. Notepad ++
6. Event Viewer
8. Wireshark (Note that fiddler cannot capture the calls from VS , but this guy can)
9. WinMerge : My recent fav tool after the GV release
2. Google Reader
3. Google Bookmark
4. Google Calendar
5. Google News (customized by logging in)
6. YouTube & Viemo (mostly to add videos to watch later category to watch at home)
7. Picassa to share pics
10. Sharepoint 2010
Most of the work in Office is Incremental (heck i made the whole of RFB Tool from scratch with Google doing all the work)…and this is worst as u can find the small snippets and patch the code base….
But this is also the best as if you spend the first 2-3 Nights (that’s the real time i learn anything….aah the silence) debugging the code (http://www.blogger.com/blogger.g?blogID=626020518553429424#editor/target=post;postID=7851608676716244147 )
Then ask questions and First think about how you would solve the same problem and then find answers from the code and then google to find better ways of doing the same things…..
This way you will gain the experience of the code (which is all that P is about) and will also Learn ….
I made it worst, with the Best of intentions.
I innocently thought that i should put a breakpoint in every method (there were around 200 + spread in 7 Projects and 3 Solns) and debug it end to end, i would know everything.
So that’s what i did…Alas, it was spawning threads everywhere and also all senarios never get covered in the firsrt run .. so all i got was frustration…
this was with UNS and so i decided to not do this ever again…
Then with SSD, i followed the right approach…
First i studied the Broad working and flow….
Then i looked into it senario by senario….
This way i did the work i had to do (patching) and also retained much more….
But sadly i haven’t yet gone the Extra mile to learn from the code…..
The best approach in my view would be to learn everything that the code is doing Logically …i.e also knowing WHY it’s doing what it does in Every senario…
This requires desire and time … both of which i have and so i will do this from now on…
1. iis 5.1 on XP is much simpler than iis 7 on the iwin….
2. Note that for all applications, create dummy folders in the webroot. then under that namespace create VDs but always keep the path of the apps, the same as their solution files (wich you should maintain in the VS folder, again under the folder name that represents the app, and in that keep diff versions , bin, backup etc…never leep more copies than necessary)
3. Convert to application is a rookie mistake and always do that first in the props
4. Next mistake is the access in VD section of Props : RULE is to keep all checked and also say : scripts and exec to simplify ur life unless u know y not…
5. in directory security do windoes auth enabled…
6. Another lesson from TUIT is that even after doing all this i get errors… so by hit and try i found that in such cases, open the soln in VS and hose it on the VS Server (by default u should host VS apps in IIS only –unless u want to debug— but then if u want to debug multiple apps, u need to host all on VS but 1 and run all from iis and attach the one to the asp_wp from the VS Debug menu)
Here, my sole aim is to record the lessons in P that i spend all day learning….The only reason that i am sitting here (in office) after hours to record this is that i realize that lessons and oops moments in the office are frequent and varied and can slip out of mind if not consciously recorded or repeated.
The diverse set of technologies i’m working on don’t allow me to repeat most things that i learn, and hence they conveniently enter my left ear and flow through the right one.
Hence i want to do this from now onwards….