Window. Show Метод

Определение

Открывает окно и возвращается без ожидания закрытия нового открытого окна. Opens a window and returns without waiting for the newly opened window to close.

Исключения

Метод Show() вызывается для окна, которое закрывается (Closing) или закрыто (Closed). Show() is called on a window that is closing (Closing) or has been closed (Closed).

Примеры

В следующем примере показано, как открыть немодальное окно. The following sample demonstrates how to open a modeless window.

Комментарии

При Window создании экземпляра класса он не отображается по умолчанию. When the Window class is instantiated, it is not visible by default. Show показывает окно и возвращает немедленно, не дожидаясь закрытия окна. Show shows a window and returns immediately, without waiting for the window to be closed. Следовательно, открытое окно не мешает пользователям взаимодействовать с другими окнами в приложении. Consequently, the opened window does not prevent users from interacting with other windows in the application. Этот тип окна называется немодальным окном. This type of window is called a modeless window. Распространенными примерами немодальных окон являются окна свойств, панели инструментов и палитры. Common examples of modeless windows are properties windows, toolboxes, and palettes. Чтобы запретить пользователю взаимодействие с определенным окном, окно должно быть открыто путем вызова ShowDialog . To restrict a user to interacting with a specific window, the window must be opened by calling ShowDialog.

Окно, открываемое при вызове, Show не имеет автоматически связи с окном, которое его открыло; в частности, открытое окно не знает, какое окно открыло его. A window that is opened by calling Show does not automatically have a relationship with the window that opened it; specifically, the opened window does not know which window opened it. Эту связь можно установить с помощью Owner Свойства и управлять ими с помощью OwnedWindows Свойства. This relationship can be established using the Owner property and managed using the OwnedWindows property.

Вызов Show достигает того же конечного результата, что и Visibility свойство Setting Window объекта, равным Visible . Calling Show achieves the same end result as setting Visibility property of the Window object to Visible. Однако существует разница между двумя значениями с точки зрения времени. However, there is a difference between the two from a timing perspective.

Вызов Show — это синхронная операция, которая возвращает только после Loaded вызова события в дочернем окне: Calling Show is a synchronous operation that returns only after the Loaded event on the child window has been raised:

VisibilityОднако параметр является асинхронной операцией, которая возвращает немедленно. Setting Visibility, however, is an asynchronous operation that returns immediately:

При установке Visibility все события окна, регистрируемые до установки, Visibility могут не вызываться до тех пор, пока не завершится выполнение метода, в котором вы установили Visibility . When setting Visibility, any window events you register before you set Visibility may not be raised until after the method in which you set Visibility has completed execution.

How to open Windows Services Manager in Windows 10

At times you may need to open and manage your Windows Services. You may want to stop some service, start it, disable the service, delay its start-up or resume or pause the Windows Service. At such time, the Services Manager, which is a built-in tool in the Windows operating system, will help you. This post will show you how to open your Windows Services, using Services Manager as well as the Command Prompt.

Windows Services are applications that typically start when the computer is booted and run quietly in the background until it is shut down. Strictly speaking, a service is any Windows application that is implemented with the services API and handles low-level tasks that require little or no user interaction.

How to open Windows Services Manager

To open the Windows Services Manager on your Windows 10 computer, do the following:

1. Right-click on the Start button to open the WinX Menu
2. Select Run
3. Type services.msc in the Run box which opens
4. Windows Services Manager will open.

Here you will be able to start, stop, disable, delay Windows Services.

Let us see how to do this in a bit more detail.

Right-click on your Start button to open the WinX Menu. Select Run. This opens the Run box. Now type services.msc in it and hit Enter to open the Services Manager.

Here, under the Name column, you will see the list of Services running on your system, along with their description. You will also be able to see their Status -whether they are running or stopped, along with the Startup types.

Types of Windows Services startup

Windows 10 offers four start-ups types:

1. Automatic
2. Automatic (Delayed Start)
3. Manual
4. Disabled.

Start, stop, disable Windows Services

To start, stop, pause, resume or restart any Windows Service, select the Service and right-click on it. You will be offered these options.

If you wish to manage more options, double-click on the Service to open its Properties box.

Here, under the Startup type drop-down menu, you will be able to select the startup type for the Service.

Under Service status, you will see buttons to Start, Stop, Pause, Resume the Service.

In the Properties box, you will also see other tabs like Log On, Recovery & Dependencies, which offer additional options and information.

Once you have made your changes, you will have to click on Apply and restart your computer, for the changes to take effect.

Read: What does Automatic (Trigger Start) and Manual (Trigger Start) mean for Windows Services?

Manage Services using Command Line

You can also use the Command Prompt to start, stop, pause, resume service. To use it, from the WinX Menu, open Command Prompt (Admin) and execute one of the following commands:

To start a service:

To stop a service:

To pause a service:

To resume a service:

To disable a service:

It is recommended that you not change the default settings unless you know what you are doing, as this can cause some parts of your operating system to stop working. When you stop, start, or restart a service, any dependent services are also affected, so you want to be careful here.

9 ways to access Services in Windows (all versions)

