Thinking In AX: How to Use .gitignore in D365 F&O (Complete Guide for Developers)

If your repository is cluttered with unnecessary files, slow check-ins, and confusing changes, your .gitignore likely needs attention—especially in enterprise ERP development. In Dynamics 365 Finance and Operations, managing source control properly isn’t optional; it directly impacts build reliability, collaboration, and deployment efficiency.

This guide walks you through how to use .gitignore effectively in D365 F&O projects—and includes a ready-to-use sample you can download and apply immediately.

🚀 Why `.gitignore` matters in D365 F&O

Development in D365 F&O using Visual Studio produces a large number of temporary, generated, and environment-specific files.

If these files are committed into Git:

Your repository size grows unnecessarily
Developers face constant merge conflicts
Builds become inconsistent across environments

.gitignore ensures only relevant, reproducible source files are tracked.

📂 What should NOT go into source control

1) Build outputs & binaries

These are generated during compilation and should never be committed:


**/bin/
**/obj/
**/*.dll
**/*.pdb

2) Visual Studio user-specific files

These vary by developer machine:


*.suo
*.user
*.userosscache
*.sln.docstates
.vs/

3) D365 F&O generated artifacts

System-generated metadata and temp files:


**/xppMetadata/Temp/
**/xppMetadata/Generated/
**/xppSource/Temp/

4) Logs, cache, and backups

No value for version control:


*.log
*.cache
*.bak
*.tmp

5) Packages and deployables

These are large, environment-specific, and rebuildable:


**/PackagesLocalDirectory/
**/*.zip

✅ What SHOULD be tracked

Only commit what’s necessary to rebuild the solution:

X++ source code (.xpp)
Metadata (models, elements)
Solution and project files (.sln, .csproj)
Required configuration files

👉 If a new developer can clone and build successfully, your repo is clean.

📥 Sample `.gitignore` File (Download & Use)

Here’s a ready-to-use .gitignore template for Dynamics 365 Finance and Operations projects:


## Ignore Visual Studio temporary files, build results, and
## files generated by popular Visual Studio add-ons.
##
## Get latest from https://github.com/github/gitignore/blob/main/VisualStudio.gitignore

# User-specific files
*.rsuser
*.suo
*.user
*.userosscache
*.sln.docstates

# User-specific files (MonoDevelop/Xamarin Studio)
*.userprefs

# Mono auto generated files
mono_crash.*

# Build results
[Dd]ebug/
[Dd]ebugPublic/
[Rr]elease/
[Rr]eleases/
x64/
x86/
[Ww][Ii][Nn]32/
[Aa][Rr][Mm]/
[Aa][Rr][Mm]64/
bld/
[Bb]in/
[Oo]bj/
[Ll]og/
[Ll]ogs/

# Visual Studio 2015/2017 cache/options directory
.vs/
# Uncomment if you have tasks that create the project's static files in wwwroot
#wwwroot/

# Visual Studio 2017 auto generated files
Generated\ Files/

# MSTest test Results
[Tt]est[Rr]esult*/
[Bb]uild[Ll]og.*

# NUnit
*.VisualState.xml
TestResult.xml
nunit-*.xml

# Build Results of an ATL Project
[Dd]ebugPS/
[Rr]eleasePS/
dlldata.c

# Benchmark Results
BenchmarkDotNet.Artifacts/

# .NET Core
project.lock.json
project.fragment.lock.json
artifacts/

# ASP.NET Scaffolding
ScaffoldingReadMe.txt

# StyleCop
StyleCopReport.xml

# Files built by Visual Studio
*_i.c
*_p.c
*_h.h
*.ilk
*.meta
*.obj
*.iobj
*.pch
*.pdb
*.ipdb
*.pgc
*.pgd
*.rsp
# but not Directory.Build.rsp, as it configures directory-level build defaults
!Directory.Build.rsp
*.sbr
*.tlb
*.tli
*.tlh
*.tmp
*.tmp_proj
*_wpftmp.csproj
*.log
*.tlog
*.vspscc
*.vssscc
.builds
*.pidb
*.svclog
*.scc

# Chutzpah Test files
_Chutzpah*

# Visual C++ cache files
ipch/
*.aps
*.ncb
*.opendb
*.opensdf
*.sdf
*.cachefile
*.VC.db
*.VC.VC.opendb

# Visual Studio profiler
*.psess
*.vsp
*.vspx
*.sap

# Visual Studio Trace Files
*.e2e

# TFS 2012 Local Workspace
$tf/

# Guidance Automation Toolkit
*.gpState

# ReSharper is a .NET coding add-in
_ReSharper*/
*.[Rr]e[Ss]harper
*.DotSettings.user

# TeamCity is a build add-in
_TeamCity*

# DotCover is a Code Coverage Tool
*.dotCover

