Starting app with Process.Start does not show in Task Manager until main application exits












0















I start a small application from my main application using process.start. Here is an abstract of my code: (I removed all the error-checking just for clarity...)



        Dim proc as New Process

Dim si As New ProcessStartInfo

si.FileName = "SourceMonitor.exe"

si.Arguments = "guid=" & GUID & " name=" & Name & " timeout=0"

si.UseShellExecute = True

si.CreateNoWindow = True

Proc.StartInfo = si

Proc.EnableRaisingEvents = True

AddHandler Proc.Exited, AddressOf procExitEventHandler

Proc.Start()


What happens is that the new app SourceMonitor will not show up in Task Manager - but I want it to. However, it Does show up as soon as the program that launched it (using process.start) exits. This seems odd to me!
I've tried setting UseShellExecute to False, and even tried a different approach using si (my ProcessStartInfo) to



WindowStyle = ProcessWindowStyle.Hidden
si.UseShellExecute = False 'this is required when using processWindowStyle.hidden


In every case the app does not show up in Task Manager until the main program exits.
Does anyone know of a way to make sure my app does show up in Task Manager? It helps when I need to diagnose a customer issue - because I need to see if the SourceMonitor is running.










share|improve this question


















  • 1





    I suspect it isn't missing, just not where you expect to see it. Perhaps it got grouped with your main program.

    – Raymond Chen
    Jan 2 at 15:57











  • Yes - that was indeed the case. Not sure if this is something new in one of the numerous Windows 10 update, but it kind works well for me. The new process does show up as a sub-process to the main application. If the main application is ended then it slides down to the list of all the independent processes.

    – Destek
    Jan 3 at 16:12
















0















I start a small application from my main application using process.start. Here is an abstract of my code: (I removed all the error-checking just for clarity...)



        Dim proc as New Process

Dim si As New ProcessStartInfo

si.FileName = "SourceMonitor.exe"

si.Arguments = "guid=" & GUID & " name=" & Name & " timeout=0"

si.UseShellExecute = True

si.CreateNoWindow = True

Proc.StartInfo = si

Proc.EnableRaisingEvents = True

AddHandler Proc.Exited, AddressOf procExitEventHandler

Proc.Start()


What happens is that the new app SourceMonitor will not show up in Task Manager - but I want it to. However, it Does show up as soon as the program that launched it (using process.start) exits. This seems odd to me!
I've tried setting UseShellExecute to False, and even tried a different approach using si (my ProcessStartInfo) to



WindowStyle = ProcessWindowStyle.Hidden
si.UseShellExecute = False 'this is required when using processWindowStyle.hidden


In every case the app does not show up in Task Manager until the main program exits.
Does anyone know of a way to make sure my app does show up in Task Manager? It helps when I need to diagnose a customer issue - because I need to see if the SourceMonitor is running.










share|improve this question


















  • 1





    I suspect it isn't missing, just not where you expect to see it. Perhaps it got grouped with your main program.

    – Raymond Chen
    Jan 2 at 15:57











  • Yes - that was indeed the case. Not sure if this is something new in one of the numerous Windows 10 update, but it kind works well for me. The new process does show up as a sub-process to the main application. If the main application is ended then it slides down to the list of all the independent processes.

    – Destek
    Jan 3 at 16:12














0












0








0








I start a small application from my main application using process.start. Here is an abstract of my code: (I removed all the error-checking just for clarity...)



        Dim proc as New Process

Dim si As New ProcessStartInfo

si.FileName = "SourceMonitor.exe"

si.Arguments = "guid=" & GUID & " name=" & Name & " timeout=0"

si.UseShellExecute = True

si.CreateNoWindow = True

Proc.StartInfo = si

Proc.EnableRaisingEvents = True

AddHandler Proc.Exited, AddressOf procExitEventHandler

Proc.Start()


What happens is that the new app SourceMonitor will not show up in Task Manager - but I want it to. However, it Does show up as soon as the program that launched it (using process.start) exits. This seems odd to me!
I've tried setting UseShellExecute to False, and even tried a different approach using si (my ProcessStartInfo) to



WindowStyle = ProcessWindowStyle.Hidden
si.UseShellExecute = False 'this is required when using processWindowStyle.hidden


In every case the app does not show up in Task Manager until the main program exits.
Does anyone know of a way to make sure my app does show up in Task Manager? It helps when I need to diagnose a customer issue - because I need to see if the SourceMonitor is running.










share|improve this question














I start a small application from my main application using process.start. Here is an abstract of my code: (I removed all the error-checking just for clarity...)



        Dim proc as New Process

Dim si As New ProcessStartInfo

si.FileName = "SourceMonitor.exe"

si.Arguments = "guid=" & GUID & " name=" & Name & " timeout=0"

si.UseShellExecute = True

si.CreateNoWindow = True

Proc.StartInfo = si

Proc.EnableRaisingEvents = True

AddHandler Proc.Exited, AddressOf procExitEventHandler

Proc.Start()


