I know a Windows Service cannot interact with the desktop, but is it acceptable to use Prism objects (EventAggregator, Unity) in a Windows Service?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I know a Windows Service cannot interact with the desktop, but is it acceptable to use Prism objects (EventAggregator, Unity) in a Windows Service?
Prism and Unity are 2 different things (although often used in combination):
Unity is an inversion of control (IoC) container, it is not necessarily only for GUI applications, so you can definetly use this in your service.
Prism privides facilities for applications with a GUI, you could use it in your service though if you don’t bother about the dependency to PRISM.