# AxoCover is a Code Coverage Tool
.axoCover/*
!.axoCover/settings.json

# Coverlet is a free, cross platform Code Coverage Tool
coverage*.json
coverage*.xml
coverage*.info

# Visual Studio code coverage results
*.coverage
*.coveragexml

# NCrunch
_NCrunch_*
.*crunch*.local.xml
nCrunchTemp_*

# MightyMoose
*.mm.*
AutoTest.Net/

# Web workbench (sass)
.sass-cache/

# Installshield output folder
[Ee]xpress/

# DocProject is a documentation generator add-in
DocProject/buildhelp/
DocProject/Help/*.HxT
DocProject/Help/*.HxC
DocProject/Help/*.hhc
DocProject/Help/*.hhk
DocProject/Help/*.hhp
DocProject/Help/Html2
DocProject/Help/html

# Click-Once directory
publish/

# Publish Web Output
*.[Pp]ublish.xml
*.azurePubxml
# Note: Comment the next line if you want to checkin your web deploy settings,
# but database connection strings (with potential passwords) will be unencrypted
*.pubxml
*.publishproj

# Microsoft Azure Web App publish settings. Comment the next line if you want to
# checkin your Azure Web App publish settings, but sensitive information contained
# in these scripts will be unencrypted
PublishScripts/

# NuGet Packages
*.nupkg
# NuGet Symbol Packages
*.snupkg
# The packages folder can be ignored because of Package Restore
**/[Pp]ackages/*
# except build/, which is used as an MSBuild target.
!**/[Pp]ackages/build/
# Uncomment if necessary however generally it will be regenerated when needed
#!**/[Pp]ackages/repositories.config
# NuGet v3's project.json files produces more ignorable files
*.nuget.props
*.nuget.targets

# Microsoft Azure Build Output
csx/
*.build.csdef

# Microsoft Azure Emulator
ecf/
rcf/

# Windows Store app package directories and files
AppPackages/
BundleArtifacts/
Package.StoreAssociation.xml
_pkginfo.txt
*.appx
*.appxbundle
*.appxupload

# Visual Studio cache files
# files ending in .cache can be ignored
*.[Cc]ache
# but keep track of directories ending in .cache
!?*.[Cc]ache/

# Others
ClientBin/
~$*
*~
*.dbmdl
*.dbproj.schemaview
*.jfm
*.pfx
*.publishsettings
orleans.codegen.cs

# Including strong name files can present a security risk
# (https://github.com/github/gitignore/pull/2483#issue-259490424)
#*.snk

# Since there are multiple workflows, uncomment next line to ignore bower_components
# (https://github.com/github/gitignore/pull/1529#issuecomment-104372622)
#bower_components/

# RIA/Silverlight projects
Generated_Code/

# Backup & report files from converting an old project file
# to a newer Visual Studio version. Backup files are not needed,
# because we have git ;-)
_UpgradeReport_Files/
Backup*/
UpgradeLog*.XML
UpgradeLog*.htm
ServiceFabricBackup/
*.rptproj.bak

# SQL Server files
*.mdf
*.ldf
*.ndf

# Business Intelligence projects
*.rdl.data
*.bim.layout
*.bim_*.settings
*.rptproj.rsuser
*- [Bb]ackup.rdl
*- [Bb]ackup ([0-9]).rdl
*- [Bb]ackup ([0-9][0-9]).rdl

# Microsoft Fakes
FakesAssemblies/

# GhostDoc plugin setting file
*.GhostDoc.xml

# Node.js Tools for Visual Studio
.ntvs_analysis.dat
node_modules/

# Visual Studio 6 build log
*.plg

# Visual Studio 6 workspace options file
*.opt

# Visual Studio 6 auto-generated workspace file (contains which files were open etc.)
*.vbw

# Visual Studio 6 auto-generated project file (contains which files were open etc.)
*.vbp

# Visual Studio 6 workspace and project file (working project files containing files to include in project)
*.dsw
*.dsp

# Visual Studio 6 technical files
*.ncb
*.aps

