Due to some new enhancements in IIS 6.0, users may encounter a significant delay before receiving the content on the page. This can be a great annoyance for the users and prevent them from visiting your site. To eliminate this delay, follow these instructions:
- Copy the following:
Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ASP\Parameters] "DisableLazyContentPropagation"=dword:00000001
- Open Notepad and paste the text.
- Save the text file and rename it to for example “IIS6_Delay_Fix.reg”.
- Merge the file into the registry by double-clicking it.
- Reboot.
Post Comment Now
As an application developper you often need to write some logs for your application, and hopefully there is actually many framework to ease your pain: Log4net, Entlib Logging Application Block, etc. But when it come to read those logs, extract statistics or to do some alert or action on them, things become harder. Actually a free command line tool from Microsoft name LogParser and it is quite awesome: you can query any log and data sources (database, event log, iis logs, file system, registry, etc.) with a complexe SQL query (I mean with functions, group by, etc.).
On the down side, using it from the command line become quickly boring as you need to type your sql query in a DOS prompt. As we failed to find any intuitive GUI for logParser, we just start to build our own, by assembling the following pieces: the logparser engine, a “visual studio” like MDI dockable interface, syntax highlighting…

Some other notes…
Do an insert to a db with the log parser utility from IIS resource toolkit:
C:\Program Files\IIS Resources\Log Parser>logparser "SELECT date, time, c-ip, cs -uri-stem, cs-uri-query, cs-username FROM C:\WINDOWS\system32\LogFiles\W3SVC201 2337366\*.log TO test2 WHERE SUBSTR( cs-uri-stem, LAST_INDEX_OF(cs-uri-stem,'.'), STRLEN(cs-uri-stem)) = '.asp'" -i:IISW3C -o:SQL -server:teas-db1 -usern ame:sa -password:"foobar" -driver:"SQL Server" -database:kevin_temp -createtable:ON
Post Comment Now
Changing the listening port for Remote Desktop can have its advantages, particularly if you are remoting in from behind a firewall. Since a lot of public firewalls (hotels, airports, etc.) block most ports except for those used for email and internet access, using the default settings for Remote Desktop will not work on them. As long as you are not remoting into a machine that is serving secure sites, you can change the listening port to 443 and access your machine from almost anywhere. Just follow these instructions:1. Open Regedit.
2. Navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp
.
3. Find the dword value named PortNumber.
4. Change the value to 443.
5. Close Regedit and reboot.
To connect, open the remote client and type in the hostname or address followed by :443.
Post Comment Now
Open notepad and paste the following text (you can get to notepad easily by going to Start -> Run -> type ‘notepad’ -> Ok)…
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{20D04FE0-3AEA-1069-A2D8-08002B30309D}\shell\Control Panel\command]
@=”rundll32.exe shell32.dll,Control_RunDLL”[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{20D04FE0-3AEA-1069-A2D8-08002B30309D}\shell\DevMgr]
@=”Device Manager”[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{20D04FE0-3AEA-1069-A2D8-08002B30309D}\shell\DevMgr\command]
@=”mmc.exe %%SYSTEMDRIVE%%\\WINDOWS\\SYSTEM32\\devmgmt.msc”[HKEY_CLASSES_ROOT\CLSID\{20D04FE0-3AEA-1069-A2D8-08002B30309D}\shell\Regedit]
[HKEY_CLASSES_ROOT\CLSID\{20D04FE0-3AEA-1069-A2D8-08002B30309D}\shell\Regedit\command]
@=”regedit.exe”[HKEY_CLASSES_ROOT\CLSID\{20D04FE0-3AEA-1069-A2D8-08002B30309D}\shell\Command Prompt]
[HKEY_CLASSES_ROOT\CLSID\{20D04FE0-3AEA-1069-A2D8-08002B30309D}\shell\Command Prompt\command]
Save the file as my_computer_context_menu.reg to the desktop. Double click my_computer_context_menu.reg it to intall this your registry. You are done. Test to see if the new items appear in the context menu by right clicking My Computer. If so, you have done it correctly and may delete my_computer_context_menu.reg from your desktop.
Post Comment Now

