Enable flash .flv video streaming in with IIS / ASP.NET

Enable flash .flv video streaming in with IIS / ASP.NET: 1) Adding .FLV MIME Type in IIS 2) FLV Flash video streaming with ASP.NET 2.0, IIS and HTTP handler

Funny automatic translation (English to Russian):

Original: ThreadPoolSynchronizer marshals all calls to a custom thread pool, where the calls are first queued up, then multiplexed on the available threads. The size of the pool is provided as a construction parameter. If the pool is maxed out, the call will be pending in the queue until a thread is available. You can also provide a pool name (which will be the prefix of the name of the threads in the pool). Disposing or closing ThreadPoolSynchronizer kills all threads in the pool gracefully... Translated: ThreadPoolSynchronizer маршалы все звонит таможенному бассейну нитки, где призывы сначала стоятся в очереди, тогда multiplexed на доступных нитках. Размер бассейна обеспечивается в качестве строительного параметра. Если бассейн maxed, призыв будет находящийся на рассмотрении в очереди прежде чем нитка имеется в распоряжении. Вы можете также обеспечить имя бассейна (который будет префикс имени ниток в бассейне). Размещая или закрытие ThreadPoolSynchronizer убивает все нитки в бассейне грациозно...

Redistributable installation of Microsoft .NET framework 3.0 SP 1

Somehow there are no direct link and installation instructions for the .NET framework 3.0 SP 1 on MS site. Here is how to get it: 1) Make sure .NET 2.0 SP 1 is installed. 2) Get redistributable install of .NET 3.0 SP 1 from here: http://download.microsoft.com/download/8/F/E/8FEEE89D-9E4F-4BA3-993E-0FFEA8E21E1B/NetFx30SP1_x86.exe 3) You may need to install XPSEPSC before installation of .NET 3.0 SP 1. Get it here: http://download.microsoft.com/download/8/D/4/8D4C4B2F-269B-44E1-80EA-BF59143D7BAC/XPSEPSC-x86-en-US.exe

How to install Windows Media Player 11 on Windows Server 2003

1) Download the installation file wmp11-windowsxp-x86-enu.exe and then extract its content to subfolder 2) Change value of HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Windows\CSDVersion from 100 to 200 3) Go to this sub-folder and change compatibility mode of wmfdist11.exe to WindowsXP. Run it. 4) Change compatibility mode compatibility mode of wmfdist11.exe to WindowsXP. Run it. 5) Change compatibility mode compatibility mode of wmdbexport.exe. to WindowsXP. Run it. 6) RESTART!!! 7) Return to the extracted files, change compatibility of wmp11.exe to Windows XP and run it 8) Change value of HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Windows\CSDVersion from 200 back to 100 9) Enjoy

How to uninstall SQL 2005 if it's missing in Add/Remove Programs

First of all - here is the support KB article. In my case - I was unable to uninstall SQL 2005 even manually from the command line (ArpWrapper was ceasing to work, displaying some "Registry Enumeration Failed" error and uninstalling components with MsiExec using their GUID's listed in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall just didn't worked). I was able to do it by uninstalling SQL components manually with Microsoft Windows Install Clean Up utility (do it in order, specified in KB article).

How to create WCF service proxy without publishing mex endpoint #2

Important update to my previous article: if your service is defined inside of a namespace - you must specify the namespace using /serviceName option during the 1st step (WSDL and XSD creation). Updated step #1 example: svcutil /serviceName:MyNamespace.MyService MyServiceSvc.exe /reference:SomeReference.dll If you'll miss specification of the namespace - resulting proxy code would be wrong (including even endpoing binding defintion).

Internet Explorer cannot open the Internet site - Operation aborted

I was affected by this issue and it took me some time to figure out what's the reason of it (in my case it was quite tricky). Generally - the reasons causing this error in IE are quite known. (Here are some for your reference :) http://support.microsoft.com/default.aspx/kb/927917 http://dean.edwards.name/weblog/2005/09/busted2/ http://www.mysticcoders.com/blog/2007/03/20/internet-explorer-cannot-open-the-internet-site-operation-aborted/ http://channel9.msdn.com/wiki/default.aspx/Channel9.InternetExplorerProgrammingBugs In my case it was a completely different story - it was caused by few IE DOM implementation bugs. Consider you have code on the IE client side that parses page body nodes and then removes them: while (body && body.hasChildNodes()) { var node = body.firstChild; // ... app logic body.removeChild(node); } Now consider that body content is created by Response.Write() on the server side (I write down some context in <p>...</p> paragraphs sections). My application was working as a blaze, but occasionally I was getting "Internet Explorer cannot open the Internet site - Operation aborted" in IE. In Firefox it was never happen. After some research I narrowed down the reason to the fact that body context is created by Response.Write and then I catched up what the problem was - it was related to the fact that on the server side I was writing body nodes in 4 steps: 1) ‘<p>’ 2) app-specific content 3) ‘</p>’ 4) Flush() output. So - sometimes on the client side the code was running while paragraph weren't fully formed (e.g. only starting <p> was written). In this case body.hasChildNodes() still returns true (IE bug #1) and body.removeChild(node) will cause "operation aborted" (IE bug #2). As I noted - it's IE-specific and not happens in other browsers. Fortunatelly - I had Response() bufferring turned off at the server side - o/w above problem would still happen, but with much lower frequency, making it very difficult to track it down. The solution, as you may guess, is to write whole node at once on the server side...