Best Approach to Writing an Enterprise Application with Windows and Web Interfaces?

Question

I am working on the architecture of a large enterprise application that will be based on the latest .NET and SQL Server technologies. This application will be used by the general public, members, employees and managers.

In the past, we used RemoteApp / RemoteDesktop to communicate with a local Windows Forms application running on a server. Simple but awkward.

• Some aspects of the application should be presented as a web application.
• Some aspects of the application should be presented as a Windows Forms application.

A Windows application should be distributed to a geographically dispersed audience (branch managers and employees).

Here are the tasks of the Windows interface:

• Thin client, where it behaves similar to a web browser (UI only)
• all processing performed on the server
• use the same code base as in the web application - only a different user interface
• Simple development (easy to maintain and grow)

What are some of the best approaches to this?

(I spent a lot of time looking at .NET Remoting and then WCF, but I don't have enough experience that I hope you can bring.)

Thank!

Answer 1

, - WCF. (WinForms) WCF , -, , WinForms. , -, -, WCF .

, , - . , ASPX-. , , WCF.

, -, . - . , WCF, - . . , , .

WCF -, - . , , ( WCF, -, , ).

-, , , , WCF , .

WCF , WCF. -.

:

1) - .svc , . (basicHTTPBinding, SOAP), (webHTTPBinding, REST). , , , , , .

2) , -, -. HTTP , XML- , - . XML . , - -, - -, ( WCF XML ). , - , .

3) , . IIS Active Directory. -, , , Active Directory, . (HTTP Basic Digest auth , - / , . SSL !)