![]() |
![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() |
| Welcome to Windows Vista Forums. Our forum is dedicated to helping you find solutions with any problems, errors or issues you are experiencing with Windows Vista. The Vista forum also covers news and updates and has an extensive Windows Vista tutorial section that covers a wide range of tips and tricks. |
| |||||||
![]() |
| |
| | #1 (permalink) |
| | New-object preventing process from exiting We have a C++ application that has an automation object model. In PowerShell we create a new instance of the object model via New-Object. Everything works as expected in terms of calls to the created object. Problems arise if the user closes the application first, then closes PowerShell. The process of the application will not have exited, as seen by Task Manager. If PowerShell is exited, and then the application the process will exit correctly. What type of solution can I provide to my customers where they don't have to worry about the order in which the application and PowerShell are exited? Thanks for any insight. |
My System Specs![]() |
![]() |
| Thread Tools | |
| |
Similar Threads | ||||
| Thread | Forum | |||
| preventing PS from Casting object to an array | PowerShell | |||
| On exiting Windows Mail, "winmail.exe" remains as active process | Vista mail | |||
| Exiting a process cleanly | PowerShell | |||
| Bug? Shouldn't Stop-Process automatically match Id if object is a process? | PowerShell | |||
| measure-object {get-process} | PowerShell | |||