Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Finance forum / Merge branches in VS m...
Finance forum

Merge branches in VS mapping setiup

(0) ShareShare
ReportReport
Posted on by 5

I need some guidance on merging branches

I looked at a couple different videos and read documents on source control but I am missing a link

I have two VMs running locally, one is my developer machine and is mapped to the DEV branch in VSTS, and I have a build definition for this branch. I did a simple model with a simple extension to change a label and check in and build works well. (The second VM functions as the build vm)

In VS I have dev/metadata mapped to c:/aosservice/packageslocaldirectory and projects is mapped to my local project folder.

In a roundabout way I got the Main and release branches created so that view hierarchy looks right. I want to merge from DEV into Main and then release.

My question has to do with mappings, earlier when I attempted to merge from the DEV branch to the Main branch I get this error

Trunk Main metadata is not mapped.

Which is of course because I didn't map it, but what do I map it to, or is there a better way to merge branches ?

Thanks,

Chris

  • ChrisB1975 Profile Picture
    5 on at
    RE: Merge branches in VS mapping setiup

    That works! thank you. I mapped Main/Metadata to c:\main branch and left Main/Projects unmapped.

  • Verified answer
    Sukrut Parab Profile Picture
    71,687 Moderator on at
    RE: Merge branches in VS mapping setiup

    You can create separate workspaces in your Dev machine for Main and Release branch , so in total you have three workspaces one is pointing to your packagesLocalDirectory folder(Dev workspace) and other two are pointing to Main and release folders. Once you do that In VS while merging code to Main branch select workspace you created/Pointing to main branch and then go to Medatadata folder and start merge. OR 

    You can map all three in a single workspace pointing to respective folders and start merging from Dev to Main and Main to Release . Advantage of doing this is each time you don't have to switch workspace while doing merge , however I always go by first way just to keep it simple.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

November Spotlight Star - Khushbu Rajvi

Congratulations to a top community star!

Forum Structure Changes Coming on 11/8!

In our never-ending quest to help the Dynamics 365 Community members get answers faster …

Dynamics 365 Community Platform update – Oct 28

Welcome to the next edition of the Community Platform Update. This is a status …

Leaderboard > Finance forum

Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans