DotNetNuke的和Subversion指南 [英] DotNetNuke and Subversion guidelines

问题描述

我GOOGLE了，猛吃，并在这里计算器，看遍了相关的问题和搜查，但我没有找到我要找的。我也搜索文档上DNN。

I've Googled, Binged, and here at StackOverflow, looked through the related questions and searched, but I'm not finding what I'm looking for. I've also searched documentation on DNN.

我正在寻找的是任何指导，从谁在使用DotNetNuke的使用SVN经验的人等（教程，博客，一步一步的设置信息库指令）。

What I'm looking for is any guidance (tutorials, blogs, step-by-step instructions for setting up a repository) etc from people who are experienced in using DotNetNuke with SVN.

我们使用SVN为我们所有的源代码控制，并与标准的应用程序没有问题，因为我们pretty多建库和目录结构与我们的流程工作。这意味着，当我们做网站，在Visual Studio中，我们基于文件的网站，而不是在本地IIS设置它们。它只是使事情变得更容易为我们。

We use SVN for all our source control, and have no problem with standard applications, because we pretty much built the repository and directory structure to work with our processes. This means when we do web sites, in Visual Studio, we do file based web sites, rather than setting them up in the local IIS. It just makes things easier for us.

然而，DNN，看来，即使你得到源$ C ​​$ C，它期待在本地IIS，这意味着额外的头痛为我们设置。

However, with DNN, it appears that even if you get the source code, it is expecting to be set up in the local IIS, which means additional headaches for us.

例如，我们正在所有的源$ C ​​$ C的从我们的本地C驱动器，而到一个服务器上的共享驱动器。这是为了使备份除了我们正常的源代码控制。 （这是一个管理的决定）。所以这意味着我们需要改变虚拟Web应用程序时，我们做出的举动。

For example, we are moving all of our source code off our local C drives, and onto a shared drive on a server. This is to enable backups in addition to our normal source control. (This was a management decision). So that means that we need to change the virtual web app when we make the move.

有没有人想出了一个好办法来解决呢？可以DNN进行设置，以便在Visual Studio中开发Web服务器可以使用，这样我们就可以把它就像任何普通的web应用程序？我失去了一些东西明显？

Has anyone come up with a good way to work around this? Can DNN be set up so that the developer web server in Visual Studio can be used, so that we can treat it just like any normal web app? Am I missing something obvious?

推荐答案

源代码控制

我建议使用单独的项目对DotNetNuke的项目（皮肤，模块，供应商），而不是检查实际网站本身到源代码控制环境（DNN模块会使用WAP风格的项目）。然后，每个开发者可以在他们的开发环境中自己的DotNetNuke的网站和数据库。我也不建议在修改DotNetNuke的核心，让你有一个干净的升级路径。我会建议使用的工具，如红门SQL数据，以便进行比较生成数据库脚本为你的数据，你可以保持源代码控制环境。

I recommend using separate projects for DotNetNuke projects (skins, modules, providers), and not checking the actual web site itself into source control environment (DNN Modules would use the WAP style project). Each developer could then have their own DotnetNuke site and database in their development environment. I also don't recommend making changes to DotNetNuke's core so that you have a clean upgrade path. I would recommend using a tool such as Red Gate's SQL Data Compare in order to generate database scripts for your data that you could keep in the source control environment as well.

<一个href=\"http://weblogs.asp.net/ianrobinson/archive/2008/10/15/creating-dotnetnuke-modules-using-a-web-application-project-wap.aspx\"相对=nofollow>这里是关于建立一个Web应用程序项目的DotNetNuke的模块的更多信息。

测试/分期/生产

在DotNetNuke的保持这些单独的通常是很容易的，因为你已经创建插到DNN网站的模块。我的建议是建立包装和正确版本的模块，这样就可以在干净的测试，分期和生产安装。

Keeping these separate in DotNetNuke is generally very easy because you're already creating modules that plug into a DNN site. My recommendation is to create packaged and properly versioned modules so that you can cleanly install them on test, staging, and production.

您可能要与调查的MSBuild脚本建筑模块包的。另外，这里是使用一些信息<一个href=\"http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryId/1489/DotNetNuke-Tip-Packaging-your-DotNetNuke-Module-using-NANT.aspx\"相对=nofollow>楠自动化DNN模块封装。

You may want to investigate building module packages with MSBuild scripts. Alternatively, Here is some information on using NAnt to automate DNN module packaging.

这篇关于DotNetNuke的和Subversion指南的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！