Add third-party models to source control from deployable package.
Contents
- Adding Third-party Deployable Package to Source Control
- Updating Third-party Models to Source Control
- For Other Development Machines
Adding Third-party Deployable Package to Source Control
To add third-party models to the source control (TFVC) from the deployable package given by the provider,
-
On your development machine, install the deployable package by following this guide - Install an application (AOT) deployable package on a development environment
-
After the installation, open Visual Studio as administrator.
-
Go to Dynamics 365 menu > Model Management > Refresh Models.
-
To confirm that you have installed the model, go to the Application explorer and type in:
model:<ModelName>
. The installed objects should be listed in italics, which means you don’t have access to the metadata. -
Open Source Control Explorer by clicking View > Other Windows > Source Control Explorer. Or through the Team Explorer window > Project > Source Control Explorer.
-
Navigate to the metadata folder that is mapped on your development machine, such as
MyProject/Trunk/Development/Metadata
. -
Right-click the Metadata folder, and then click New Folder. Create a folder for the third-party Model.
-
Check in the new folder created.
-
Update workspace mapping, map the new folder from source control to the metadata folder of the third-party Model.
From:
$/Project/Development/Metadata/ISVModel
To:
C:\AOSService\PackagesLocalDirectory\ISVModel
-
Select No on the Workspace Modified prompt.
-
On the Source Control Explorer, right-click the created folder, and then click Add Items to Folder.
-
In the Add to Source Control dialog box, select all (Ctrl+A) the folders except XppMetadata and Descriptor, if they exist, and then click Next.
-
On the next page, on the Excluded items tab, select all files by clicking one of the files and then pressing Ctrl+A. At the bottom of the selection window, click Include item(s).
-
Click Finish.
-
Open the Pending Changes window from the Team Explorer pane or by clicking View > Other Windows > Pending Changes.
-
Review the changes, enter a check-in comment, and then click Check In.
Updating Third-party Models to Source Control
Upon receiving an updated package from your providers,
-
On your development machine, stop IIS, and the Microsoft Dynamics 365 Unified Operations: Batch Management Service.
-
Delete the third-party model folder from
PackagesLocalDirectory
. -
Install the package. (See step 1 above)
-
Start IIS and Microsoft Dynamics 365 Unified Operations: Batch Management Service.
-
Add all items to source control, including Excluded Items. (See steps 12 & 13 above)
-
Open the Pending Changes window from the Team Explorer pane or by clicking View > Other Windows > Pending Changes.
-
Review the changes, enter a check-in comment, and then click Check In.
For Other Development Machines
Getting Third-party Models from Source Control for the First Time
Once the third-party model is available on the source control, other developers would only need to get the latest version to install the model on their machines.
-
On your deveopment machine, open Visual Studio.
-
Open Source Control Explorer.
-
Update workspace mapping, go to
PackagesLocalDirectory
and create a new folder for the third-party model. -
Map the third-party model from source control to the new folder you have created.
From:
$/Project/Development/Metadata/ISVModel
To:
C:\AOSService\PackagesLocalDirectory\ISVModel
-
Select Yes on the Workspace Modified prompt to get the latest version.
-
Build and Sync.
Updating Third-party models from Source Control
Once the third-party model is updated on the source control,
-
On your development machine, stop IIS, and the Microsoft Dynamics 365 Unified Operations: Batch Management Service.
-
Delete third-party model folder from
PackagesLocalDirectory
. -
Open Visual Studio.
-
Open Source Control Explorer and click get latest version.
-
Build and Sync.
-
Start IIS and Microsoft Dynamics 365 Unified Operations: Batch Management Service.