MsDyn365BC.Code.History Tips & Tricks

Описание: GitHub code search in the MSDyn365BC.Code.History repository is broken — it returns no results, which makes the repo feel unusable at first. The fix is to open the repo in the browser-based VS Code by pressing `.` on your keyboard or replacing `github.com` with `github.dev` in the URL. From there, full-text search, file search with Ctrl+P, and the Timeline view for file-level commit history all work exactly as you'd expect, as long as you switch to a version branch like `w1-25` first (the master branch only contains scripts).

For more advanced comparisons across BC versions, a local clone with `--single-branch` is the right approach. You can clone just one branch, then add more later using `git remote set-branches` or by editing `.git/config` directly with wildcard fetch rules. With the GitLens extension installed, you can compare entire BC version ranges across all changed files at once — useful when you need to know everything Microsoft changed between two minor releases. The MSDyn365BC.Sandbox.Code.History repository extends this further with `vNext` branches that update daily from Insider artifacts, letting you see what is changing in the next release before it ships.

This stream walks through the full workflow: fixing GitHub search, navigating files in the browser editor, cloning efficiently, using GitLens for cross-version diffs, fetching multiple branches with wildcard config, and using the Sandbox repository to track upcoming Business Central changes.

Streaming all kinds of coding for Microsoft Dynamics 365 Business Central.
Join me to just hang out or tell me what I am doing wrong ;)

Join me live and let's build this together.

📝 Blog post: https://stefanmaron.com/posts/msdyn36...

https://github.com/StefanMaron/MSDyn3...
https://github.com/StefanMaron/MSDyn3...

====== Content of this Video ======
0:00 - Introduction and overview
1:32 - Addressing broken features in code history repository
2:23 - Using GitHub's web-based VS Code
3:57 - Searching and navigating in VS Code
6:26 - Using VS Code command palette and file search
8:19 - Comparing file versions using timeline
10:40 - Comparing multiple versions of a file
11:49 - Cloning a single branch from the repository
14:52 - Using Git Lens extension for commit history
17:34 - Comparing branches across versions
19:43 - Adding and fetching additional branches
23:37 - Modifying Git config to fetch multiple branches
25:50 - Explaining repository structure and version history
27:25 - Sandbox history repository and branch organization
30:31 - Comparing current version with next version (v-ex)
34:22 - Comparing files across branches in VS Code
36:33 - Updating repositories and workspaces
37:14 - Conclusion and invitation for feedback

About Me:
https://stefanmaron.com/

Music by:
   / @streambeatsbyharrisheller  
https://open.spotify.com/artist/6GTRL...