Roll forward self-contained apps to latest patch version

build/Versions.props

@@ -19,7 +19,7 @@
 
   <!-- Toolset Dependencies -->
   <PropertyGroup>
-    <DotNetCliVersion>2.1.300-preview2-008290</DotNetCliVersion>
+    <DotNetCliVersion>2.1.300-preview3-008414</DotNetCliVersion>
     <RoslynToolsRepoToolsetVersion>1.0.0-beta-62615-02</RoslynToolsRepoToolsetVersion>
     <VSWhereVersion>2.2.7</VSWhereVersion>
   </PropertyGroup>

src/Tasks/Common/Resources/Strings.resx

@@ -336,4 +336,10 @@
   <data name="ErrorReadingAssetsFile" xml:space="preserve">
     <value>Error reading assets file: {0}</value>
   </data>
+  <data name="MismatchedPlatformPackageVersion" xml:space="preserve">
+    <value>The project was restored using {0} version {1}, but with current settings, version {2} would be used instead.  To resolve this issue, make sure the same settings are used for restore and for subsequent operations such as build or publish.  Typically this issue can occur if the RuntimeIdentifier property is set during build or publish but not during restore.</value>
+    <comment>{0} - Package Identifier for platform package
+{1} - Restored version of platform package
+{2} - Current version of platform package</comment>
+  </data>
 </root>

src/Tasks/Common/Resources/xlf/Strings.cs.xlf

@@ -367,6 +367,13 @@
         <target state="new">Error reading assets file: {0}</target>
         <note />
       </trans-unit>
+      <trans-unit id="MismatchedPlatformPackageVersion">
+        <source>The project was restored using {0} version {1}, but with current settings, version {2} would be used instead.  To resolve this issue, make sure the same settings are used for restore and for subsequent operations such as build or publish.  Typically this issue can occur if the RuntimeIdentifier property is set during build or publish but not during restore.</source>
+        <target state="new">The project was restored using {0} version {1}, but with current settings, version {2} would be used instead.  To resolve this issue, make sure the same settings are used for restore and for subsequent operations such as build or publish.  Typically this issue can occur if the RuntimeIdentifier property is set during build or publish but not during restore.</target>
+        <note>{0} - Package Identifier for platform package
+{1} - Restored version of platform package
+{2} - Current version of platform package</note>
+      </trans-unit>
     </body>
   </file>
 </xliff>

src/Tasks/Common/Resources/xlf/Strings.de.xlf

@@ -367,6 +367,13 @@
         <target state="new">Error reading assets file: {0}</target>
         <note />
       </trans-unit>
+      <trans-unit id="MismatchedPlatformPackageVersion">
+        <source>The project was restored using {0} version {1}, but with current settings, version {2} would be used instead.  To resolve this issue, make sure the same settings are used for restore and for subsequent operations such as build or publish.  Typically this issue can occur if the RuntimeIdentifier property is set during build or publish but not during restore.</source>
+        <target state="new">The project was restored using {0} version {1}, but with current settings, version {2} would be used instead.  To resolve this issue, make sure the same settings are used for restore and for subsequent operations such as build or publish.  Typically this issue can occur if the RuntimeIdentifier property is set during build or publish but not during restore.</target>
+        <note>{0} - Package Identifier for platform package
+{1} - Restored version of platform package
+{2} - Current version of platform package</note>
+      </trans-unit>
     </body>
   </file>
 </xliff>

src/Tasks/Common/Resources/xlf/Strings.es.xlf

@@ -367,6 +367,13 @@
         <target state="new">Error reading assets file: {0}</target>
         <note />
       </trans-unit>
+      <trans-unit id="MismatchedPlatformPackageVersion">
+        <source>The project was restored using {0} version {1}, but with current settings, version {2} would be used instead.  To resolve this issue, make sure the same settings are used for restore and for subsequent operations such as build or publish.  Typically this issue can occur if the RuntimeIdentifier property is set during build or publish but not during restore.</source>
+        <target state="new">The project was restored using {0} version {1}, but with current settings, version {2} would be used instead.  To resolve this issue, make sure the same settings are used for restore and for subsequent operations such as build or publish.  Typically this issue can occur if the RuntimeIdentifier property is set during build or publish but not during restore.</target>
+        <note>{0} - Package Identifier for platform package
+{1} - Restored version of platform package
+{2} - Current version of platform package</note>
+      </trans-unit>
     </body>
   </file>
 </xliff>

src/Tasks/Common/Resources/xlf/Strings.fr.xlf

@@ -367,6 +367,13 @@
         <target state="new">Error reading assets file: {0}</target>
         <note />
       </trans-unit>
