.NET Framework

Upload large content with Http.sys, IIS, ASP and ASP.NET

Posted on Updated on

There is a limit on the size of content (like files) one can upload when that content is hosted on an Internet Information Services (IIS) web server. The limits in charge depend on

  • The version of IIS
  • The configuration of IIS
  • The possible usage of certain ISAPI extensions and filters
    • If so, which extensions/filters? (for example: ASP or ASP.NET)
    • If so, which versions of extensions/filters (for example: version 4.0 of ASP.NET)

Different versions of IIS and ISAPI extensions/filters have different upload limit settings and/or hardcoded upload limits. Yes, you can already feel this article, that restricts itself to IIS, ASP and ASP.NET, won’t be THAT easy… 😉
Read the rest of this entry »

Windows Presentation Foundation (WPF): introduction & overview (useful for system administrators and engineers)

Posted on Updated on

Most articles about WPF start straight away with WPF code, trying to get you started as soon as possible. The problem is those articles don’t start with some basic and sometimes even necessary theory, so readers don’t get a real grip on what exactly they’re doing. Heck, many of those articles don’t even mention those basics at all, leaving readers alone without awareness of the context they’re programming in and that’s more than a pity of course. Other readers are not interested in WPF programming itself, but would like to get an idea of what WPF is, how it works and how to deal with it; system administrators and engineers for example. Read the rest of this entry »

How to run 32 bit .NET Windows apps on 64 bit Windows (including with IEExec)

Posted on Updated on

Suppose you have a 32 bit .NET Windows application (whether it is a console or GUI Windows application (the latter in .NET a so-called Windows Forms app)) and you want to run it on a 32 bit Windows system. It doesn’t matter if you start it from Windows Explorer, from Command Prompt, from PowerShell (PS), through ClickOnce or start it directly from Internet Explorer (IE). In the last case IEExec.exe is started and your 32 bit .NET (version 1, 2 or 3) application is run within this process. IEExec is a runtime host for .NET (version 1, 2 or 3) applications in the scenario where the .NET executable is referred to via an URL provided to IE. For example, suppose you have a .NET GUI application hosted on a web server (no no, I’m not talking about a .NET WUI application, I am talking about a .NET GUI application (an .exe file and possibly a few DLLs) hosted by a web server like IIS, just like any other kind of file can be hosted by a web server. This type of deployment is called No-Touch Deployment aka Zero Deployment). The URL is something like http://servername:port/vdir/application.exe. You open IE, type or paste this URL in the address bar and let IE do its job. The IEExec.exe process will be created and the application.exe will run within this process, as IEExec is the runtime host in this scenario. Read the rest of this entry »