问题描述
我公司正在重新设计我们的内部网站，并决定与DotNetNuke的去为实施解决方案。现在，在过去的一年，我一直想在这里开车的改变关于保持开发，测试和生产环境中分离出来。我也希望所有的相关的网站修改进入SVN，这包括数据定义的页面和模块的布局。
My company is redesigning our intranet site and decided to go with DotNetNuke as the solution to implement. Now for the past year I've been trying to drive changes here about keeping development, testing, and production environments separate. I also want all changes that are relevant to the site to go into SVN, this includes data that defines the page and module layout.
有没有人尝试与DotNetNuke的前尝试吗？并且没有任何人有任何其他提示开发DotNetNuke的网站？
Has anyone attempted trying this with dotnetnuke before? And does anyone have any other tips for developing dotnetnuke sites?
推荐答案
源代码控制
我建议使用单独的项目对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.
以下是关于建立一个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.
以下是关于使用楠自动化DNN模块封装一些信息。
这篇关于DotNetNuke的开发环境和部署的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！