Friday, September 26, 2008

FireFox easter eggs

Just an easter egg in FireFox 3.0, Type about:robots in its address bar and hit enter



Try about:Mozilla in its address bar you will be presented a red screen with a verse from The Book of Mozilla



hmmm due to the browser wars we got a few easter eggs and many compatibility issues in our web applications.

Thursday, September 25, 2008

Free Sql Server 2008 Ebook - Direct Download

As some of my friends felt bit difficult to make a download of free SQL Server Ebook. I would like to dedicate this direct download link to those who find it difficult to download and those who don't have hotmail ID or Live ID.

Download here:

Tuesday, September 23, 2008

Even Gmail server goes down.

Gmail is no exception from server errors, but it crashed graciously.

Monday, September 22, 2008

Free Microsoft Press E-Book offer

Download Free E-book from Microsoft
You will need to provide your Live Id or Hotmail ID for a registration process before downloading.



Table Of Contents:

Chapter 1: Security and Administration
Chapter 2: Performance
Chapter 3: Type System
Chapter 4: Programmability
Chapter 5: Storage
Chapter 6: Enhancements for High Availability
Chapter 7: Business Intelligence Enhancements

Introducing Microsoft SQL Server 2008
by Peter DeBetta, Greg Low, and Mark Whitehorn
ISBN: 9780735625587

Download From here

Thursday, September 18, 2008

Wednesday, September 17, 2008

SharePoint development VM loves IISReset

When we develop application pages or custom web part development in SharePoint. This requires a lot of IISreset for each and every bit of change in the assembly when we are going to deploy these modified binaries GAC.

IISRESET takes a lot of time instead of that if we recycle the required application pool which is associated to our IIS web application, this will save atleast a minute of dev effort.

This recycling process can be automated by using the following OOB VB script

cscript.exe iisapp.vbs /a SharePointAppPool /r

or
cscript.exe iisapp.vbs /p [Process ID] /r

[Process ID] : This can be obtained just by executing iisapp.vbs in the command line. This will list all the application pools with their process ids

Get more info about IISapp.vbs from Microsoft Technet library

Do you want to recycle all the application pools in your IIS ?

Save the following the VB script to vbs file and replace the MachineName with your Dev machine's name

Set locator = CreateObject("WbemScripting.SWbemLocator")
Set Service = locator.connectserver("MachineName", "root/MicrosoftIISv2")
Set APCollection = Service.InstancesOf("IISApplicationPool")
For Each APInstance In APCollection
APInstance.Recycle
Next

Monday, September 8, 2008

The Last Supper bigggggessst Photo

HAL 9000, an Italian imaging company which recently posted a high resolution of world famous "The Last Supper" photograph in its web site. Watching such a famous painting closer in high definition is quite amazing (People are restricted to watch closer because of the current condition of the photograph, might be 500 years older).

The resolution of the picture is 16 billion pixel (approx), which is 1600 times larger than a picture which is taken by a 10 Mega pixel camera. Image was photographed as 1677 pieces and then electronically assembled by computers. Each piece is 73 Mega byte approx.You can watch the image here


Technical Information:

Image Info:

---------------
Resolution : 16.118.035.591 pixel (172181 x 93611)
Camera : "Nikon D2Xs"
Lens : AF-S Nikkor 600mm f/4D IF-ED II

Computer used for processing
:
---------------------------------------
Processor : Two Quad Core AMD Opteron™ processors
Memory : 16 Gigabyte RAM memory
Storage : 2 Terabyte hard disk space


Watch the video how they did it here

Friday, September 5, 2008

Retrieving the password for IUSR & IWAM accounts

IIS provides  a script file called adsutil.vbs to obtain or set the password for IUSR/IWAM accounts in IIS metabase. Just adding this tip not to forget in future.

More details : http://support.microsoft.com/default.aspx?scid=kb;en-us;297989

SharePoint Page processing model

This is one of the architectural diagram I'm searching for a long time, finally I found it in MSDN


  1. The browser requests a Web page from Microsoft Internet Information Services (IIS).

  2. IIS passes the request to ASP.NET 2.0.

  3. An HttpApplication pipeline is created for the request.

    a. This request will be handled by WSS specific module SPRequestModule

    b. Then the processed request will be handled by WSS specific handler SPHttpHandler.

  4. ASP.NET 2.0 fetches the page via the Windows SharePoint Services 3.03 file provider. ASP.NET passes the URL to the file provider, and the file provider fetches the page and returns the page stream. The Windows SharePoint Services file provider implements caching and reduces round-trips to the database.

  5. ASP.NET loads a Page class, parses the page stream, and finds a reference to the page layout upon which the page is based.

  6. The ASP.NET engine compiles the page stream and stores it in memory.

  7. ASP.NET queries the Windows SharePoint Services file provider for the page layout.

  8. ASP.NET loads the stream for the page layout associated with the current page.

  9. ASP.NET compiles the page layout and stores it in memory. ASP.NET can free this memory later if the system needs memory.

  10. ASP.NET determines the master page for the site and fetches the master page via the Windows SharePoint Services file provider.

  11. ASP.NET compiles the master page and writes to the disk so you never have to recompile the master page unless you modify it.

  12. The page layout runs each control on the page in the context of the page that was requested.

  13. ASP.NET updates the necessary caches.

  14. IIS returns the page to the browser.

The next time the page is requested by the same user or by a different user who has the same permissions to see the page as the first user, page processing is much more efficient:

  1. The browser requests a Web page from IIS.

  2. IIS passes the request to ASP.NET 2.0.

  3. An HTTPApplication pipeline is created for the request and hits the HandleRequest.

  4. ASP.NET uses all the internal caches.

  5. ASP.NET renders the HTML for the controls.

  6. IIS returns the page to the browser.