开发 DotNetNuke CMS 网站
我是一名初级开发人员，今年刚刚大学毕业。 我正在与一些人私下合作，我刚刚得到一个使用 DotNetNuke 开发的音乐网站。 我有一些使用 DotNetNuke 的经验，我通过制作小模块来处理网页上的某些功能，但我以前从未使用过整个网站。 如果有人能给我一些关于如何完成这个项目并回答我的一些问题的指导，我会很高兴。
开发 dotnetnuke 网站涉及哪些步骤？
从开发人员的角度来看，开发 dotnetnuke cms 网站与从头开始开发的 cms 网站有什么不同？
当涉及到数据库时，您是在开发新功能时逐步向数据库添加表，还是提前计划一切并立即创建表和存储过程？
I am a junior developer and I have just graduated from university this year. I am working private with some people and I have just been given a music website to develop using DotNetNuke. I have a some experience using DotNetNuke which I have gained making small modules that take care of certain functionality on a webpages but I have never taken on a whole website before. I would love it if some one would give me some guidence on how to approach this project and answer some of my questions.
What are the steps involved in developing a dotnetnuke website?
How different is it from a developers perspective to develop a dotnetnuke cms website from a cms website which was developed from scratch?
When it comes to the database do you add tables to the database incrementally as you develop new functionality or do you plan everything in advance and create tables and stored procedures at once?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
非常。 当您开始使用已建立的 CMS 时，您将继承大量已解决问题的解决方案。 就 DNN 而言，您拥有一个可供您使用的实质性框架。 重点将更多地放在学习和利用现有的 API/功能上。 如果您是从头开始，那么您就是在自己提供基础。 使用已建立的 CMS 并不一定比其他更好 - 这取决于您想要实现的目标。 如果您需要对一切进行精细控制并且想要获得良好的学习体验，那么自己动手可能是最好的方法。
无论您的项目是什么，我都建议在需要时而不是之前做事情。 我认为“提前做好一切”是不可能/可怕的。 这个问题的核心实际上是定义您的开发过程 - 我认为这不一定与其他项目有任何不同。 我喜欢定义我想要的功能，根据它们之间的关系来组织它们（由于依赖关系等，这应该是第一位的），然后开始一次实现一个功能，并给予每个功能所需的关注。
Very. When you're starting with an established CMS you're inheriting solutions to tons and tons of solved problems. In the case of DNN, you have a substantial framework at your disposal. The focus will be more on learning and leveraging the existing API/features. If you're starting from scratch you're providing that foundation yourself. Using an established CMS is not necessarily better than the other - it depends on what you're trying to accomplish. If you require fine-grained control over everything and you want a great learning experience, rolling your own may be the best way to go.
No matter what your project is, I'd suggest doing things as they are needed and not before. I think "doing everything in advance" would be impossible/horrible anyway. The heart of this question is really going to be defining your development process - I don't think this would necessarily be any different than in other projects. I like to define the features I want, organize them based on their relation to each other (which should come first due to dependencies, etc) and start implementing them one at a time and give each one the attention it needs.
您可能还想查看 Lee Sykes 关于使用 OpenWebStudio 进行模块开发的教程。 然而，我更多的是在设计方面，主要是换肤、配置、SE 优化站点以及将客户需求与我们的许可第三方模块库相匹配。 然而，DNN 社区非常支持并且非常有帮助。 那里有一些很棒的资源，而且我发现核心开发团队的几篇博客对于帮助我了解 DNN 框架至关重要。
坚持下去，不要害怕提问。
参考资料：
www.dnncreative.com - Lee Sykes 的网站，关于DNN 系统的操作方法。 恕我直言，每年订阅是非常值得的。
www.dotnetnuke.com - DNN 社区的主站点
www.snowcovered.com - 中央 (AFAIK) 站点，许多模块开发人员在此销售他们的产品，从皮肤到模块的一切产品。
You may also want to look into Lee Sykes' tutorials on module development using OpenWebStudio. However, I'm more on the design end, mainly just skinning, configuring, SE optimizing sites and matching client needs to our library of licensed 3rd party modules. However, the DNN community is VERY supportive and VERY helpful. There are some great resources out there, and I've found several blogs by the core development team to be essential for helping me wrap my head around the DNN framework.
Keep with it, and don't be scared to ask questions.
References:
www.dnncreative.com - Lee Sykes' Site, many tutorials on the how-tos of the DNN system. It's well worth the yearly subscription IMHO.
www.dotnetnuke.com - The main site for the DNN community
www.snowcovered.com - Central (AFAIK) site where many module developers sell their products, everything from skins to modules.