Plaza 365
Plaza 365

No results found for your search

RegisterLog in

5

F&O development with multiple version control workspaces

Visit article

#applicationdevelopment

#branchswitching

#custompackages

#versioncontrol

#workspacemapping

Dynamics 365 Finance

Category

Aug 30, 2023

Published date

Text

Article Type

AI Summary

  • The usual setup for version control in Dynamics 365 Finance and Operations (F&O) involves using Team Foundation Version Control and configuring workspace mapping.
  • Switching to a different branch or version in F&O is time-consuming and requires several steps, including suspending pending changes, deleting workspace mapping, and compiling custom packages.
  • The author suggests using multiple workspaces instead of the traditional approach to version control. Each workspace contains its own version of the application, a list of pending changes, and compiled binaries.
  • Instead of storing custom packages in the PackagesLocalDirectory, the author creates a separate folder for each workspace and only includes Microsoft code in the PackagesLocalDirectory.
  • The author uses scripts to automate the process of configuring workspace paths and creating symbolic links for package folders.
  • Actions such as downloading latest code, merging code, and building the application can be performed without switching workspaces.
  • When applying an application update from Microsoft, it is important to tell F&O to use the PackagesLocalDirectory to ensure all workspaces can access the new package.
  • Multiple workspaces can be created for a single branch, allowing for separate workspaces for code reviews and development.

Registered users can view the full text for FREE!

Sign In Now!