简体   繁体   English

如何管理MS Dynamics 365 CRM门户自定义代码?

[英]How to manage MS Dynamics 365 CRM Portal custom codes?

I would like to know how to auto manage portal's custom code just like in TFS/VSTS? 我想知道如何像TFS / VSTS中一样自动管理门户网站的自定义代码

At present ,I am using XRMToolbox to manage ,push or pull portal's code into CRM Instance but disadvantage is code checkin and checkout. 目前,我正在使用XRMToolbox来管理,推送或将门户网站的代码拖入CRM实例,但缺点是代码签入和签出。

Can anyone help me in this to manage a code with auto pull and push option into CRM instance with checkin ,checkout options? 谁能在这方面帮助我管理带有检入,检出选项的自动拉入和推入CRM实例的代码吗?

Thanks in Advance! 提前致谢!

I'm afraid the XRMToolbox plugin doesn't support it yet. 恐怕XRMToolbox插件尚不支持它。

Ref: https://github.com/MscrmTools/MscrmTools.PortalCodeEditor/issues/13 参考: https : //github.com/MscrmTools/MscrmTools.PortalCodeEditor/issues/13

But there is no stopping you from creating your own pipeline - at the end of the day portal code is just bunch of Crm entities. 但是并不能阻止您创建自己的管道-最终,门户代码只是一堆Crm实体。 Part of Crm SDK is configuration migration tool - last version is here: Crm SDK的一部分是配置迁移工具-最新版本在这里:

https://www.nuget.org/packages/Microsoft.CrmSdk.XrmTooling.ConfigurationMigration.Wpf https://www.nuget.org/packages/Microsoft.CrmSdk.XrmTooling.ConfigurationMigration.Wpf

So the idea is: 因此,想法是:

1) Get this tool 1)获取此工具

2) Define entities you want to backup & create schema xml file for them. 2)定义要备份的实体,并为其创建架构xml文件。 I think you'd want adx_webpage, adx_webfile, adx_pagetemplate (and all attributes from them) 我认为您需要adx_webpage,adx_webfile,adx_pagetemplate(以及它们的所有属性)

3) Export data using this schema - this exports them to .zip package that contains simple structure (schema file and data file); 3)使用此架构导出数据-这会将它们导出到包含简单结构(模式文件和数据文件)的.zip包; so you can unzip it and store in your git branch (pull) 因此您可以将其解压缩并存储在git分支中(拉出)

4) For push zip this file and again use configuration migration tool to import the data 4)对于该文件,请使用zip推送,然后再次使用配置迁移工具导入数据

This gives you also an opportunity to have separate dev version of portal code and production version of portal code (which is always a good thing). 这也使您有机会获得独立的门户网站代码开发版本和门户网站代码的生产版本(这总是一件好事)。

Portals code is made up of configuration changes to a solution (which can be extracted as xml) and data (records such as web pages, web roles etc.) 门户网站代码由解决方案的配置更改(可以提取为xml)和数据(如网页,Web角色等记录)组成。

There are several tools available to help you source control both. 有几种工具可帮助您同时进行源代码控制。

xrm-ci-framework provides automation tools to extract your CRM solution as xml, and then source control it. xrm-ci-framework提供了自动化工具来将您的CRM解决方案提取为xml,然后对其进行源代码控制。 You can do this locally or in the cloud with Azure DevOps or other. 您可以在本地或使用Azure DevOps或其他工具在云中执行此操作。

msbuild-xrm-sourcecontrol is similar. msbuild-xrm-sourcecontrol与之类似。 It integrates into Visual Studio to help you extract CRM customisations locally. 它集成到Visual Studio中,以帮助您在本地提取CRM定制。 It also has a partner project xrm-datamigration which helps you extract data from CRM, version control it and deploy it to other environments in your release pipeline. 它还有一个合作伙伴项目xrm-datamigration ,可以帮助您从CRM中提取数据,进行版本控制并将其部署到发布管道中的其他环境。 Both have documentation on the GitHub pages I've linked; 两者都在我链接的GitHub页面上有文档; this blog post is informative too. 该博客文章也提供了很多信息。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM