我应该如何修复 DNN Web 应用程序?

发布于 2024-09-09 05:43:58 字数 347 浏览 3 评论 0原文

我和我的团队正在接管由软件开发供应商开发的 DNN Web 应用程序。

有一些问题,例如 1.用于访问模块的选项卡和配置的冗余非标准数据/API,以及 2.其他一些架构相关的问题。

我的目标是删除我们不需要的东西,并将应用程序引导回 DNN 最佳实践。我还需要使用 DNN 实现工作流引擎,因为目前工作流过程是“半硬编码”的。

我想知道是否有任何设计模式/最佳实践材料(特别是与工作流程有关)我们可以遵循来减轻我们的痛苦并帮助我们确定工作的优先顺序?

编辑:该应用程序的设计并未考虑到单元测试,但只要我可以创建单元测试,我不介意更改它,请帮助我解决有关使用 DNN 进行单元测试的问题。

提前致谢。

Myself and my team is taking over a DNN web application done by a software development vendor.

There are some issues like
1. redundant non-standard data / API to access to tab and configuration of a module, and
2. some other architecture related issues.

My goal is to remove things we don't need and steer the application back to DNN best practice. I also need to implement a work flow engine with DNN because at the moment the work flow process is "semi-hard-coded".

I am wondering if there are any design pattern / best practice material (especially to do with work flow) that we can follow to ease our pain and help us to prioritize work?

EDIT: the application is not designed with unit testing in mind, but I do not mind changing it as long as I can creating unit test, please help me with something about unit testing with DNN too.

Thanks in advance.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

江南烟雨〆相思醉 2024-09-16 05:43:58

最好的情况是制作目录的副本,克隆数据库,并将其单独放置,以便您可以使用它。首先也是最重要的,升级到最新版本,看看购买和构建的模块会发生什么情况。我遇到了一些旧模块的问题,这些问题对于没有或不与最新 dnn 版本兼容的操作至关重要。在所有情况下,快速浏览一下积雪,我发现了替代方案,无论如何结果都更好。

我们不是一个庞大的开发团队,但我发现编写测试用例以确保升级过程中不会丢失功能有很大帮助。

正如我之前提到的,如果您可能不想加快甚至接管自己开发的代码,那么有很多模块可以做很多很酷的事情。可能值得考虑全新安装 DNN 并迁移您必须拥有的内容并从那里开始。

Best case would be to make a copy of the directory, clone the db, and put it separately so you can play around with it. First and foremost, upgrade to the newest version and see what happens with the bought and built modules. I had some problems with old modules that were central to operations not having or not being compatible with the newest dnn version. In all cases, a quick look on snowcovered found me alternates which turned out to be better anyway.

We're not a huge development team, but I found writing out test cases to ensure that functionality is not lost in the upgrade process helped immeasurably.

As I mentioned before, if it's homegrown code that you might not want to bring up to speed or even take over, there are a lot of modules out there that do a lot of cool stuff. Might be worth looking at a fresh install of DNN and migrating what you have to have and going from there.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文