Posts

Showing posts from January, 2011

Web Browser control memory leakage

There is a quite long discussion regarding to the memory leak in IE webBrowser control. I noticed this problem as well. In my C# Windows form application, I used the WebBrowser control to navigate a list of web pages. Originally every navigation will consum 5MB memory and never release this memory until application crashes. After install IE 8, this problem disappeared. Memory usage stays quite stable. My development environment is Visual Studio 2010 Express + Visual Studio 2010 Service pack Beta 1 + Vista with Service pack 2 + IE 8. It looks IE 8 did the trick to remove this memory leakage.

Add compiler option to Visual Web Developer Express

In Visual Web Developer 2005 Express Edition, there is no direct way to compile the web site. However, we can add a pre-compile menu to the VWD using the external tools 1. In main VWD top menu bar, select the Tools -> External tools menu. 2. In the pop out dialog, click add to add a menu item. 3. In the Title edit box, add text: Pre-&Compile (non-updatable) 4. Specify the the Command text by browsing to the asp.net compiler. By default it is C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_compiler.exe 5. In the arguments text box, add following text: -p "$(ProjectDir)" -v / "$(ProjectDir)\..\Compiled" You can specify other options such as us output window or not. Click Apply to add this menu. Now you can start to compile your application. You can also compile the application as update-able web site. Update-able web site using Partial Compilation, which compiles only the CodeBeside classes but leaves the ASPX pages to compile at run time on the se...