DevOps for Dynamics 365 Customer Engagement (CE) is becoming a popular topic. The goal of this project is to help Dynamics 365 CE solution builders understand and accelerate their implementation of DevOps practices with Dynamics CE and VSTS.
MIT License
89
stars
28
forks
source link
Create a "starter solution" for "getting started with source control" #30
While it is nice (and necessary) to learn how to deploy an existing application, what's missing is the ability to understand how to get the initial "skeleton" solution setup to be in a position to source control all the items. To that end, create a Visual Studio solution that contains a set of projects for the following:
Web Resources
Plugins
SolutionPackage
DeploymentPackage (i.e. Package Deployer project)
InitialData (i.e. using DataMigrationUtility.exe)
The intended use case would be:
-Developer downloads "skeleton" Visual Studio solution/projects
-Developer commits to their source control repository
-Developer can manually create the web resource and plugin assets or use tools like spkl (https://github.com/scottdurow/SparkleXrm/wiki/spkl), or others to bring existing assets down.
-Developer can use tools like SolutionPackager (https://docs.microsoft.com/en-us/dynamics365/customer-engagement/developer/compress-extract-solution-file-solutionpackager) or spkl (which provides is a wrapper around SolutionPackager) to bring configurations into source control
-Developer is able to "get started" faster and now focus on using build and deployment automation from VSTS pointing to their source control system.
devkeydet
commented
6 years ago
While it is nice (and necessary) to learn how to deploy an existing application, what's missing is the ability to understand how to get the initial "skeleton" solution setup to be in a position to source control all the items. To that end, create a Visual Studio solution that contains a set of projects for the following: Web Resources Plugins SolutionPackage DeploymentPackage (i.e. Package Deployer project) InitialData (i.e. using DataMigrationUtility.exe)
The intended use case would be: -Developer downloads "skeleton" Visual Studio solution/projects -Developer commits to their source control repository -Developer can manually create the web resource and plugin assets or use tools like spkl (https://github.com/scottdurow/SparkleXrm/wiki/spkl), or others to bring existing assets down. -Developer can use tools like SolutionPackager (https://docs.microsoft.com/en-us/dynamics365/customer-engagement/developer/compress-extract-solution-file-solutionpackager) or spkl (which provides is a wrapper around SolutionPackager) to bring configurations into source control -Developer is able to "get started" faster and now focus on using build and deployment automation from VSTS pointing to their source control system.