The Services app in Windows lists all the services that are installed by the operating system, the drivers and apps that you are using. With it, you can set which services run when Windows starts, disable services you do not need, and perform other useful actions. If you need to view all the services that exist in Windows, you need to start the Services app. Here is how to do that in all versions of Windows:

NOTE: This guide covers Windows 10, Windows 7, and Windows 8.1. Some methods work in all three versions of Windows, others just in one or two. For each method, we mention the Windows version in which it works. If you do not know the version of Windows that you have, read this tutorial: What version of Windows do I have installed?

1. Access Windows Services using search (all Windows versions)

One way that works in all versions of Windows is to use search. If you are using Windows 10, click the search box near the Start button, and type “services.” Then, click or tap the search result with the same name.

In Windows 7, click Start, and in the search box above this button, type the word “services.” Click the search result with the same name.

In Windows 8.1, go to the Start screen, and start typing the word “services.” Then, click or tap the “View local services” search result.

2. Use the Start Menu to start Services (Windows 10 only)

Windows 10 is the only Windows version that has a shortcut to, in the Start Menu. To find it, click the Start button, scroll down the list of apps to the letter W and find the “Windows Administrative Tools” folder. Open it, and there you see the Services shortcut. Click on it.

3. Use the Control Panel to access Services (all Windows versions)

Start the Control Panel , and go to “System and Security -> Administrative Tools.”

In the list of Administrative Tools, find and use the Services shortcut.

4. Use the Run window to start Services (all Windows versions)

Press the Win + R keys on your keyboard, to open the Run window . Then, type “services.msc” and hit Enter or press OK.

The Services app window is now open.

5. Create a shortcut to Services and place it where you want (all Windows versions)

You can also create a shortcut for Services and place it on your desktop, pin it to the taskbar or the Start Menu. When you create the shortcut, use the command services.msc as its target.

6. Use the Command Prompt or PowerShell to start Services (all Windows versions)

You can also open Services from the Command Prompt or PowerShell . Type the command services.msc and press Enter on your keyboard.

7. Use the Computer Management console to view Services (all Windows versions)

In all versions of Windows, Services can also be accessed using the Computer Management console. Start by opening Computer Management . On the left side of the Computer Management window, there is a section called Services and Applications. Open it and then double-click Services. All your services are loaded in the center of the window.

8. Use Task Manager to access Services (all Windows versions)

The Task Manager can also be used for launching the Services app. First press the Ctrl + Shift + Esc keys to open Task Manager. If you are doing this on a Windows 10 or Windows 8.1 PC, and the Task Manager opens up in its compact mode , click or tap on “More details.” Then, open the File menu, select “Run new task,” and type the command services.msc in the “Create new task” window. Finally, press Enter on your keyboard or click or tap OK.

9. Use the Services shortcut from our collection (all versions of Windows)

We have created the most extensive collection of shortcuts for Windows. Download it , extract it and you can find the Services shortcut in the Administration Tools sub-folder for your Windows version.

Why are you accessing your services, in Windows?

We access Services when we set up a new PC or device with Windows, or when performance degrades and we need to improve it by disabling unnecessary services that are automatically run at Windows startup. Before closing this tutorial, tell us why you are using the Services app. Comment below and let’s discuss.

show a windows form from a window service

i am creating a window service. my requirement is to display window form from window NT service on particular interval. For testing purpose , i just want to display the form on service start:

it not working. Neither form is showing nor calc process is running. i have found some links showing pop up , but most of them suggesting WCF. isn’t it possible without wcf. can anybody show me the way to achieve this.

3 Answers 3

Cant be done*. In later Operating Systems that won’t work as Windows Services are disallowed from interacting with the Desktop — instead UI presented by Windows Services is shown in Session 0, a special logon session which is not normally visible to the end user.

What you should instead do is write a separate Windows Forms application which is always running, but not always visible (possibly have that application run at startup and have an icon in the notification area) and communicates with the Windows Service using some form of IPC

When the Windows Service wishes to display some UI to the user it sends a message to the application, which in turns shows the desired UI to the end user.

**or at least it definitely shouldn’t be done*

I am just referring to the answer given in another link in StackOverflow

Be aware that if you are planning to eventually deploy on Windows Vista or Windows Server 2008, many ways that this can be done today will not work. This is because of the introduction of a new security feature called «Session 0 Isolation».

Most windows services have been moved to run in Session 0 now in order to properly isolate them from the rest of the system. An extension of this is that the first user to login to the system no longer is placed in Session #0, they are placed in Session 1. And hence, the isolation will break code that does certain types of communication between services and desktop applications.

The best way to write code today that will work on Vista and Server 2008 going forward when doing communication between services and applications is to use a proper cross-process API like RPC, Named Pipes, etc. Do not use SendMessage/PostMessage as that will fail under Session 0 Isolation.

How can I run an EXE program from a Windows Service using C#?

How can I run an EXE program from a Windows Service using C#?

This is my code:

When I run this service, the application is not starting.
What’s wrong with my code?

9 Answers 9

This will never work, at least not under Windows Vista or later. The key problem is that you’re trying to execute this from within a Windows Service, rather than a standard Windows application. The code you’ve shown will work perfectly in a Windows Forms, WPF, or Console application, but it won’t work at all in a Windows Service.