# Visual Studio LightSwitch build output
**/*.HTMLClient/GeneratedArtifacts
**/*.DesktopClient/GeneratedArtifacts
**/*.DesktopClient/ModelManifest.xml
**/*.Server/GeneratedArtifacts
**/*.Server/ModelManifest.xml
_Pvt_Extensions

# Paket dependency manager
.paket/paket.exe
paket-files/

# FAKE - F# Make
.fake/

# CodeRush personal settings
.cr/personal

# Python Tools for Visual Studio (PTVS)
__pycache__/
*.pyc

# Cake - Uncomment if you are using it
# tools/**
# !tools/packages.config

# Tabs Studio
*.tss

# Telerik's JustMock configuration file
*.jmconfig

# BizTalk build output
*.btp.cs
*.btm.cs
*.odx.cs
*.xsd.cs

# OpenCover UI analysis results
OpenCover/

# Azure Stream Analytics local run output
ASALocalRun/

# MSBuild Binary and Structured Log
*.binlog

# NVidia Nsight GPU debugger configuration file
*.nvuser

# MFractors (Xamarin productivity tool) working folder
.mfractor/

# Local History for Visual Studio
.localhistory/

# Visual Studio History (VSHistory) files
.vshistory/

# BeatPulse healthcheck temp database
healthchecksdb

# Backup folder for Package Reference Convert tool in Visual Studio 2017
MigrationBackup/

# Ionide (cross platform F# VS Code tools) working folder
.ionide/

# Fody - auto-generated XML schema
FodyWeavers.xsd

# VS Code files for those working on multiple tools
.vscode/*
!.vscode/settings.json
!.vscode/tasks.json
!.vscode/launch.json
!.vscode/extensions.json
*.code-workspace

# Local History for Visual Studio Code
.history/

# Windows Installer files from build outputs
*.cab
*.msi
*.msix
*.msm
*.msp

# JetBrains Rider
*.sln.iml
.idea/

# F&O specific
/src/Metadata/*/BuildModelResult.*
/src/Metadata/*/BuildProjectResult.*
/src/Metadata/*/CompileLabels.*
/src/Metadata/*/Resources/
/src/Metadata/*/Reports/
/src/Metadata/*/WebContent/
/src/Metadata/*/XppMetadata/
/src/Metadata/**/bin/
!/src/Metadata/**/bin/*.dll
# Also keep any binary package that may be in source control for binary 
#package "Binary Company"
# this will keep all files and folders with files in folder "Binary Company"
#bin/
# keep VS Projects
#!/Projects
# Also include the following files in root of PackagesLocalDirectory
#!.gitignore
# YAML Pipeline for DevOps
#!.azuredevops/azure-pipelines.yml
# settings for NuGet for Pipeline
#!nuget.config
# packages references for NuGet for use in Pipeline
#!packages.config

.env

🧩 How to Use

Create a file named .gitignore in the root of your repository
Paste the above content
Commit it to your repo

If unwanted files are already tracked, clean them with:


git rm -r --cached .
git add .
git commit -m "Apply .gitignore cleanup"

⚠️ Common mistakes to avoid

❌ Committing `PackagesLocalDirectory`

This is one of the biggest mistakes—massive size, environment-specific, and unnecessary.

❌ Ignoring too much

If your teammates can’t build after cloning, you’ve gone too far.

❌ Updating `.gitignore` too late

Once files are tracked, they stay tracked unless explicitly removed.

📊 Real-world impact

A properly configured .gitignore leads to:

Faster builds and deployments
Cleaner pull requests
Fewer merge conflicts
Easier onboarding for new developers

In large D365 F&O implementations, this directly reduces operational friction and project risk.

💡 Pro Tip

You can extend your setup using templates from GitHub:

👉 https://github.com/github/gitignore

Start with VisualStudio.gitignore and layer in D365-specific rules.

🏁 Final thoughts

.gitignore isn’t just a configuration file—it’s a foundation for maintainable development. In D365 F&O projects, where generated artifacts and large packages are common, setting this up correctly from day one saves significant time and effort later.

If your repo feels bloated or chaotic, this is one of the highest-impact fixes you can make.

Thinking In AX

Thursday, April 30, 2026

How to Use .gitignore in D365 F&O (Complete Guide for Developers)

🚀 Why `.gitignore` matters in D365 F&O

📂 What should NOT go into source control

1) Build outputs & binaries

2) Visual Studio user-specific files

3) D365 F&O generated artifacts

4) Logs, cache, and backups

5) Packages and deployables

✅ What SHOULD be tracked

📥 Sample `.gitignore` File (Download & Use)

🧩 How to Use

⚠️ Common mistakes to avoid

❌ Committing `PackagesLocalDirectory`

❌ Ignoring too much

❌ Updating `.gitignore` too late

📊 Real-world impact

💡 Pro Tip

🏁 Final thoughts

No comments:

Post a Comment

Thursday, April 30, 2026

How to Use .gitignore in D365 F&O (Complete Guide for Developers)

🚀 Why .gitignore matters in D365 F&O

📂 What should NOT go into source control

1) Build outputs & binaries

2) Visual Studio user-specific files

3) D365 F&O generated artifacts

4) Logs, cache, and backups

5) Packages and deployables

✅ What SHOULD be tracked

📥 Sample .gitignore File (Download & Use)

🧩 How to Use

⚠️ Common mistakes to avoid

❌ Committing PackagesLocalDirectory

❌ Ignoring too much

❌ Updating .gitignore too late

📊 Real-world impact

💡 Pro Tip

🏁 Final thoughts

No comments:

Post a Comment

🚀 Why `.gitignore` matters in D365 F&O

📥 Sample `.gitignore` File (Download & Use)

❌ Committing `PackagesLocalDirectory`

❌ Updating `.gitignore` too late