Month: May 2011

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 »

Remote Desktop Connection (RDC) 6.1 for Windows Server 2003

Posted on Updated on

I read and hear a lot of questions about why Remote Desktop Connection 6.1 or later doesn’t exist for Windows Server 2003. Well, if you’re wondering, I have good news for you: RDC 6.1 does exist for Windows Server 2003!

First of all, Remote Desktop Connection (RDC) is the Microsoft RDP client, previously called Terminal Services Client (TSC). It’s by far the most common tool to connect to a Remote Desktop Protocol (RDP) server, which is actually every somewhat modern Windows system. The RDP server component of Windows systems (clients and servers) is called Remote Desktop Services (RDS), formerly known as Terminal Services (TS). Some of those Windows systems can be put in a special mode to allow more remote connections/sessions, making the system a so-called Remote Desktop Session Host (RDSH) or Terminal Server (TS) (the former name). Read the rest of this entry »