Windows Services cannot start additional applications because they are not running in the context of any particular user. Unlike regular Windows applications, services are now run in an isolated session and are prohibited from interacting with a user or the desktop. This leaves no place for the application to be run.

More information is available in the answers to these related questions:

The best solution to your problem, as you’ve probably figured out by now, is to create a standard Windows application instead of a service. These are designed to be run by a particular user and are associated with that user’s desktop. This way, you can run additional applications whenever you want, using the code that you’ve already shown.

Another possible solution, assuming that your Console application does not require an interface or output of any sort, is to instruct the process not to create a window. This will prevent Windows from blocking the creation of your process, because it will no longer request that a Console window be created. You can find the relevant code in this answer to a related question.

i have tried this article Code Project, it is working fine for me. I have used the code too. article is excellent in explanation with screenshot.

I am adding necessary explanation to this scenario

You have just booted up your computer and are about to log on. When you log on, the system assigns you a unique Session ID. In Windows Vista, the first User to log on to the computer is assigned a Session ID of 1 by the OS. The next User to log on will be assigned a Session ID of 2. And so on and so forth. You can view the Session ID assigned to each logged on User from the Users tab in Task Manager.

But your windows service is brought under session ID of 0. This session is isolated from other sessions. This ultimately prevent the windows service to invoke the application running under user session’s like 1 or 2.

In order to invoke the application from windows service you need to copy the control from winlogon.exe which acts as present logged user as shown in below screenshot.

you can use from windows task scheduler for this purpose, there are many libraries like TaskScheduler that help you.

for example consider we want to scheduling a task that will executes once five seconds later:

notepad.exe will be executed five seconds later.

for details and more information please go to wiki

if you know which class and method in that assembly you need, you can invoke it yourself like this:

Top answer with most upvotes isn’t wrong but still the opposite of what I would post. I say it will totally work to start an exe file and you can do this in the context of any user. Logically you just can’t have any user interface or ask for user input.

Here is my advice:

1. Create a simple Console Application that does what your service should do right on start without user interaction. I really recommend not using the Windows Service project type especially because you (currently) can’t using .NET Core.
2. Add code to start your exe you want to call from service

Example to start e.g. plink.exe. You could even listen to the output:

1. Use NSSM (Non-Sucking Service Manager) to register that Console Application as service. NSSM can be controlled via command line and can show an UI to configure the service or you configure it via command line. You can run the service in the context of any user if you know the login data of that user.

I took LocalSystem account which is default and more than Local Service. It worked fine without having to enter login information of a specific user. I didn’t even tick the checkbox «Allow service to interact with desktop» which you could if you need higher permissions.

Lastly I just want to say how funny it is that the top answer says quite the opposite of my answer and still both of us are right it’s just how you interpret the question :-D. If you now say but you can’t with the windows service project type — You CAN but I had this before and installation was sketchy and it was maybe kind of an unintentional hack until I found NSSM.

You can execute an .exe from a Windows service very well in Windows XP. I have done it myself in the past.

You need to make sure you had checked the option «Allow to interact with the Desktop» in the Windows service properties. If that is not done, it will not execute.

I need to check in Windows 7 or Vista as these versions requires additional security privileges so it may throw an error, but I am quite sure it can be achieved either directly or indirectly. For XP I am certain as I had done it myself.

First, we are going to create a Windows Service that runs under the System account. This service will be responsible for spawning an interactive process within the currently active User’s Session. This newly created process will display a UI and run with full admin rights. When the first User logs on to the computer, this service will be started and will be running in Session0; however the process that this service spawns will be running on the desktop of the currently logged on User. We will refer to this service as the LoaderService.

Next, the winlogon.exe process is responsible for managing User login and logout procedures. We know that every User who logs on to the computer will have a unique Session ID and a corresponding winlogon.exe process associated with their Session. Now, we mentioned above, the LoaderService runs under the System account. We also confirmed that each winlogon.exe process on the computer runs under the System account. Because the System account is the owner of both the LoaderService and the winlogon.exe processes, our LoaderService can copy the access token (and Session ID) of the winlogon.exe process and then call the Win32 API function CreateProcessAsUser to launch a process into the currently active Session of the logged on User. Since the Session ID located within the access token of the copied winlogon.exe process is greater than 0, we can launch an interactive process using that token.

I think You are copying the .exe to different location. This might be the problem I guess. When you copy the exe, you are not copying its dependencies.

So, what you can do is, put all dependent dlls in GAC so that any .net exe can access it

Else, do not copy the exe to new location. Just create a environment variable and call the exe in your c#. Since the path is defined in environment variables, the exe is can be accessed by your c# program.

previously I had some kind of same issue in my c#.net 3.5 project in which I was trying to run a .exe file from c#.net code and that exe was nothing but the another project exe(where i added few supporting dlls for my functionality) and those dlls methods I was using in my exe application. At last I resolved this by creating that application as a separate project to the same solution and i added that project output to my deployment project. According to this scenario I answered, If its not what he wants then I am extremely sorry.