+      <trans-unit id="MismatchedPlatformPackageVersion">
+        <source>The project was restored using {0} version {1}, but with current settings, version {2} would be used instead.  To resolve this issue, make sure the same settings are used for restore and for subsequent operations such as build or publish.  Typically this issue can occur if the RuntimeIdentifier property is set during build or publish but not during restore.</source>
+        <target state="new">The project was restored using {0} version {1}, but with current settings, version {2} would be used instead.  To resolve this issue, make sure the same settings are used for restore and for subsequent operations such as build or publish.  Typically this issue can occur if the RuntimeIdentifier property is set during build or publish but not during restore.</target>
+        <note>{0} - Package Identifier for platform package
+{1} - Restored version of platform package
+{2} - Current version of platform package</note>
+      </trans-unit>
     </body>
   </file>
 </xliff>

src/Tasks/Common/Resources/xlf/Strings.it.xlf

@@ -367,6 +367,13 @@
         <target state="new">Error reading assets file: {0}</target>
         <note />
       </trans-unit>
+      <trans-unit id="MismatchedPlatformPackageVersion">
+        <source>The project was restored using {0} version {1}, but with current settings, version {2} would be used instead.  To resolve this issue, make sure the same settings are used for restore and for subsequent operations such as build or publish.  Typically this issue can occur if the RuntimeIdentifier property is set during build or publish but not during restore.</source>
+        <target state="new">The project was restored using {0} version {1}, but with current settings, version {2} would be used instead.  To resolve this issue, make sure the same settings are used for restore and for subsequent operations such as build or publish.  Typically this issue can occur if the RuntimeIdentifier property is set during build or publish but not during restore.</target>
+        <note>{0} - Package Identifier for platform package
+{1} - Restored version of platform package
+{2} - Current version of platform package</note>
+      </trans-unit>
     </body>
   </file>
 </xliff>

src/Tasks/Common/Resources/xlf/Strings.ja.xlf

@@ -367,6 +367,13 @@
         <target state="new">Error reading assets file: {0}</target>
         <note />
       </trans-unit>
+      <trans-unit id="MismatchedPlatformPackageVersion">
+        <source>The project was restored using {0} version {1}, but with current settings, version {2} would be used instead.  To resolve this issue, make sure the same settings are used for restore and for subsequent operations such as build or publish.  Typically this issue can occur if the RuntimeIdentifier property is set during build or publish but not during restore.</source>
+        <target state="new">The project was restored using {0} version {1}, but with current settings, version {2} would be used instead.  To resolve this issue, make sure the same settings are used for restore and for subsequent operations such as build or publish.  Typically this issue can occur if the RuntimeIdentifier property is set during build or publish but not during restore.</target>
+        <note>{0} - Package Identifier for platform package
+{1} - Restored version of platform package
+{2} - Current version of platform package</note>
+      </trans-unit>
     </body>
   </file>
 </xliff>

src/Tasks/Common/Resources/xlf/Strings.ko.xlf

@@ -367,6 +367,13 @@
         <target state="new">Error reading assets file: {0}</target>
         <note />
       </trans-unit>
+      <trans-unit id="MismatchedPlatformPackageVersion">
+        <source>The project was restored using {0} version {1}, but with current settings, version {2} would be used instead.  To resolve this issue, make sure the same settings are used for restore and for subsequent operations such as build or publish.  Typically this issue can occur if the RuntimeIdentifier property is set during build or publish but not during restore.</source>
+        <target state="new">The project was restored using {0} version {1}, but with current settings, version {2} would be used instead.  To resolve this issue, make sure the same settings are used for restore and for subsequent operations such as build or publish.  Typically this issue can occur if the RuntimeIdentifier property is set during build or publish but not during restore.</target>
+        <note>{0} - Package Identifier for platform package
+{1} - Restored version of platform package
+{2} - Current version of platform package</note>
+      </trans-unit>
     </body>
   </file>
 </xliff>

src/Tasks/Common/Resources/xlf/Strings.pl.xlf

@@ -367,6 +367,13 @@
         <target state="new">Error reading assets file: {0}</target>
         <note />
       </trans-unit>
+      <trans-unit id="MismatchedPlatformPackageVersion">
+        <source>The project was restored using {0} version {1}, but with current settings, version {2} would be used instead.  To resolve this issue, make sure the same settings are used for restore and for subsequent operations such as build or publish.  Typically this issue can occur if the RuntimeIdentifier property is set during build or publish but not during restore.</source>
+        <target state="new">The project was restored using {0} version {1}, but with current settings, version {2} would be used instead.  To resolve this issue, make sure the same settings are used for restore and for subsequent operations such as build or publish.  Typically this issue can occur if the RuntimeIdentifier property is set during build or publish but not during restore.</target>
+        <note>{0} - Package Identifier for platform package
+{1} - Restored version of platform package
+{2} - Current version of platform package</note>
+      </trans-unit>
     </body>
   </file>
 </xliff>

src/Tasks/Common/Resources/xlf/Strings.pt-BR.xlf

@@ -367,6 +367,13 @@
         <target state="new">Error reading assets file: {0}</target>
         <note />
       </trans-unit>
