From 7bdfa43347926dd76847b60814b17c2c3fafaa00 Mon Sep 17 00:00:00 2001
From: Tomas Prokop <tomas.prokop@networg.com>
Date: Wed, 29 Jul 2026 14:21:13 +0200
Subject: [PATCH] chore: drop redundant OutputPath from PCF template

TALXIS.DevKit.Build.Dataverse.Pcf.props already defaults OutputPath to
this exact value ($(MSBuildProjectDirectory)\out\controls), so
scaffolded PCF projects don't need to declare it themselves. Consumers
building PCF controls aren't building .NET code at all (webpack/
pcf-scripts owns the actual build), so the template shouldn't carry
MSBuild property clutter that has no function.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---
 src/Dataverse/templates/pp-pcf/examplesourcename.csproj | 1 -
 1 file changed, 1 deletion(-)

diff --git a/src/Dataverse/templates/pp-pcf/examplesourcename.csproj b/src/Dataverse/templates/pp-pcf/examplesourcename.csproj
index 1130b4b..42e2c2b 100644
--- a/src/Dataverse/templates/pp-pcf/examplesourcename.csproj
+++ b/src/Dataverse/templates/pp-pcf/examplesourcename.csproj
@@ -3,7 +3,6 @@
   <PropertyGroup>
     <Name>examplesourcename</Name>
     <ProjectGuid>56daf92d-4098-4de0-9ba5-0fa2f9e3d36b</ProjectGuid>
-    <OutputPath>$(MSBuildThisFileDirectory)out\controls</OutputPath>
     <ProjectType>Pcf</ProjectType>
   </PropertyGroup>
 </Project>