Vaibhav Mayee's Blog

Hi Geek friends and Non Geeks Today with the memory storage industry revolutionized the sizes in which they come , you can see a 80 GB pen drive smaller than your thumb. The Pen drives have revolutionized the way we deal with huge amount of data. Right from the swanky key chain to the pendant on your neck , Pen drives have become more than data storage medium , they have become as a fashion statement In this tutorial at Seek2Geek , we teach you how to give your Pen drive an extra interior touch . We will be teaching you to pick up an icon and a wallpaper and apply them as your background 1) Download a .ICO file for your icon from www.iconarchive.com and also choose a wallpaper for it 2)Now in the Root directory of the Pen drive , create a notepad file and type in this code [Autorun] icon=boy.ico where fish.ico is the file I chose , Put in your file name instead of boy.ico 3)Save this file as "Autorun.inf". Click on Save as and do this . Remember to put in the quotes too 4) No

Follow me on twitter http://twitter.com/vaibhavmayee to see my madness

* Viewstate * Session Variables * Application Variables * Cache * Cookies Now the question arises that when to use what? 1- Viewstate Viewstate is a hidden fields in an ASP.NET page, contains state of those controls on a page whose “EnableViewstate” property is “true”. You can also explicitly add values in it, on an ASP.NET page like: Viewstate.Add( “TotalStudents”, “87″ ); Viewstate should be used when you want to save a value between different roundtrips of a single page as viewstate of a page is not accessible by another page. Because Viewstate renders with the page, it consumes bandwidth, so be careful to use it in applications to be run on low bandwidth. 2- Session Variable Session variables are usually the most commonly used. When a user visits a site, it’s sessions starts and when the user become idle or leave the site, the session ends. Session variables should be used to save and retrieve user specific information required on multiple pages. Session variables consu

Software doesn't just appear on the shelves by magic. That program shrink-wrapped inside the box along with the indecipherable manual and 12-paragraph disclaimer notice actually came to you by way of an elaborate path, through the most rigid quality control on the planet. Here, shared for the first time with the general public, are the inside details of the program development cycle. Programmer produces code he believes is bug-free. Product is tested. 20 bugs are found. Programmer fixes 10 of the bugs and explains to the testing department that the other 10 aren't really bugs. Testing department finds that five of the fixes didn't work and discovers 15 new bugs. See 3. See 4. See 5. See 6. See 7. See 8. Due to marketing pressure and an extremely pre-mature product announcement based on overly-optimistic programming schedule, the product is released. Users find 137 new bugs. Original programmer, having cashed his royalty check, is nowhe