Hi Rafael,
Basically the decision mainly depends on what you and your team are more comfortable with each framework, and if the main features of your app would be provided by Prism in a simple manner.
Firstly, the technologies you mentioned you would be using are supported by Prism. Indeed, Prism already provides several functionalities regarding dependency injection with Unity. You can find some related information on the following MSDN Prism chapter:
I would suggest you then to checkout the main features provided by Prism in the following MSDN Prism Guide chapters in order to evaluate how it would help you implement the application requirements:
Regards.
Gabriel Ostrowsky
https://blogs.southworks.net/gostrowsky
Basically the decision mainly depends on what you and your team are more comfortable with each framework, and if the main features of your app would be provided by Prism in a simple manner.
Firstly, the technologies you mentioned you would be using are supported by Prism. Indeed, Prism already provides several functionalities regarding dependency injection with Unity. You can find some related information on the following MSDN Prism chapter:
I would suggest you then to checkout the main features provided by Prism in the following MSDN Prism Guide chapters in order to evaluate how it would help you implement the application requirements:
- 2: Initializing Prism Applications
- 4: Modular Application Development
- 7: Composing the User Interface
- 8: Navigation
Regards.
Gabriel Ostrowsky
https://blogs.southworks.net/gostrowsky