Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Microsoft Dynamics 365 Extensions Cookbook

You're reading from   Microsoft Dynamics 365 Extensions Cookbook Add functionality to existing model elements, source code and finally package and deploy using DevOps

Arrow left icon
Product type Paperback
Published in Jun 2017
Publisher Packt
ISBN-13 9781786464170
Length 462 pages
Edition 1st Edition
Languages
Tools
Concepts
Arrow right icon
Toc

Table of Contents (19) Chapters Close

Title Page
Credits
Foreword
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface
1. No Code Extensions FREE CHAPTER 2. Client-Side Extensions 3. SDK Enterprise Capabilities 4. Server-Side Extensions 5. External Integration 6. Enhancing Your Code 7. Security 8. DevOps 9. Dynamics 365 Extensions 10. Architectural Views 11. Dynamics 365

Using SolutionPackager to save solutions in source control


In this recipe, we will focus on storing a fragmented Dynamics 365 solution in the source control. More specifically, we will be using SolutionPackager to extract a Dynamics 365 solution into a folder that is Git initialized. We will then export an updated solution that had some components removed and demonstrate how the items will be removed from source control.

SolutionPackager is a utility introduced with Dynamics CRM 2013. It allows you to explode a Dynamics CRM\365 solution into small fragments. SolutionPackager also allows you to implode the extracted files back into a zipped solution file.

We primarily chose Git as it is becoming the mainstream distributed version control system, as well as for its ease of use. Git will recognize filesystem changes without the need to check-out files. We will use a local repository without connecting or pushing to a remote repository.

Getting ready

Given that we will be using Git, you will need...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime
Visually different images