Skip to content

Commit

Permalink
Juno: check in to JUNO/hb_d40a9464-5533-4bb6-bb4d-a39a3f1c4f0e_202312…
Browse files Browse the repository at this point in the history 
…13095500812.
  • Loading branch information
@csigs
csigs committed Dec 13, 2023
1 parent 413d5ed commit cbe8888
Show file tree
Hide file tree
Showing 5 changed files with 25 additions and 10 deletions.
7 changes: 5 additions & 2 deletions ...ize/loc/de-DE/Tasks/FileTransformV1/Strings/resources.resjson/en-US/resources.resjson.lcl
View file
Original file line number Diff line number Diff line change
Expand Up @@ -56,10 +56,13 @@
</Item>
<Item ItemId=";loc.input.help.fileType" ItemType="0" PsrId="306" Leaf="true">
<Str Cat="Text">
<Val><![CDATA[Provide file format on which substitution has to be perfformed<br/>For XML, Variables defined in the build or release pipelines will be matched against the 'key' or 'name' entries in the appSettings, applicationSettings, and connectionStrings sections of any config file and parameters.xml. Variable Substitution is run after config transforms.<br/>To substitute JSON variables that are nested or hierarchical, specify them using JSONPath expressions. <br/> <br/> For example, to replace the value of ‘ConnectionString’ in the sample below, you need to define a variable as ‘Data.DefaultConnection.ConnectionString’ in the build or release pipeline (or release pipeline's environment). <br/> {<br/>&nbsp;&nbsp;"Data": {<br/>&nbsp;&nbsp;&nbsp;&nbsp;"DefaultConnection": {<br/>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"ConnectionString": "Server=(localdb)\SQLEXPRESS;Database=MyDB;Trusted_Connection=True"<br/>&nbsp;&nbsp;&nbsp;&nbsp;}<br/>&nbsp;&nbsp;}<br/> }<br/> Variable Substitution is run after configuration transforms. <br/><br/> Note: only custom variables defined in build/release pipelines are used in substitution. Default/system defined pipeline variables are excluded. <br/>Note: If same variables are defined in the release pipeline and in the stage, then the stage variables will supersede the release pipeline variables.]]></Val>
<Val><![CDATA[Provide file format on which substitution has to be performed<br/>For XML, Variables defined in the build or release pipelines will be matched against the 'key' or 'name' entries in the appSettings, applicationSettings, and connectionStrings sections of any config file and parameters.xml. Variable Substitution is run after config transforms.<br/>To substitute JSON variables that are nested or hierarchical, specify them using JSONPath expressions. <br/> <br/> For example, to replace the value of ‘ConnectionString’ in the sample below, you need to define a variable as ‘Data.DefaultConnection.ConnectionString’ in the build or release pipeline (or release pipeline's environment). <br/> {<br/>&nbsp;&nbsp;"Data": {<br/>&nbsp;&nbsp;&nbsp;&nbsp;"DefaultConnection": {<br/>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"ConnectionString": "Server=(localdb)\SQLEXPRESS;Database=MyDB;Trusted_Connection=True"<br/>&nbsp;&nbsp;&nbsp;&nbsp;}<br/>&nbsp;&nbsp;}<br/> }<br/> Variable Substitution is run after configuration transforms. <br/><br/> Note: only custom variables defined in build/release pipelines are used in substitution. Default/system defined pipeline variables are excluded. <br/>Note: If same variables are defined in the release pipeline and in the stage, then the stage variables will supersede the release pipeline variables.]]></Val>
<Tgt Cat="Text" Stat="Loc" Orig="New">
<Val><![CDATA[Geben Sie das Dateiformat an, für das die Ersetzung durchgeführt werden soll. <br/>Für XML werden in den Build- oder Releasepipelines definierte Variablen anhand der Einträge "key" oder "name" in den Abschnitten "appSettings", "applicationSettings" und "connectionStrings" einer beliebigen Konfigurationsdatei und "parameters.xml" abgeglichen. Die Variablenersetzung wird nach den Konfigurationstransformationen durchgeführt.<br/>Um JSON-Variablen zu ersetzen, die geschachtelt oder hierarchisch aufgebaut sind, geben Sie diese mithilfe von JSONPath-Ausdrücken an. <br/> <br/>Um beispielsweise den Wert von "ConnectionString" im Beispiel unten zu ersetzen, müssen Sie eine Variable als "Data.DefaultConnection.ConnectionString" in der Build- oder Releasepipeline (oder der Umgebung der Releasepipeline) definieren. <br/> {<br/>&nbsp;&nbsp;"Data": {<br/>&nbsp;&nbsp;&nbsp;&nbsp;"DefaultConnection": {<br/>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"ConnectionString": "Server=(localdb)\SQLEXPRESS;Database=MyDB;Trusted_Connection=True"<br/>&nbsp;&nbsp;&nbsp;&nbsp;}<br/>&nbsp;&nbsp;}<br/> }<br/> Die Variablenersetzung wird nach den Konfigurationstransformationen durchgeführt. <br/><br/> Hinweis: Bei der Ersetzung werden nur benutzerdefinierte Variablen verwendet, die in Build-/Releasepipelines definiert sind. In der Pipeline definierte Standard- oder Systemvariablen werden ausgeschlossen. <br/>Hinweis: Wenn dieselben Variablen für die Releasepipeline und die Stufe definiert werden, haben die Stufenvariablen Vorrang vor den Variablen der Releasepipeline.]]></Val>
<Val><![CDATA[Geben Sie das Dateiformat an, in dem der Ersatz ausgeführt werden muss<br/>Für XML werden Variablen, die in den Build- oder Releasepipelines definiert sind, mit den Einträgen "key" oder "name" in den Abschnitten "appSettings", "applicationSettings" und "connectionStrings" jeder Konfigurationsdatei und "parameters.xml" abgeglichen. Die Variablenersetzung wird nach Konfigurationstransformationen ausgeführt.<br/>Geben Sie JSONPath-Ausdrücke an, um geschachtelte oder hierarchische JSON-Variablen zu ersetzen. <br/> <br/> Um beispielsweise den Wert von ‘ConnectionString’ im folgenden Beispiel zu ersetzen, müssen Sie eine Variable in der Build- oder Releasepipeline (oder in der Umgebung der Releasepipeline) als ‘Data.DefaultConnection.ConnectionString’ definieren. <br/> {<br/>&nbsp;&nbsp;"Data": {<br/>&nbsp;&nbsp;&nbsp;&nbsp;"DefaultConnection": {<br/>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"ConnectionString": "Server=(localdb)\SQLEXPRESS;Database=MyDB;Trusted_Connection=True"<br/>&nbsp;&nbsp;&nbsp;&nbsp;}<br/>&nbsp;&nbsp;}<br/> }<br/> Variablenersetzung wird nach Konfigurationstransformationen ausgeführt. <br/><br/> Hinweis: Bei der Ersetzung werden nur benutzerdefinierte Variablen verwendet, die in Build-/Releasepipelines definiert sind. Standard-/systemdefinierte Pipelinevariablen werden ausgeschlossen. <br/>Hinweis: Wenn dieselben Variablen in der Releasepipeline und in der Phase definiert sind, ersetzen die Phasenvariablen die Releasepipelinevariablen.]]></Val>
</Tgt>
<Prev Cat="Text">
<Val><![CDATA[Provide file format on which substitution has to be perfformed<br/>For XML, Variables defined in the build or release pipelines will be matched against the 'key' or 'name' entries in the appSettings, applicationSettings, and connectionStrings sections of any config file and parameters.xml. Variable Substitution is run after config transforms.<br/>To substitute JSON variables that are nested or hierarchical, specify them using JSONPath expressions. <br/> <br/> For example, to replace the value of ‘ConnectionString’ in the sample below, you need to define a variable as ‘Data.DefaultConnection.ConnectionString’ in the build or release pipeline (or release pipeline's environment). <br/> {<br/>&nbsp;&nbsp;"Data": {<br/>&nbsp;&nbsp;&nbsp;&nbsp;"DefaultConnection": {<br/>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"ConnectionString": "Server=(localdb)\SQLEXPRESS;Database=MyDB;Trusted_Connection=True"<br/>&nbsp;&nbsp;&nbsp;&nbsp;}<br/>&nbsp;&nbsp;}<br/> }<br/> Variable Substitution is run after configuration transforms. <br/><br/> Note: only custom variables defined in build/release pipelines are used in substitution. Default/system defined pipeline variables are excluded. <br/>Note: If same variables are defined in the release pipeline and in the stage, then the stage variables will supersede the release pipeline variables.]]></Val>
</Prev>
</Str>
<Disp Icon="Str" />
</Item>
Expand Down
7 changes: 5 additions & 2 deletions ...ize/loc/es-ES/Tasks/FileTransformV1/Strings/resources.resjson/en-US/resources.resjson.lcl
View file
Original file line number Diff line number Diff line change
Expand Up @@ -56,10 +56,13 @@
</Item>
<Item ItemId=";loc.input.help.fileType" ItemType="0" PsrId="306" Leaf="true">
<Str Cat="Text">
<Val><![CDATA[Provide file format on which substitution has to be perfformed<br/>For XML, Variables defined in the build or release pipelines will be matched against the 'key' or 'name' entries in the appSettings, applicationSettings, and connectionStrings sections of any config file and parameters.xml. Variable Substitution is run after config transforms.<br/>To substitute JSON variables that are nested or hierarchical, specify them using JSONPath expressions. <br/> <br/> For example, to replace the value of ‘ConnectionString’ in the sample below, you need to define a variable as ‘Data.DefaultConnection.ConnectionString’ in the build or release pipeline (or release pipeline's environment). <br/> {<br/>&nbsp;&nbsp;"Data": {<br/>&nbsp;&nbsp;&nbsp;&nbsp;"DefaultConnection": {<br/>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"ConnectionString": "Server=(localdb)\SQLEXPRESS;Database=MyDB;Trusted_Connection=True"<br/>&nbsp;&nbsp;&nbsp;&nbsp;}<br/>&nbsp;&nbsp;}<br/> }<br/> Variable Substitution is run after configuration transforms. <br/><br/> Note: only custom variables defined in build/release pipelines are used in substitution. Default/system defined pipeline variables are excluded. <br/>Note: If same variables are defined in the release pipeline and in the stage, then the stage variables will supersede the release pipeline variables.]]></Val>
<Val><![CDATA[Provide file format on which substitution has to be performed<br/>For XML, Variables defined in the build or release pipelines will be matched against the 'key' or 'name' entries in the appSettings, applicationSettings, and connectionStrings sections of any config file and parameters.xml. Variable Substitution is run after config transforms.<br/>To substitute JSON variables that are nested or hierarchical, specify them using JSONPath expressions. <br/> <br/> For example, to replace the value of ‘ConnectionString’ in the sample below, you need to define a variable as ‘Data.DefaultConnection.ConnectionString’ in the build or release pipeline (or release pipeline's environment). <br/> {<br/>&nbsp;&nbsp;"Data": {<br/>&nbsp;&nbsp;&nbsp;&nbsp;"DefaultConnection": {<br/>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"ConnectionString": "Server=(localdb)\SQLEXPRESS;Database=MyDB;Trusted_Connection=True"<br/>&nbsp;&nbsp;&nbsp;&nbsp;}<br/>&nbsp;&nbsp;}<br/> }<br/> Variable Substitution is run after configuration transforms. <br/><br/> Note: only custom variables defined in build/release pipelines are used in substitution. Default/system defined pipeline variables are excluded. <br/>Note: If same variables are defined in the release pipeline and in the stage, then the stage variables will supersede the release pipeline variables.]]></Val>
<Tgt Cat="Text" Stat="Loc" Orig="New">
<Val><![CDATA[Proporcione el formato de archivo en el que debe realizarse la sustitución.<br/>Para XML, las variables que se definen en las canalizaciones de compilación o versión se compararán con las entradas "key" o "name" de las secciones appSettings, applicationSettings y connectionStrings de cualquier archivo de configuración y parameters.xml. La sustitución de variable tiene lugar después de las transformaciones de configuración. <br/> Para sustituir las variables JSON anidadas o jerárquicas, especifíquelas mediante expresiones JSONPath. <br/> <br/> Por ejemplo, para reemplazar el valor de “ConnectionString” en el ejemplo siguiente, debe definir una variable como “Data.DefaultConnection.ConnectionString” en la canalización de compilación o versión (o el entorno de la canalización de versión). <br/> {<br/>&nbsp;&nbsp;"Data": {<br/>&nbsp;&nbsp;&nbsp;&nbsp;"DefaultConnection": {<br/>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"ConnectionString": "Server=(localdb)\SQLEXPRESS;Database=MyDB;Trusted_Connection=True"<br/>&nbsp;&nbsp;&nbsp;&nbsp;}<br/>&nbsp;&nbsp;}<br/> }<br/> La sustitución de variables se ejecuta una vez que se transforma la configuración. <br/><br/> Nota: Solo las variables personalizadas definidas en las canalizaciones de compilación o versión se usan en la sustitución. Se excluyen las variables de canalización predeterminadas o definidas por el sistema. <br/>Nota: Si se definen las mismas variables en la canalización de versión y en la fase, las últimas sustituirán a las variables de la canalización de versión.]]></Val>
<Val><![CDATA[Proporcione el formato de archivo en el que debe realizarse la sustitución<br/>Para XML, las variables definidas en las canalizaciones de compilación o versión se compararán con las entradas "key" o "name" de las secciones appSettings, applicationSettings y connectionStrings de cualquier archivo de configuración y parameters.xml. La sustitución de variables se ejecuta después de las transformaciones de configuración.<br/>Para sustituir variables JSON anidadas o jerárquicas, especifíquelas mediante expresiones JSONPath. <br/> <br/> Por ejemplo, para reemplazar el valor de ‘ConnectionString’ en el ejemplo siguiente, debe definir una variable como ‘Data.DefaultConnection.ConnectionString’ en la canalización de compilación o versión (o en el entorno de la canalización de versión). <br/> {<br/>&nbsp; &nbsp;" Datos": {<br/>&nbsp; &nbsp; &nbsp; &nbsp;" DefaultConnection": {<br/>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;" ConnectionString": "Server=(localdb)\SQLEXPRESS; Base de datos=MyDB; Trusted_Connection=True"<br/>&nbsp; &nbsp; &nbsp; &nbsp;}<br/>&nbsp; &nbsp;}<br/> }<br/> La sustitución de variables se ejecuta después de las transformaciones de configuración. <br/><br/> Nota: en la sustitución solo se usan las variables personalizadas definidas en las canalizaciones de compilación o versión. Se excluyen las variables de canalización predeterminadas o definidas por el sistema. <br/>Nota: Si se definen las mismas variables en la canalización de versión y en la fase, las variables de fase sustituirán a las variables de canalización de versión.]]></Val>
</Tgt>
<Prev Cat="Text">
<Val><![CDATA[Provide file format on which substitution has to be perfformed<br/>For XML, Variables defined in the build or release pipelines will be matched against the 'key' or 'name' entries in the appSettings, applicationSettings, and connectionStrings sections of any config file and parameters.xml. Variable Substitution is run after config transforms.<br/>To substitute JSON variables that are nested or hierarchical, specify them using JSONPath expressions. <br/> <br/> For example, to replace the value of ‘ConnectionString’ in the sample below, you need to define a variable as ‘Data.DefaultConnection.ConnectionString’ in the build or release pipeline (or release pipeline's environment). <br/> {<br/>&nbsp;&nbsp;"Data": {<br/>&nbsp;&nbsp;&nbsp;&nbsp;"DefaultConnection": {<br/>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"ConnectionString": "Server=(localdb)\SQLEXPRESS;Database=MyDB;Trusted_Connection=True"<br/>&nbsp;&nbsp;&nbsp;&nbsp;}<br/>&nbsp;&nbsp;}<br/> }<br/> Variable Substitution is run after configuration transforms. <br/><br/> Note: only custom variables defined in build/release pipelines are used in substitution. Default/system defined pipeline variables are excluded. <br/>Note: If same variables are defined in the release pipeline and in the stage, then the stage variables will supersede the release pipeline variables.]]></Val>
</Prev>
</Str>
<Disp Icon="Str" />
</Item>
Expand Down
Loading

0 comments on commit cbe8888

Please sign in to comment.