diff --git a/Documentation/developer-guide.md b/Documentation/developer-guide.md
index 44d1e35c2a3..d640df002e8 100644
--- a/Documentation/developer-guide.md
+++ b/Documentation/developer-guide.md
@@ -47,6 +47,24 @@ If there were any failures, you can cd into $(RepoRoot)\artifacts\test\$(Configu
*NOTE: This requires being run from an admin window at the moment. Removing this restriction is tracked by https://github.com/dotnet/wpf/issues/816.*
+### Debugging locally built WPF assemblies with WPF Application
+This section is intended to simplify the steps needed to be able to debug the locally built WPF Assemblies, with any sample app.
+Configure the project to build x86 or x64, as per the platform architecture you have selected while performing the build for WPF assemblies.
+Go to the csproj file and append this line at the bottom of it. ``. The resultant csproj will look like this:
+```xml
+
+ WinExe
+ net6.0-windows
+ true
+
+
+
+ C:\wpf
+
+
+```
+
+
### Testing Locally built WPF assemblies (excluding PresentationBuildTasks)
This section of guide is intended to discuss the different approaches for ad-hoc testing of WPF assemblies,
and not automated testing. For automated testing, see the [Running DRTs locally](#Running-DRTs-locally) section above. There are a few different ways this can be done, and for the most part, it depends on what you are trying to accomplish. This section tries to lay out which scenarios require which workflow.
diff --git a/eng/wpf-debug.targets b/eng/wpf-debug.targets
new file mode 100644
index 00000000000..39c9d459217
--- /dev/null
+++ b/eng/wpf-debug.targets
@@ -0,0 +1,23 @@
+
+
+
+
+
+ Debug
+ win-$(PlatformTarget)
+ $([System.IO.Path]::GetFullPath('$(MSBuildThisFileDirectory)\..\'))\artifacts\packaging\$(WpfConfig)\Microsoft.DotNet.Wpf.GitHub.$(WpfConfig)
+
+
+
+
+
+
+