AutoIt .EXE stops while debugging C#/.Net program

[Rockney]

Have a .EXE program written with AutoIt to monitor and manage any selected Windows services, see https://github.com/Corionis/CorionisServiceManager

The issue is - when debugging C# Windows service code in either Visual Studio or Jetbrains Rider the AutoIt program also stops when a C# breakpoint is reached.

Why does that happen?

Any way to keep the AutoIt program from stopping at C# breakpoints? 

The AutoIt program is separate and has nothing to do with the  C# code other than starting/stopping the relevant Windows service being worked on.

[faustf]

why you use  Corionis Service Manager ,  and not  use  Windows service  ??

and i think you must ask why not  work corionis  in  git hub 

https://github.com/Corionis/CorionisServiceManager/issues

 

Edited February 9, 2019 by faustf

[Jos]

3 minutes ago, faustf said:

and i think you must ask why not  work corionis  in  git hub 

Why when the AutoIt3 script stops working?

29 minutes ago, Rockney said:

the AutoIt program also stops

What exactly does this mean?   Crash/Just nicely exits/ other?
.. and what about showing the script so we can have a look?

Jos

[faustf]

2 minutes ago, Jos said:

and what about showing the script so we can have a look?

you can  download a script  here 

https://github.com/Corionis/CorionisServiceManager

also if  i think is much better if  him  use  a windows service  and remove corionius

 

[Jos]

7 minutes ago, faustf said:

you can  download a script  here 

https://github.com/Corionis/CorionisServiceManager

Ah, now your answer makes sense... sorry for my earlier comment.  

Jos

[faustf]

don't  worry Jos  is  sathurday

 

[Rockney]

On 2/9/2019 at 1:58 PM, faustf said:

you can  download a script  here 

https://github.com/Corionis/CorionisServiceManager

also if  i think is much better if  him  use  a windows service  and remove corionius

 

I wrote the Corionis Service Manager (CSM) because Windows Services is a poor interface when you're only interested in monitoring and controlling 4-8 services. As an engineer I start/stop services constantly while working on their code. The CSM is very handy for that.

To try to explain more clearly ... the CSM runs normally, compiled as an .exe, monitoring various Windows services including the one I'm writing.

But, while working on a service in C#/.NET code in a debugger in Visual Studio or JetBrains Rider, when the debugger stops at a breakpoint in the service's code CSM also stops.  The two are not directly related.  CSM uses a call to advapi32.dll to detect each service's running state. So I must assume the call to advapi32.dll is being stopped by a breakpoint in the service's code. It's odd that a separate program (CSM) is affected by debugging C#/.NET Windows service code.

[Earthshine]

 You need lots of logging in your auto IT script and read your logs and see what’s happening. That logger that you were wrote Is not up to the task download log4a.au3 and use that To create data rich logs that you can debug with

Edited February 14, 2019 by Earthshine

[Juvigy]

I am guessing the debugger stops the calling CSM process that has started the service. Most likely the service is started as a child of the SCM and that is why this happens. You can verify my guess via the task manager.