There is an intranet based ASP.NET application that is deployed to a server (IIS) and a group of clients (about ten). The end user can then decide to either connect to the local application (deployed to their local machine) or the server version. I do not understand the reasoning for doing this. My question is: is this common practice?
有一个基于Intranet的ASP.NET应用程序，它部署到服务器（IIS）和一组客户端（大约十个）。然后，最终用户可以决定连接到本地应用程序（部署到其本地计算机）还是服务器版本。我不明白这样做的原因。我的问题是：这是常见做法吗？
2 个解决方案
#1
2
yes, it is a common practice to verify the performance of the application. Each client will have their own settings and as per process, application should not break in any kind of environment. it is always beneficial to put a server version and a local version.
是的，通常的做法是验证应用程序的性能。每个客户端都有自己的设置，并且根据流程，应用程序不应该在任何类型的环境中中断。放置服务器版本和本地版本总是有益的。
#2
0
If the clients are laptops, and the application supports disconnected data sets and synchronization, it would make sense. Typically you'd see something like this when the client machines are taken off-network to be used at a remote work site.
如果客户端是笔记本电脑，并且应用程序支持断开连接的数据集和同步，那么这将是有意义的。通常，当客户端计算机脱离网络以在远程工作站点使用时，您会看到类似的内容。
#1
2
yes, it is a common practice to verify the performance of the application. Each client will have their own settings and as per process, application should not break in any kind of environment. it is always beneficial to put a server version and a local version.
是的，通常的做法是验证应用程序的性能。每个客户端都有自己的设置，并且根据流程，应用程序不应该在任何类型的环境中中断。放置服务器版本和本地版本总是有益的。
#2
0
If the clients are laptops, and the application supports disconnected data sets and synchronization, it would make sense. Typically you'd see something like this when the client machines are taken off-network to be used at a remote work site.
如果客户端是笔记本电脑，并且应用程序支持断开连接的数据集和同步，那么这将是有意义的。通常，当客户端计算机脱离网络以在远程工作站点使用时，您会看到类似的内容。