You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: