Orchard:完整来源与否?

发布于 2024-12-01 05:27:15 字数 356 浏览 2 评论 0原文

我们将使用 Orchard 作为特定客户的基地。我们是一家运行 VS2K10 的 C# 商店。我们将按照我们项目的规范将其放入版本控制系统中。

也就是说,我们将根据客户的需求创建自定义模块。这里每个人都推荐什么方法?

  1. 从 CodePlex 获取完整源代码并检查
  2. 是否仅下载 Orchard Web 代码(类似于 Web 平台安装程序)

问题 #1 是代码库相当大,但它允许我们在开发时在本地调试站点。

#2 有哪些注意事项?缺乏调试?

我很好奇每个人对此会采取什么方法。我倾向于选择#1,获取完整的源代码,将其放入 SVN,然后以此为基础进行构建。

想法?

We're going to be using Orchard as a base for a particular client. We're a C# shop running VS2K10. We'll throw it in our version control system as per the norm for our projects.

That said, we'll be creating custom modules based on the needs of our clients. What approach does everyone here recommend?

  1. Get full source from CodePlex and check that in
  2. Download just the Orchard web code (similar to Web Platform Installer)

Problem with #1 is that the code base is rather large, but it will allow us to debug the site locally when developing.

What are the caveats with #2? Lack of debugging?

I'm curious what everyone's approach would be for this. I'm inclined to go with #1, get the full source, throw it in SVN, and build off of that.

Thoughts?

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

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

发布评论

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

评论(3

心如狂蝶 2024-12-08 05:27:15

如果您要使用 Visual Studio 开发模块,只需使用完整的源代码。磁盘空间很便宜。
第 2 点需要注意的是,它非常不舒服。何苦呢?

If you are going to develop modules using Visual Studio, just use the full source code. Disk space is cheap.
Caveats with #2 are that it's immensely less comfortable. Why bother?

不念旧人 2024-12-08 05:27:15

我使用完整的源代码版本,但我只将我正在处理的模块和主题检查到源代码管理中。

我最初只使用网络代码,但发现自己遇到了很多小问题,当使用完整源代码时,这些问题更容易追踪。

我发现只有对我正在处理的内容进行源代码控制才能更轻松地更新到更高版本的 Orchard。

I use the full source version, but I only check the modules and themes that I'm working on into source control.

I did originally use just the web code, but found myself running into lots of little problems that were much easier to track down when using the full source.

I found that only source controlling the stuff I was working on made updating to later versions of Orchard much easier.

爱人如己 2024-12-08 05:27:15

我不是软件工程师,但我会这样做:

  • 获取源代码。
  • 将其添加到您的 VS 解决方案和源代码管理中。
  • 不要引用项目。
  • 在该项目上添加一个生成后事件,以将 dll 和符号(用于调试)复制到项目的文件夹中,否则将引用该项目。

如果它在该项目程序集中的类中崩溃,那么您将能够指定源代码文件,因为您获得了符号,并且由于您不会定期修改该项目,因此您的 VS 不会重建它每次。如果您想节省一些内存,您甚至可以卸载该项目,无论它多么微不足道。

I'm no software engineer, but here is what I would do :

  • Get the source code.
  • Add it in your VS solution and source control.
  • Do NOT reference the project(s).
  • Add a post-build event on that project to copy the dll and the symbols (for debug) in the folders of the project that would otherwise refer this one.

If it crashed in a class from that project's assembly, you'll be able to specify the source code files since you got the symbols, and since you won't be modifying that project on a regular basis, your VS won't rebuild it every time. You could even unload the project if you want to save some memory, however trivial it might be.

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