为 Asp.Net 人员开发 Commerce Server
我希望粗略地了解通常涉及在 MS Commerce Server 上创建一个相当大的商店以及一些外部系统集成的开发活动，以及它与标准 asp.net 开发有何不同
1) 您通常是从头开始还是从头开始来自“入门站点”
2) 您通常是否创建自定义模板来访问商店项目以通过 .net 对象显示，或者您是否需要使用提供的可模板化 CS Web 控件
3) 商店站点的模板和代码工件（aspx 等） ）xcopy-部署到不同的环境（测试/阶段/产品）？或者是像 Sharepoint 中那样通过部署打包完成
谢谢
I'm looking to get a rough overview of the development activities typically involved in creating a fairly large store with some external systems integration on MS Commerce Server and how it differs from standard asp.net development
1) Do you typically start from scratch or start from the "starter site"
2) Do you typically create custom templates which access the store items to display through .net objects or do you need to use provided templateable CS webcontrols
3) Are templates and code artifacts for the store site (aspx's etc.) xcopy-deployed to the different environments (test/stage/prod)? Or is it done like in Sharepoint with deployment packaging
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
1) Commerce Server 附带一个共享点扩展工具包，其中包含一组相当强大的电子商务 Web 部件。了解代码和开发定制流程需要一些时间，但我认为这比从头开始构建这些组件所需的时间要少得多。
2) 不确定你的意思，但 Commerce Server 的架构确实从 UI 中抽象了数据。我们正在直接更新 Commerce Server Web 部件 HTML 以进行 UI 定制。
3) 首先，我们将自定义代码直接复制到共享点虚拟目录（bin 和 UserControls）中。现在我们已经设置了一个疯狂的、精心设计的自动化构建/打包脚本化 wsp 构建环境。我认为这种方法很好采用，因为我们的开发团队能够使用和学习可扩展性工具包，而我们的脚本和环境团队则了解他们需要什么。否则，您将面临一个线性流程，其中所有环境和升级流程都必须就位，然后才能开始自定义代码。
1) Commerce Server comes with a sharepoint extensibility kit that contains a fairly robust set of e-commerce web parts. There is some ramp up time on getting to know the code and developing customization processes, but I think this is far less time than what would be required to build these components from scratch.
2) Not sure what you mean here, but Commerce Server's architecture does abstract data from UI. We are updating the Commerce Server web part HTML directly for our UI custimziations.
3) At first we were copying customized code directly into the sharepoint virtual directories (bin and UserControls). Now we've setup a crazy elaborative automated build/packaging scripted wsp building environment. I think this approach was good to take because our development team was able to work with and learn the extensbility kit while our scripting and environment teams figured what they needed to. Otherwise you have a linear process where all the enviroments and promotion processes have to be in place before you can start customizing code.