We are developing intranet base solution in ASP.NET MVC. It will be deployed across client's own internal network hence respective employee of client can use it.
我们正在ASP.NET MVC中开发Intranet基础解决方案。它将部署在客户自己的内部网络中,因此客户的相应员工可以使用它。
As it is IIS based intranet application, one can easily copy files and configure IIS on other server. So what are the different solution available to prevent this.
由于它是基于IIS的Intranet应用程序,因此可以轻松复制文件并在其他服务器上配置IIS。那么有什么不同的解决方案来防止这种情况发生。
Thank you in advance.
先谢谢你。
1 个解决方案
#1
0
Generally when you are publishing the ASP.NET MVC web app, you can publish the version in dlls.
通常,在发布ASP.NET MVC Web应用程序时,可以在dll中发布该版本。
So Instead of creating a single Web App, you can create a new dll file where you are going to compile all the Models of the App and save it in a dll).
因此,您可以创建一个新的dll文件,而不是创建单个Web应用程序,您将编译应用程序的所有模型并将其保存在DLL中。
Then coming back to your original solution you will add the reference to this dll so no logic can be taken of your solution.
然后回到原始解决方案,您将添加对此dll的引用,因此无法对您的解决方案进行逻辑处理。
#1
0
Generally when you are publishing the ASP.NET MVC web app, you can publish the version in dlls.
通常,在发布ASP.NET MVC Web应用程序时,可以在dll中发布该版本。
So Instead of creating a single Web App, you can create a new dll file where you are going to compile all the Models of the App and save it in a dll).
因此,您可以创建一个新的dll文件,而不是创建单个Web应用程序,您将编译应用程序的所有模型并将其保存在DLL中。
Then coming back to your original solution you will add the reference to this dll so no logic can be taken of your solution.
然后回到原始解决方案,您将添加对此dll的引用,因此无法对您的解决方案进行逻辑处理。