从 DotNetNuke 中删除站点
我的公司有一个注册网站，目前位于 DotNetNuke 中。我被指示“从网站中删除核武器”，但从我读到的所有内容来看，该网站位于 dnn 中，而不是相反。
有没有人必须从 dnn 迁移网站，如果是这样，您能给我一些资源或提供一些 insite 来帮助我开始吗？
该网站是dnn 5.04
My company has a enrollment website that is currently in DotNetNuke. I've been directed to "strip out nuke from the site" but from everything I've read it is the opposite that the site is in dnn not the other way around.
Has anyone had to migrate a site from dnn and if so can you point me towards some resources or give some insite to get me started?
The site is dnn 5.04
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
如果您想将内容精简为绝对的骨架（HTML、图像、JavaScript），您可以使用基本上将整个网站复制到本地计算机的工具，例如 HTTrack。
下载该应用程序，为其提供 DNN 网站的 URL，它会抓取整个网站，单独下载每个页面及其任何图像和脚本。您将（理论上）留下一个包含所有内容页面的完整网站，您可以在纯文本编辑器中对其进行编辑。
所有用户管理、角色管理、内容管理、仅管理区域、受保护内容等都不会通过此方法进行，但无论您是否从 DNN 迁移到普通的静态 HTML 网站，情况都会如此。
If you want to strip things down to absolute bare bones (HTML, images, JavaScript), you could use a tool that basically copies down an entire website to your local machine, such as HTTrack.
Download the app, give it your DNN website's URL, and it'll spider the entire website, download each page individually, along with any of its images and scripts. You'll be (theoretically) left with a full website containing all your content pages, which you can edit in a plain text editor.
All the user management, role management, content management, admin only areas, protected content, etc. will not carry over with this method, but that will be the case regardless if you're moving from DNN to a normal static HTML website.
“注册网站”听起来更像是一个应用程序，而不是静态 HTML 网站，如果是这样的话，那么仅仅获取呈现的 HTML 就不是最佳选择，因为您不会获得任何功能。我的方法是首先找出他们为什么希望将其从 DotNetNuke 中撤出。也许它实施得不好，他们指责 DNN，而实际上问题在于它的构建方式。 DNN 可能是一个很好的解决方案，最好说服他们保留 DNN，但改进实施。
如果您确实需要从 DNN 中提取应用程序，并且注册部分是作为自定义模块构建的，则将自定义模块的 ascx 文件转换为正常的 .net 用户控件应该相当容易。
如果注册应用程序是使用某种形式的表单模块构建的，那么您可能需要从头开始重建它。
An "enrollment website" sounds more like an application than a static HTML site and if that's the case then just grabbing the rendered HTML isn't going to be the best option as you wouldn't get any of the functionality. My approach would be to first find out why they want it pulled out of DotNetNuke. Perhaps it was poorly implemented and they are blaming DNN when the problem was actually how it was built. DNN may be a good solution and it might be best to convince them to leave it as DNN but improve the implementation.
If you do need to pull an application out of DNN and the enrollment piece was built as a custom module, it should be fairly easy to convert the ascx files of the custom module to normal .net User Controls.
If the Enrollment application was built using a Forms Module of some form, then you will likely need to rebuild it from scratch.