WindowsForms orASP.Net

[Mike Lopez]

Hello.

For an Intranet application, what would be some reasons NOT to use WF and
use ASP.Net instead?

I can't think of any.

Thanks in advance,

Mike

 

[Carlos J. Quintero [.NET MVP]]

Only if you want to avoid .NET Framework and app deployment to the clients.
But if client satisfaction is what matters, rich Windows Forms apps are
better, IMO.

--

Carlos J. Quintero

MZ-Tools 4.0: Productivity add-ins for Visual Studio .NET
You can code, design and document much faster.
http://www.mztools.com

 

[Jeffrey Tan[MSFT]]

Hi Mike,

Yes, I agree with Carlos's statement. Actually, this is a big topic about
the difference between B/S and C/S, there are a lot of discussion over the
internet on this topic. The short answer is that Asp.net is B/S
architecture, which requires nothing to be installed on client machine,
while C/S architecture will have the advantage of rich client
representation, which is the weak side of IE(B/S architecture).

Furthermore, there is the third choice: Smart Client, which has some
advantage of both B/S and C/S. For more information about smart client, I
suggest you search "smart client" in msdn.microsoft.com or www.google.com

Hope this makes sense to you.
======================================
Thank you for your patience and cooperation. If you have any questions or
concerns, please feel free to post it in the group. I am standing by to be
of assistance.

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.