对于.NET部署实践 [英] Deployment practices for .NET
问题描述
我有一个新的应用程序，我希望部署到受管服务器我最近注册了。我想知道什么是部署到它的最佳方式。在我的经验，我已经看到了很多的asp.net应用程序只是把dll文件到服务器。这是如何实现的？
I have a new application i would like to deploy to a Managed Server I have recently signed up for. I would like to know what would be the best way to deploy to it. In my experience I have seen that many of the asp.net applications just push dlls to the server. How is this achieved?.
我有乌龟SVN作为我subversioning系统。我有另一台服务器上的存储库，通常我承诺我的变化，然后在受管服务器更新我发布文件夹，但是这所有在.aspx，解决方案，我相信不需要其他文件。我该怎么办我的设置，让我只推DLL和更新，只有dll文件被更新的时候？
I have Tortoise SVN as my subversioning system. I have a repository on another server and usually i commit my changes and then update my release folder in the managed server but this has all the .aspx, solution and other files I belive are not needed. How can I do my set up so that I only push the dlls and when updating that only dlls are updated?.
我不是这个太清楚，想给这个场景的解释和最佳实践。
I am not too clear on this and would like an explanation and best practices given this scenario.
推荐答案
我曾经面临类似以前的问题和按照以下步骤我每次移动编译后的文件进行增量补丁在我的应用程序的时间。
I have faced similar questions before and follow the below steps every time I move the compiled files for incremental fixes in my application.
-
维护解决方案文件的两个单独的副本 - 本地应用和生产应用
//这是非常重要的，因为一旦你去生产环境。一个副本只有在活的服务器部署本地工作和其他副本。此副本应该是最新的与您的生活服务器副本。
Maintain two separate copies of the solution files - Local Application and Production application //This is very important because once you go to production environment. One copy for your local working and other copy only for deploying in the live server. This copy should be up to date with your live server copy.
请更改文件和编译和测试在您的本地应用程序文件夹/解决方案的应用程序。现在，仅提交您编辑的文件。 SVN将照顾这。它会告诉你一个可能的红色印记为从信息库中的更新present不同的文件。通过这种方式，你可以跟踪哪些被修改的页面。
Make the changes to files and compile and test the application in your local application folder/solution. Now commit only the files that you edited. SVN will take care of this. It will show you a possible "red mark" for the files which differ from the updates present in the repository. In this way you can track the pages which were modified.
现在打开打开你的生产解决方案文件夹，并更新文件夹。这将更新生产应用程序文件夹中的文件。
Now open open your production solution folder and update the folder. This will update the files in production application folder.
现在编译和测试完成的改变。验证如果问题已修复或更改反映同本地应用程序副本。现在构建应用程序，并发布到一个文件夹。
Now compile and test the changes done. Verify if its issue is fixed or the changes are reflected same as the Local application copy. Now build the application and publish to a folder.
要知道修改后的文件：
DLL文件：
按订单修改日期转到该文件夹和的bin位置。这些是要复制并在你的生活中服务器替换的DLL。
Go to the bin location of the folder and "order by" modified date. These are the dlls which are to be copied and replaced with in your life server.
ASPX / ASCX
a）公开SVN生产应用程序文件夹中。右击，然后单击显示日志。这将显示修改/带日期更新了所有的文件。选择最近更新的那些，并记下的位置。
a) Open SVN of production application folder. Right click and click show log. This will show all the files modified/updated with date. Select the ones last updated and note down the location.
b）现在导航到该位置在已发布的文件夹并选择这些文件的文件升/降修改日期的命令。单独替换这些文件到您的LIVE服务器。
b) Now navigate to the location in your published folder and select those files "ordered by" descending/ascending modified date of the files. Replace those files alone to your LIVE server.
注意：这当然不是最好的解决方案，但一般的做法之一，随后整个行业。有可同时跟踪变化和相关文件发布到您发布的文件夹一些其他的插件。但同样，这仅适用，如果你有在同一台机器源$ C $ CS和应用程序文件为您主持从应用程序之一。让我知道，如果你有任何问题，。
Note: This is certainly not the best possible solution, but one of the general practices followed throughout the industry. There are few other plugins which can track changes and publish the relevant files to your published folder. But again ,this is applicable only if you have the source codes and application files in the same machine as of the one you are hosting the application from. Let me know if you have any question in this.
这篇关于对于.NET部署实践的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