+      <trans-unit id="MismatchedPlatformPackageVersion">
+        <source>The project was restored using {0} version {1}, but with current settings, version {2} would be used instead.  To resolve this issue, make sure the same settings are used for restore and for subsequent operations such as build or publish.  Typically this issue can occur if the RuntimeIdentifier property is set during build or publish but not during restore.</source>
+        <target state="new">The project was restored using {0} version {1}, but with current settings, version {2} would be used instead.  To resolve this issue, make sure the same settings are used for restore and for subsequent operations such as build or publish.  Typically this issue can occur if the RuntimeIdentifier property is set during build or publish but not during restore.</target>
+        <note>{0} - Package Identifier for platform package
+{1} - Restored version of platform package
+{2} - Current version of platform package</note>
+      </trans-unit>
     </body>
   </file>
 </xliff>

src/Tasks/Common/Resources/xlf/Strings.ru.xlf

@@ -367,6 +367,13 @@
         <target state="new">Error reading assets file: {0}</target>
         <note />
       </trans-unit>
+      <trans-unit id="MismatchedPlatformPackageVersion">
+        <source>The project was restored using {0} version {1}, but with current settings, version {2} would be used instead.  To resolve this issue, make sure the same settings are used for restore and for subsequent operations such as build or publish.  Typically this issue can occur if the RuntimeIdentifier property is set during build or publish but not during restore.</source>
+        <target state="new">The project was restored using {0} version {1}, but with current settings, version {2} would be used instead.  To resolve this issue, make sure the same settings are used for restore and for subsequent operations such as build or publish.  Typically this issue can occur if the RuntimeIdentifier property is set during build or publish but not during restore.</target>
+        <note>{0} - Package Identifier for platform package
+{1} - Restored version of platform package
+{2} - Current version of platform package</note>
+      </trans-unit>
     </body>
   </file>
 </xliff>

src/Tasks/Common/Resources/xlf/Strings.tr.xlf

@@ -367,6 +367,13 @@
         <target state="new">Error reading assets file: {0}</target>
         <note />
       </trans-unit>
+      <trans-unit id="MismatchedPlatformPackageVersion">
+        <source>The project was restored using {0} version {1}, but with current settings, version {2} would be used instead.  To resolve this issue, make sure the same settings are used for restore and for subsequent operations such as build or publish.  Typically this issue can occur if the RuntimeIdentifier property is set during build or publish but not during restore.</source>
+        <target state="new">The project was restored using {0} version {1}, but with current settings, version {2} would be used instead.  To resolve this issue, make sure the same settings are used for restore and for subsequent operations such as build or publish.  Typically this issue can occur if the RuntimeIdentifier property is set during build or publish but not during restore.</target>
+        <note>{0} - Package Identifier for platform package
+{1} - Restored version of platform package
+{2} - Current version of platform package</note>
+      </trans-unit>
     </body>
   </file>
 </xliff>

src/Tasks/Common/Resources/xlf/Strings.zh-Hans.xlf

@@ -367,6 +367,13 @@
         <target state="new">Error reading assets file: {0}</target>
         <note />
       </trans-unit>
+      <trans-unit id="MismatchedPlatformPackageVersion">
+        <source>The project was restored using {0} version {1}, but with current settings, version {2} would be used instead.  To resolve this issue, make sure the same settings are used for restore and for subsequent operations such as build or publish.  Typically this issue can occur if the RuntimeIdentifier property is set during build or publish but not during restore.</source>
+        <target state="new">The project was restored using {0} version {1}, but with current settings, version {2} would be used instead.  To resolve this issue, make sure the same settings are used for restore and for subsequent operations such as build or publish.  Typically this issue can occur if the RuntimeIdentifier property is set during build or publish but not during restore.</target>
+        <note>{0} - Package Identifier for platform package
+{1} - Restored version of platform package
+{2} - Current version of platform package</note>
+      </trans-unit>
     </body>
   </file>
 </xliff>

src/Tasks/Common/Resources/xlf/Strings.zh-Hant.xlf

@@ -367,6 +367,13 @@
         <target state="new">Error reading assets file: {0}</target>
         <note />
       </trans-unit>
+      <trans-unit id="MismatchedPlatformPackageVersion">
+        <source>The project was restored using {0} version {1}, but with current settings, version {2} would be used instead.  To resolve this issue, make sure the same settings are used for restore and for subsequent operations such as build or publish.  Typically this issue can occur if the RuntimeIdentifier property is set during build or publish but not during restore.</source>
+        <target state="new">The project was restored using {0} version {1}, but with current settings, version {2} would be used instead.  To resolve this issue, make sure the same settings are used for restore and for subsequent operations such as build or publish.  Typically this issue can occur if the RuntimeIdentifier property is set during build or publish but not during restore.</target>
+        <note>{0} - Package Identifier for platform package
+{1} - Restored version of platform package
+{2} - Current version of platform package</note>
+      </trans-unit>
     </body>
   </file>
 </xliff>