I have windows 7 home premium. I have turned on IIS .Confirmed if its running by typing localhost on my address bar. It show IIS welcome message, showing its working.
However when I try to open IIS manager, nothing happens. I want to deploy my asp.net mvc 3 application on it. How do I solve this issue?
For me helped focusing on the window via Alt-Tab, then pressing Alt-Space and select Move in the drop-down menu. After that, either drag the mouse or move with keyboard buttons. By the way, works with all windows.
Update for Win 10
There is another easier solution for such windows for Win 10. You can pull any available window to the left edge of the screen. Windows will expand the window to half of the screen and prompts you to choose any opened window to fill the second half. Choose the window you can't access and you're good.
Related
My user interface for MAMP Pro itĖself won't show up. . Everything run/works fine though (Apache, MySQL).
I'm on Windows 10 Home 1903. The window is simply not there, also not in Task view.
What i tried so far to no avail;
Uninstalled MAMP, installed latest package
Windows + arrowkeys for window positioning
Other Monitors, extended & mirror view
The normal MAMP UI (not pro) launches fine btw.
For anybody else experiencing this issue in the future, it has to do with Windows screen management. For me hitting windows + P and selecting extending screen, enter, and than quickly back to 'second screen only' showed the application UI 'ghosting' somewhere in the right below corner.
Somehow like magic the previews in my task view (and also hovering over taskbar icon) were back and the app is showing again.
In Windows 7 when I right click on the taskbar icon, all my Delphi apps (5, 2006 and XE) show the full taskbar menu: App name, Pin/Unpin and Close Window. On Windows 10 all these apps show only the Close Window menu item. Why is that and how can I get the full menu in Win10?
Update: If I create a new app in Delphi XE on Win 10 it shows the full menu. If I create a new app on Delphi XE in Win 7 it shows the full menu on Win 7 but not on Win 10.
No, this neither happens to all your apps (it happens to every application with a window), nor can David Heffernan be able to see it: Win10 just don't has that (most likely it was gone with Win8 already).
To make sure what fullerm is talking about: right-click on the task button and see its context menu: for every window you only have "close" plus two more generic entries, and then based on the application even more. But the system menu (right click on a window's top left icon) is not available thru the task button anymore
Task button = taskbar representing each currently displayed window. Pinned apps and shortcuts are not task buttons, neither are those of the task tray (rightmost next to the clock)
System menu = context menu every window owns with basic entries like "minimize", "maximize", "close", "size", "move" and even more. Accessible thru right clicking the topleft icon of a window or pressing ALT+SPACE. Might be inaccessible when the window is owner-drawn.
Window = owned by a running process. Processes neither need to have a window, nor are they restricted to only having one window. Nowadays Windows calls processes "apps" (I guess).
Sometimes when dragging a window around on the Windows 7 desktop, all of my other open windows will suddenly minimize. I can go to the task bar and reopen them, one by one, but is there a way to get them all back at once? And is there a way to turn off this annoying behaviour?
Thanks.
That will be Aero Shake.
You can shake the window that you were moving and your windows will be restored.
You can also disable Aero Shake, following instructions here:
Go to Run (Windows+R) and type gpedit.msc
Navigate to User configuration > Administratives Templates > Desktop
Search for "Turn off Aero Shake window minimizing mouse gesture" and enable the policy.
If you shake a window (left-right rapidly or another direction) then it minimizes all windows except that one. To get them back, shake the first window again.
This is what worked for me.
Open Windows Explorer.
Maximize and close it with Shift pressed.
Windows Explorer should open maximized.
We have a windows app, written several years ago and maintained over time. We do not have any specific code to handle any Windows 7 UI features. Just plain old Winforms and WPF. We are seeing issues with closing windows using the Taskbar's preview and close button.
On some workstations, when the window is re-opened (calling the same tool via a menu), it is empty (white/blank). On other workstations, the same window is drawn outside the screen.
While there might be some custom code to initialize the window and restore it in the right location, what is troubling us is that none of those issues exist if we close the window using the standard close button on the title bar or using a "close" command.
Does anybody have any idea what is different between the closing of a window using the Taskbar and the standard button?
Regards,
Eric.
I have an issue where a program that runs fine under windows xp has stopped working with windows 7. The application appears to start fine then disappears with only the taskbar icon remaining. If you hover over the taskbar icon you can see the application and it kind of looks correct but selecting it does nothing. I cannot seem to get the application to actually appear. Has anyone experienced anything like this and is aware of any possible solutions?
Recent builds have worked with windows 7 in the past and I don't believe any significant changes were made before this issue arrived.
Thanks
It may be the program is running but somewhere off screen. Shift-right-click the taskbar button and select "Move." Press the arrow keys to begin the move, then move your mouse to attach the movement to the mouse cursor. See if that brings the app to the primary monitor.
If not, you may have an incompatibility issue which will require more research/investigation.
Holding down the Windows key and the letter P at the same time will allow you to change your projector settings. Select the "Duplicate" option. As mentioned above, this usually occurs when you typically use a dual monitor but switch to a single monitor.