IISxpress Forums

hi I am evaluating your software at present however I can not launch it from the system try, although I can see the icon. any suggestions as to why this would be ?

 

thanks

Hi Jeremy,

That seems like a strange problem. You should be able to activate the configuration window by double clicking on the icon in the notification area of the status bar or by right clicking on the icon and selecting 'Status' from the menu.

It is also possible to navigate to the notification area by using the keyboard. If you are using XP use your mouse to click the 'start' button in the task bar, then use your tab key to move the input focus to the quick launch area (if you have it enabled), then the running application buttons and finally to the notification area. From here use your cursor keys to select the IISxpress icon, then press the Windows context key (on a US keyboard it is to the left of the right CTRL key).

What version of Windows are you running? it would also be useful to know what service pack you have installed.

Hi

I have seen this situation once myself, I shows your product to a friend who runs a personal weather site (http://weather.cobbnz.com) and I encouraged him to install the 2.1 beta.

His system was 2003 R2.

Install and everything went fine ( I am amazed that you don't even need to restart the IIS Process )

Now he logged in via his desktop and then I saw the issue when we logged back to his box via Remote Desktop.

The icon was visible but not the dialog, so I do not know if any of this is useful to you but it could be worth looking into.

Chris Crowe [ IIS MVP]
http://blog.crowe.co.nz

 

Hi Chris, thanks for the detailed explanation of the problem.

One explanation for what is happening here is that the local and remote sessions are running different screen resolutions. My guess would be that the local session has a higher screen resolution than the remote session. If the dialog is placed in an area of the screen which is outside the screen area of the remote desktop session then the window could appear to be missing. One way to confirm this possibility is to press ALT+SPACE then M when the problem occurs. This is the key sequence which instructs Windows to move the active window on the screen. If the mouse cursor changes to a four pointed cross then it confirms the fact that the window is active but offscreen somewhere. You can use the cursor keys to move the window into the visible screen area.

Alternately it could be something more subtle.

I will continue to investigate the issue and hopefully get a fix included in 2.1.

Is there any update on this? I'm seeing this problem on 2.2 trial edition on Windows 2003 SP2. Sometimes double clicking the tray icon and closing the remote desktop window and re-connecting will allow the screen to appear but it's quite sporadic

There is a scenario which I have recently uncovered which may (at least partially) explain this issue. If you are running a two screen setup and screen 2 is to the left of screen 1 (21 rather than 12) then the display coordinate system used by Windows uses negative coordinate space. The fallout of this is that when IISxpress attempts to restore the previous window position it incorrectly calculates that the last displayed position is still valid which results in the window being displayed offscreen. This would most likely when remote desktop is thrown into the mix since it only supports one screen.

For example, if you have two displays running 1024x768, in the 12 configuration then the screen rectangle is [0, 0, 2048, 768]. If the screen configuration is 21 the screen rectangle becomes [-1024, 0, 1024, 768].

Ok, thats enough of the math. If you encounter this problem running IISxpress 2.2 then try this fix. Please post back to this thread with your results.

Fix instructions:

1. Download the ZIP file.
2. In the ZIP file there are two directories, 32bit and 64bit. Select the one that matches your system.
3. Run the IISxpressTray.exe program. Note: you should NOT copy this over the IISxpress install directory unless you want to keep this version of the application.
4. Try to recreate the problem you were seeing with the previous version.