[Deployment] Use MSBuildProject's Namespace when saving project data

Adding deployment data into the project file now uses the
MSBuildProject's Namespace instead of the Schema constant. This
prevents an xmlns attribute being added when the project's namespace
is not the standard MSBuild project namespace such as with Sdk style
projects.

1 files changed, 1 insertions, 1 deletions

diff --git a/main/src/addins/Deployment/MonoDevelop.Deployment.Linux/MonoDevelop.Deployment.Linux/LinuxDeployData.cs b/main/src/addins/Deployment/MonoDevelop.Deployment.Linux/MonoDevelop.Deployment.Linux/LinuxDeployData.cs
index aed6187f73..e3ce030a58 100644
--- a/main/src/addins/Deployment/MonoDevelop.Deployment.Linux/MonoDevelop.Deployment.Linux/LinuxDeployData.cs
+++ b/main/src/addins/Deployment/MonoDevelop.Deployment.Linux/MonoDevelop.Deployment.Linux/LinuxDeployData.cs
@@ -66,7 +66,7 @@ namespace MonoDevelop.Deployment.Linux
 			var data = ser.Serialize (this);
 
 			XmlDocument doc = new XmlDocument ();
-			var writer = new XmlConfigurationWriter { Namespace = MSBuildProject.Schema };
+			var writer = new XmlConfigurationWriter { Namespace = entry.MSBuildProject.Namespace };
 			var elem = writer.Write (doc, data);
 
 			entry.MSBuildProject.SetMonoDevelopProjectExtension ("Deployment.LinuxDeployData", elem);