Saving .asdatabase files as UTF8

Files conaining special characters where saved as ANSI when changing impersonation, resulting in weird characters in the output files. UTF8 is now enforced on these writes.

BuildSSASTask/task.json

@@ -17,7 +17,7 @@
   "version": {
     "Major": 1,
     "Minor": 0,
-    "Patch": 6
+    "Patch": 7
   },
   "demands": [ ],
   "minimumAgentVersion": "1.95.0",

DeploySSASTask/DeploySSASTask.ps1

@@ -225,7 +225,7 @@ try {
 						$datasource.ImpersonationInfo.Password = ""
 					}
 				}
-				[Microsoft.AnalysisServices.Tabular.JsonSerializer]::SerializeDatabase($db) | Set-Content $AsDBFilePath
+				[Microsoft.AnalysisServices.Tabular.JsonSerializer]::SerializeDatabase($db) | Set-Content $AsDBFilePath -Encoding UTF8
 			}
 			write-host "Impersonation information is changed on the Multidimensional Server"
 		}
@@ -259,7 +259,7 @@ try {
 						$datasource.Password = ""
 					}
 				}
-				[Microsoft.AnalysisServices.Tabular.JsonSerializer]::SerializeDatabase($db) | Set-Content $AsDBFilePath
+				[Microsoft.AnalysisServices.Tabular.JsonSerializer]::SerializeDatabase($db) | Set-Content $AsDBFilePath -Encoding UTF8
 			}
 			write-host "Impersonation information is changed on the Tabular server"
 

DeploySSASTask/task.json

@@ -17,7 +17,7 @@
     "version": {
         "Major": 1,
         "Minor": 0,
-        "Patch": 6
+        "Patch": 7
     },
     "demands": [],
     "minimumAgentVersion": "1.95.0",

README.md

@@ -28,7 +28,9 @@
 > NOTE: the deployment uses the Management Studio executable Microsoft.AnalysisServices.Deployment.exe Make sure that this is installed on your build agent!
 > Currently the Microsoft Hosted Agents DO NOT have Management Studio installed, so deployement from these hosts is unsupported. Setup a self hosted agent with SQL
 > Server Managenment Studio installed on it to use the deployment component
-> SECURITY WARNING: if you choose to use Windows username and password as impersonation mode the password you supply will be written in plaintext on disk at the deploy agent!
+> SECURITY WARNING: if you choose to use Windows username and password as impersonation mode the password you supply will be written in plaintext on disk at the deploy agent!\s\s
+> NOTE: When using Impersonation changing capabilities the outputfile that is used to deploy the model is written to disk using UTF8 encoding. If you're model uses some other encoding you might want to skip impersonation settings. (message me if this is a problem, I'll see if I can fix this)
+
 
 ## Contribute
 > * Contributions are welcome!
@@ -42,6 +44,7 @@
 > * Upated to use fit in Azure piplines category
 > * Added ImpersonationInformation option None, to skip impersonation settings altogether
 > * Custom Management Studio location (Microsoft.AnalysisServices.Deployment.exe) for deployment component
+> * Forced UTF8 encoding on writing .asdatabase json files to disk after changing impersonation information
 
 ## TODO:
 > * a Lot!

vss-extension.json

@@ -1,7 +1,7 @@
 {
     "manifestVersion": 1,
     "id": "VSTS-SSAS",
-    "version": "1.0.6",
+    "version": "1.0.7",
     "name": "SSAS Build & Deploy",
     "scopes": [ "vso.work", "vso.work_write" ],
     "description": "Extension with Continuous Integration support for SSAS",