Hi,
Based on your description I am assuming the user needs to enter the authentication server's address along with the login and password in the LoginView.
In that case a possible approach to be able to maintain the chain of dependencies is to inject in the view model a LoginServiceProxy instead of the real WCF Service that connects to the server. Like this, the LoginServiceProxy could be constructed and injected by Unity in an "uninitialized" state. When the user enters his credentials along with the server's address the view model could pass that information to the proxy service that will be in charge of initializing the real WCF Service and authenticating against the server.
How to configure and set-up the real WCF Service to connect to the corresponding server is more of a WCF-specific topic; therefore I believe you might find better support for that part in the Windows Communication Forums forums:
Regards,
Damian Cherubini
http://blogs.southworks.net/dcherubini
Based on your description I am assuming the user needs to enter the authentication server's address along with the login and password in the LoginView.
In that case a possible approach to be able to maintain the chain of dependencies is to inject in the view model a LoginServiceProxy instead of the real WCF Service that connects to the server. Like this, the LoginServiceProxy could be constructed and injected by Unity in an "uninitialized" state. When the user enters his credentials along with the server's address the view model could pass that information to the proxy service that will be in charge of initializing the real WCF Service and authenticating against the server.
How to configure and set-up the real WCF Service to connect to the corresponding server is more of a WCF-specific topic; therefore I believe you might find better support for that part in the Windows Communication Forums forums:
Regards,
Damian Cherubini
http://blogs.southworks.net/dcherubini