WCSF 适合我吗? [英] Is WCSF for me?

问题描述

我有一个 3 人 .NET 网上商店.多年来，我们开发了许多用于内容管理、博客、电子商务、社交网络等的工具.不过，我们从未真正将软件模块化；因此，将功能从一个站点移植到另一个站点是一项劳动密集型的工作(我们通常只是将代码和其他资产(如 JS、CSS 和图像)从模型站点复制并粘贴到目标站点).我们确实有一个提供许多共享功能的控件库，但是由于无法将 ASPX 或 ASCX 文件编译到控件库中，因此这些页面和控件通常只存在于每个网站中，并从一个站点复制并粘贴到下一个.

I have a 3-man .NET web shop. Over the years we've developed a number of tools for content management, blogging, e-commerce, social network, and so on. We've never really modularized the software, though; so that porting functionality from one site to another is labor-intensive (we typically just copy and paste bits of code and other assets like JS, CSS, and images from the model site to the target site). We do have a control library that provides a lot of shared functionality, but since there's no way to compile ASPX or ASCX files down to the control library, these pages and controls typically just live in each website and get copied and pasted from one site to the next.

我们想重新构建我们的整个平台，以便更轻松地标准化和重用模块.理想情况下，我希望能够 xcopy 包含模块所需的所有内容的文件夹，并让目标网站识别它并在应用程序启动时注册它.

We'd like to re-architect our whole platform to make it easier to standardize and reuse modules. Ideally I'd like to be able to xcopy a folder containing everything a module needs, and have the target website recognize it and register it on application start.

此外，我想保留我们目前拥有的一些灵活性，以便可以针对特定站点轻松自定义模块的功能(而不仅仅是 CSS 和母版页).场景可能包括向联系人模块添加自定义字段，或在博客评论表单上收集自定义信息.

Additionally, I'd like to preserve some of the flexibility we currently have, so that a module's functionality (and not just the CSS and master pages) can be easily customized for a particular site. Scenarios might include adding a custom field to a Contacts module, or collecting custom information on a blog comment form.

最后，我希望能够在基本代码和每个网站的自定义之间划清界限，这样我们只需将核心代码升级到最新版本，就可以轻松地将现有网站升级到最新版本的核心软件日期.我会看到核心代码(包括公共资产、代码和 ASPX/ASCX 文件)存在于每个网站项目中，但通过源代码控制进行同步.

Finally, I would want to be able to draw a clear line between the base code and each website's customizations, so that we can easily upgrade an existing site to the latest version of the core software by just bringing the core code up to date. I'd see the core code (including common assets, code, and ASPX/ASCX files) living in each website project, but being synced up via source control.

现在，我可以很清楚地看到我们将如何自行构建和编码；但是，我想知道 Web 客户端软件工厂 (WCSF) 模式 是否会给我们带来很多好处我们会需要.根据您使用 WCSF 的经验，您认为它适合我在这里描述的场景吗?从快速阅读来看，它似乎为模块化问题提供了一个很好的解决方案，但尚不清楚它是否会提供定制模块的直接方法.

Now, I can see pretty clearly how we would structure and code this all ourselves; however, I'm wondering if the Web Client Software Factory (WCSF) pattern would buy us a lot what we would need. From your experience using WCSF, do you think it would be right for the scenario I describe here? From a quick read, it seems like it would provide a good solution to the modularization problem, but it's not clear if it would provide a straightforward way of customizing a module.

推荐答案

回答这个问题的最好方法是深入研究并进行一些实验——这不是浪费时间，而是对研究的投资.使用 WCSF 与传统架构进行一些并发开发，看看哪个效果最好.

The best way for you to answer this is to dive in and experiment a bit -- it's not a waste of time, it's an investment in research. Do some concurrent development with WCSF vs. your conventional architecture, and see which plays best.

这篇关于WCSF 适合我吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！