It was a nice meeting with Deepak, on last friday at Microsoft IBDC. Most of the attendies are core operating members for MUGH.net (Microsoft User Group Hyderabad). We had some cool photo sessions as well :)
Today, we have launched www.mugh.net (Microsoft User Group, Hyderabad).
As of today we have got nearly 900 members from various product groups including Windows Installer 2.0.
The cool news is Microsoft India will be going extend it's support to MUGH in various ways. Thanks to Deepak.
Deepak is the guy who drives Microsoft MVP program and makes the community to enjoy the MS benefits at his best.
Today's agenda for Launch
01. www.mugh.net launch and Introduction by Jaffer Mirza
02. Microsoft MVPs - Curtain Raiser by Geetesh
03. Longhorn - An Introduction for next generation OS by Tammem
04. Weblogs - New face of Developer Information by Me ;)
05. Microsoft Recognition for Active participants in MUGH - Gift presentation
06. Inauguration of MUGH Library
Intelligroup is sponsoring the Venue for MUGH, Thanks Intelli...
Cool ! Yesterday I got my PDC bits DVD box (Whidbey, LH).
It took around 45 minutes to install on a new partition of my XP box. [2.4 Ghz, 512 MB DDR, 64 MB GeForce II ]
I got to wait 2 minutes to see my task bar and side bar appeared on screen. :). I was able to do 100% hardware configuration except my cabel modem :(.
It was configured as it was in XP partition, but no way to connect to internet. Still I have to install Whidbey and LH SDK to play around XAML and other stuff.
Hope I could post some LH posts here ;)
May be this is an off-blog topic, but I am sure, this is one of the popular news in India today.
[ Rediff ] India won a remarkable game of cricket at the Adelaide Oval by four wickets. Rahul Dravid top-scored the run chase with 72 runs and aggregated 305 runs for the Test. Quite fittingly he bagged the man of the match award.
How To: HTTP Compression in IIS 6.0
Source: The .NET Guy’s Web log
1. Allow the compression ISAPI to run
IIS 6's new security system prohibits ISAPI DLLs from running by default, so you need to tell IIS 6 that it's okay to let the compression ISAPI DLL run.
01. Open the IIS admin tool (inetmgr); drill into your server, and right-click on "Web Service Extensions".
02. Choose "Add a new web service extension". For the extension name, use whatever you want to identify it in the list (I used "HTTP Compression Extension").
03. You need to add a single required file, which is \Windows\System32\inetsrv\gzip.dll, the ISAPI responsible for doing gzip and deflate compression.
04. Check the "Set extension status to allowed", then click OK.
05. You should have a new web service extension in your list called "HTTP Compression" (or whatever you named it), and it should have a status of "Allowed".
2. Select compressible content
IIS 6's compression system only compresses a very limited set of content. You need to enable compression for the appropriate file extensions (specifically, .aspx files for your ASP.NET pages, and perhaps any static content you want compressed as well).
01. You're going to edit the Metabase. To do this, you first need to shut down IIS.
02. In the IIS admin tool, right click on your server name in the left panel, and choose All Tasks -> Restart IIS.
03. On the restart dialog, choose "Stop internet services" and click OK. When IIS is shut down, you'll need to edit \Windows\System32\inetsrv\MetaBase.xml (make a backup first!).
04. Search for "IIsCompressionScheme". There will be two XML elements, one for deflate and one for gzip. Both elements have properties called HcFileExtensions and HcScriptFileExtensions. These contain a space-delimited list of file extension for compressible content.
05. At a bare minimum, you'll need to add “aspx”, “ascx” to the HcScriptFileExtensions list. Note that if the properties are left blank, then all content, regardless of file extension, will be compressed.
1. Make sure that IIS process user account has required privileges on the compression temp folder.
2. Do never try to compress image types (jpg, gif, png, tiff etc…)
“General Network Error. Please check your network documentation”.
I think this is one of the most weird, clue-less error that every typical ADO.NET Developer get.
I get the same error (randomly) with Microsoft Data Access Application Blocks (DAAB 2.0 for .NET 1.1). I found this error is some how realted to the Command execution behavior of DAAB.
I googled for 10 mins, and got redirected to some alien worlds of database issues. The actual fix/work around is related to DAAB's command execution. I made Command.CommandTimeOut = 60 (default is 0). Thats it ! The problem is solved.
I hope this issue is fixed in 3.0, I still need to check the source again.
20. "That's weird...."
19. "It's never done that before..."
18. "It worked yesterday."
17. "How it that possible?"
16. "It must be a hardware problem."
15. "What did you type in wrong to get it to crash?"
14. "There is something funky in your data."
13. "I haven't touched that module in weeks!"
12. "You must have the wrong version."
11. "It's just some unlucky coincidence."
10. "I can't test everything!"
9. "THIS can't be the source of THAT."
8. "It works, but it hasn't been tested."
7. "Somebody must have changed my code."
6. "Did you check for a virus on your system?"
5. "Even though it doesn't work, how does it feel?"
4. "You can't use that version on your system."
3. "Why do you want to do it that way?"
2. "Where were you when the program blew up?"
And the Number One Reply by Programmers when their program doesn't work:
1. "It works on my machine."
Oops! This is too much of Pro-Activeness, but of no use anyway, when it comes to product support and quality.
I think most of the longhorn features are still in stuido level, and never been exposed to public. In that case these pirates will make money out of selling garbage to customers. There are some cases where companies tried to sell Linux with XP shell (lycoris i think...), but not able to get stability over the product market.
Well, Today I hit a Century with this posting. ;)
Here is the answer from .NET Guy
Good and worth of reading.