如何使用SVN推出ASP.NET网站?

时间:2022-08-10 03:21:34

We use ASP.NET / C#.

我们使用ASP.NET / C#。

We work locally, test locally, check in our code and binaries through SVN.

我们在本地工作,在本地测试,通过SVN检查我们的代码和二进制文件。

On our server, we checkout the latest 'build' from SVN directly into our IIS web directory.

在我们的服务器上,我们将SVN中的最新“构建”直接签入我们的IIS Web目录。

Is this a good practice, or is there something else we should be doing for rollouts?

这是一个很好的做法,还是我们应该为推出做其他事情?

3 个解决方案

#1


3  

Why check it out? You could easily create a script to export it (clean, no .svn directories, no mess) to the IIS directory.

为何查看?您可以轻松地创建一个脚本以将其导出(干净,没有.svn目录,没有混乱)到IIS目录。

SVN supports an export feature, SVN Export

SVN支持导出功能SVN Export

Edit: Just noticed this has been covered before on SO: Link

编辑:刚刚注意到之前已经覆盖了SO:Link

#2


2  

I theory there is no problem with this practise. I imagine it keeps your rollouts simple and you are able to check which revision is currently live at any given time.

我的理论认为这种做法没有问题。我想它可以简化你的推出,你可以在任何给定的时间检查当前的版本。

Perhaps others will raise pertinent issues but I really can't see any major reasons not to do this.

也许其他人会提出相关问题,但我真的看不出任何主要原因不这样做。

#3


1  

I do the same thing with 1 exception...I first checkout the latest build to a dev version of the site on the same server just to make sure there aren't any weird issues on the server-side. It's rare that ever are any, but it's happened before.

我做了同样的事情,有一个例外......我首先在同一台服务器上检查最新版本的网站开发版本,以确保服务器端没有任何奇怪的问题。它是罕见的,但它发生在以前。

Not sure if there's a better way of doing it, but it's worked well for me so far.

不确定是否有更好的方法,但到目前为止它对我来说效果很好。

#1


3  

Why check it out? You could easily create a script to export it (clean, no .svn directories, no mess) to the IIS directory.

为何查看?您可以轻松地创建一个脚本以将其导出(干净,没有.svn目录,没有混乱)到IIS目录。

SVN supports an export feature, SVN Export

SVN支持导出功能SVN Export

Edit: Just noticed this has been covered before on SO: Link

编辑:刚刚注意到之前已经覆盖了SO:Link

#2


2  

I theory there is no problem with this practise. I imagine it keeps your rollouts simple and you are able to check which revision is currently live at any given time.

我的理论认为这种做法没有问题。我想它可以简化你的推出,你可以在任何给定的时间检查当前的版本。

Perhaps others will raise pertinent issues but I really can't see any major reasons not to do this.

也许其他人会提出相关问题,但我真的看不出任何主要原因不这样做。

#3


1  

I do the same thing with 1 exception...I first checkout the latest build to a dev version of the site on the same server just to make sure there aren't any weird issues on the server-side. It's rare that ever are any, but it's happened before.

我做了同样的事情,有一个例外......我首先在同一台服务器上检查最新版本的网站开发版本,以确保服务器端没有任何奇怪的问题。它是罕见的,但它发生在以前。

Not sure if there's a better way of doing it, but it's worked well for me so far.

不确定是否有更好的方法,但到目前为止它对我来说效果很好。