Checklist
Is Your Feature Request Related To A Problem? Please describe.
When the project files where updated to make use of the VS2017 csproj structure, there were a need to also update SimpleInjector, the behaviour of the SimpleInjector we needed to update to throws exceptions related to life cycles being invalid, and we had to disable this verification system to be able to continue (changing the lifecycle could have breaking changes, so this weren't done).
Describe The Solution. Why is it needed?
We need to investigate and update the lifecycle used when registering dependencies to be proper for SimpleInjector, so that we are able to continue with having SimpleInjector validate the bindings.
User Story
As a maintainer of the application, I would like us to validate/ensure that we are registering dependencies properly, so that we can ensure that there won't be any surprises happening when resolving items during runtime.
Additional Context
This is not directly related to something a user would see (most likely), but rather to the maintenance of the application and that we ensures that we are doing the correct things when it comes to registering dependencies.
Acceptance Criteria
Related Issues
No response
Checklist
Is Your Feature Request Related To A Problem? Please describe.
When the project files where updated to make use of the VS2017 csproj structure, there were a need to also update SimpleInjector, the behaviour of the SimpleInjector we needed to update to throws exceptions related to life cycles being invalid, and we had to disable this verification system to be able to continue (changing the lifecycle could have breaking changes, so this weren't done).
Describe The Solution. Why is it needed?
We need to investigate and update the lifecycle used when registering dependencies to be proper for SimpleInjector, so that we are able to continue with having SimpleInjector validate the bindings.
User Story
As a maintainer of the application, I would like us to validate/ensure that we are registering dependencies properly, so that we can ensure that there won't be any surprises happening when resolving items during runtime.
Additional Context
This is not directly related to something a user would see (most likely), but rather to the maintenance of the application and that we ensures that we are doing the correct things when it comes to registering dependencies.
Acceptance Criteria
Related Issues
No response