In the end, what I did was change my mailserver settings to disable the catch-all thing and bounce mail back if it didn’t belong to a real account.

It’s one way to deal with it.

In the Metabase.xml file, take off the pdf from the list and compression should work fine for all types listed.

Potentially this may be contributing to your issue.

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

Turn off Compression to a specific file (Download.aspx) while allowing dynamic compression on all other ASPX pages

1. Open IIS manager
2. Navigate to the ASPX file
3. Open the file and make a slight change to the file (for example if anonymous is allowed turn on clear text on the security tab so that the file will be entered as an exception in the metabase for IIS on the site)
4. Open CMD window. Navigate to C:\Inetpub\AdminScripts
5. Run the following commands to turn off compression for that file:

cscript adsutil.vbs set W3SVC/[#]/Root/[PathToFile]/DoStaticCompression False

cscript adsutil.vbs set W3SVC/[#]/Root/[PathToFile]/DoDynamicCompression False

Where [#] equals the “Identifier” of the site in IIS (go to “Web Sites” in IIS Administration and see next to Description in right pane)

And

Where [PathToFile] is the path from the root of your web application to the ASPX (or other file) to turn off compression for.

/Download.aspx/SomeFileName.zip?FileId=[Guid]

We do this header like this so that the browsers get tricked into thinking the extension is .zip and not .ASPX, but the server knows it is executing .ASPX, so it attempts to compress the zipped file, which the browser doesn’t know how to do.

I am attempting to change the compression to not work for that one particular file.

When I compared with XCompress, it did work with the above (similiar type) download code while IIS6 dynamic compression had the issue.

Your article is excellent, and is the only thing I have been able to find regarding how to use satellite assemblies with .NET 2.0. The documentation gap on this is unbelievable. Thank you for posting this!

Anyway, I have been able to follow your example successfully, but have a few follow up questions and was wondering if you can shed any light:

1) I initially ran into problems following your guided steps because I started with an “ASP.NET Web Application” project instead of a “Web Site.” Interestingly enough, if you use an application project, things break down at step #13. The culture sub-directory is not created and the WebLocalization.resources.dll for the culture is not inserted. Any idea why that is (and how to overcome it)? It seems like this must be related to the compilation model for the 2 project types, but I’m not sure.

2) In .NET 1.1, satellite assemblies were a recommended best practice over hitting resource files directly because of possible contention issues with using a file. When using satellite assemblies, they get shadow copied to the GAC which relieves the issue. I am wondering if satellite assemblies are still needed in 2.0 or not? Since nothing in the 2.0 documentation says anything about this, it makes me wonder. If the 2.0 runtime has new functionality built into it to relieve contention problems (specifically on files in the App_GlobalResources and App_LocalResources folders) without using satellite assemblies, the whole process becomes MUCH simpler. Anyway, just wondering if you have any insights.

Thanks in advance for your thoughts,
Mark

1. go to file manager
2. copy the mp3 you want to use as a ringtone (from whereever you store your music files on the phone).
2. open “storage” folder
3. open “application data” folder
4. open “sounds” folder
5. paste the MP3 into the “sounds” folder
6. now go back to “settings” (in the Start menu) and change your ringtone to the MP3. Wa-la!