@schatekar oh yes, even more when you turn on verbose mode :-)
with the 7 PRs you submitted, was that 7 times the usual reading of logs? ;)
I've only done 3 pr's for tests :-)
@GraemeBradbury One option is to drop a Debugger.Break() where you want the breakpoint. Will force attachment of debugger.
@cpx Is that not what VS does internally when you set a breakpoint?
@creepone we decided on a standard set of expectations for how DI is supposed to behave in Akka.NET, since it was chaotic and unpredictable from one framework to the next
@stefansedich is publishing a list of all of the settings you should have on your containers for working with actors, but the TL;DR; of it is that we expect the container to manage the lifecycle of the objects
and to automatically dispose those objects on restart / termination
Ninject and others were not doing this before
leaking memory, essentially
@schatekar No, those breakpoints are only set when VSHost executes. My guess is that the VSHost exe injects the breakpoints at runtime using internal CLR methods.
@creepone but if this is causing some unintended side effects, please file an issue!
I think @stefansedich recommended for Ninject that you bind things .InScope()
@bruinbrown > I've got the child process debugging power tools but it doesn't seem to attach the debugger on child processes. Any tips on running them as well?
there's a little trick to this that isn't very straightforward
so you want to open that menu, Debug --> Other Debug Targets --> Child Process Debugging Settings
and then configure it like this
make sure Enable child process debugging is checked
and add NodeTestRunner.exe as an entry, also checked, with action Attach debugger
then press Save
@Aaronontheweb could you stick that to a gist or an issue? so that it is easy to refer to in future?