What happens is that the new app SourceMonitor will not show up in Task Manager - but I want it to. However, it Does show up as soon as the program that launched it (using process.start) exits. This seems odd to me!
I've tried setting UseShellExecute to False, and even tried a different approach using si (my ProcessStartInfo) to



WindowStyle = ProcessWindowStyle.Hidden
si.UseShellExecute = False 'this is required when using processWindowStyle.hidden


In every case the app does not show up in Task Manager until the main program exits.
Does anyone know of a way to make sure my app does show up in Task Manager? It helps when I need to diagnose a customer issue - because I need to see if the SourceMonitor is running.







taskmanager process.start






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 2 at 14:58









DestekDestek

7615




7615








  • 1





    I suspect it isn't missing, just not where you expect to see it. Perhaps it got grouped with your main program.

    – Raymond Chen
    Jan 2 at 15:57











  • Yes - that was indeed the case. Not sure if this is something new in one of the numerous Windows 10 update, but it kind works well for me. The new process does show up as a sub-process to the main application. If the main application is ended then it slides down to the list of all the independent processes.

    – Destek
    Jan 3 at 16:12














  • 1





    I suspect it isn't missing, just not where you expect to see it. Perhaps it got grouped with your main program.

    – Raymond Chen
    Jan 2 at 15:57











  • Yes - that was indeed the case. Not sure if this is something new in one of the numerous Windows 10 update, but it kind works well for me. The new process does show up as a sub-process to the main application. If the main application is ended then it slides down to the list of all the independent processes.

    – Destek
    Jan 3 at 16:12








1




1





I suspect it isn't missing, just not where you expect to see it. Perhaps it got grouped with your main program.

– Raymond Chen
Jan 2 at 15:57





I suspect it isn't missing, just not where you expect to see it. Perhaps it got grouped with your main program.

– Raymond Chen
Jan 2 at 15:57













Yes - that was indeed the case. Not sure if this is something new in one of the numerous Windows 10 update, but it kind works well for me. The new process does show up as a sub-process to the main application. If the main application is ended then it slides down to the list of all the independent processes.

– Destek
Jan 3 at 16:12





Yes - that was indeed the case. Not sure if this is something new in one of the numerous Windows 10 update, but it kind works well for me. The new process does show up as a sub-process to the main application. If the main application is ended then it slides down to the list of all the independent processes.

– Destek
Jan 3 at 16:12












1 Answer
1






active

oldest

votes


















0














Ok - found the "issue" - and it was rather obvious...
The second process is owned by the first. It doesn't show up in the list as an independent process, rather it shows up as a child of the main process. The Task Manager has a drop-down arrow on the main application.



v  MainApplication
- SourceMonitor


Clicking the dropdown shows the SourceMonitor it shelled. If I stop the main application the SourceMonitor does become an independent app and then shows up on the regular list. This actually works better than I had hoped.






share|improve this answer























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54008525%2fstarting-app-with-process-start-does-not-show-in-task-manager-until-main-applica%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    Ok - found the "issue" - and it was rather obvious...
    The second process is owned by the first. It doesn't show up in the list as an independent process, rather it shows up as a child of the main process. The Task Manager has a drop-down arrow on the main application.



    v  MainApplication
    - SourceMonitor


    Clicking the dropdown shows the SourceMonitor it shelled. If I stop the main application the SourceMonitor does become an independent app and then shows up on the regular list. This actually works better than I had hoped.






    share|improve this answer




























      0














      Ok - found the "issue" - and it was rather obvious...
      The second process is owned by the first. It doesn't show up in the list as an independent process, rather it shows up as a child of the main process. The Task Manager has a drop-down arrow on the main application.



      v  MainApplication
      - SourceMonitor


      Clicking the dropdown shows the SourceMonitor it shelled. If I stop the main application the SourceMonitor does become an independent app and then shows up on the regular list. This actually works better than I had hoped.






      share|improve this answer


























        0












        0








        0







        Ok - found the "issue" - and it was rather obvious...
        The second process is owned by the first. It doesn't show up in the list as an independent process, rather it shows up as a child of the main process. The Task Manager has a drop-down arrow on the main application.



        v  MainApplication
        - SourceMonitor


        Clicking the dropdown shows the SourceMonitor it shelled. If I stop the main application the SourceMonitor does become an independent app and then shows up on the regular list. This actually works better than I had hoped.






        share|improve this answer













        Ok - found the "issue" - and it was rather obvious...
        The second process is owned by the first. It doesn't show up in the list as an independent process, rather it shows up as a child of the main process. The Task Manager has a drop-down arrow on the main application.



        v  MainApplication
        - SourceMonitor


        Clicking the dropdown shows the SourceMonitor it shelled. If I stop the main application the SourceMonitor does become an independent app and then shows up on the regular list. This actually works better than I had hoped.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jan 2 at 17:03









        DestekDestek

        7615




        7615
































            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54008525%2fstarting-app-with-process-start-does-not-show-in-task-manager-until-main-applica%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            MongoDB - Not Authorized To Execute Command

            How to fix TextFormField cause rebuild widget in Flutter

            Npm cannot find a required file even through it is in the searched directory