diff --git a/src/Build/Resources/xlf/Strings.en.xlf b/src/Build/Resources/xlf/Strings.en.xlf deleted file mode 100644 index 2e20e50527d..00000000000 --- a/src/Build/Resources/xlf/Strings.en.xlf +++ /dev/null @@ -1,2455 +0,0 @@ - - - - - - MSB4001: The "{0}" task has more than one parameter called "{1}". - MSB4001: The "{0}" task has more than one parameter called "{1}". - {StrBegin="MSB4001: "}UE: This message is shown when a task has more than one .NET property with the same name -- it's unclear which of - those properties the task wants to use as a parameter in project files. - - - MSB4249: Unable to build website project "{0}". The ASP.NET compiler is only available on the .NET Framework version of MSBuild. - MSB4249: Unable to build website project "{0}". The ASP.NET compiler is only available on the .NET Framework version of MSBuild. - {StrBegin="MSB4249: "} - - - MSB4002: There was a failure retrieving the attributes for parameters in the "{0}" task. {1} - MSB4002: There was a failure retrieving the attributes for parameters in the "{0}" task. {1} - {StrBegin="MSB4002: "}UE: This message is shown when the .NET attributes that a task's .NET properties are decorated with, cannot be - retrieved -- this is typically because the .NET classes that define the .NET attributes cannot be loaded because the assembly - they are defined in cannot be found, or the classes themselves cannot be found. - - - MSB4003: "{0}" is a reserved attribute of the <{1}> element, and must be spelled with the correct casing. This attribute cannot be used as a parameter to the "{2}" task. - MSB4003: "{0}" is a reserved attribute of the <{1}> element, and must be spelled with the correct casing. This attribute cannot be used as a parameter to the "{2}" task. - {StrBegin="MSB4003: "}UE: Tasks are not allowed to use incorrect case for reserved attributes on the task nodes e.g. "continueonerror" - instead of the "ContinueOnError". - - - The operation cannot be completed because a build is already in progress. - The operation cannot be completed because a build is already in progress. - - - - MSB4252: Project "{0}" with global properties - ({1}) - is building project "{2}" with global properties - ({3}) - with the ({4}) target(s) but the build result for the built project is not in the engine cache. In isolated builds this could mean one of the following: - - the reference was called with a target which is not specified in the ProjectReferenceTargets item in project "{0}" - - the reference was called with global properties that do not match the static graph inferred nodes - - the reference was not explicitly specified as a ProjectReference item in project "{0}" - - MSB4252: Project "{0}" with global properties - ({1}) - is building project "{2}" with global properties - ({3}) - with the ({4}) target(s) but the build result for the built project is not in the engine cache. In isolated builds this could mean one of the following: - - the reference was called with a target which is not specified in the ProjectReferenceTargets item in project "{0}" - - the reference was called with global properties that do not match the static graph inferred nodes - - the reference was not explicitly specified as a ProjectReference item in project "{0}" - - - {StrBegin="MSB4252:"} - LOCALIZATION: Do not localize the following words: ProjectReference, ProjectReferenceTargets - - - - MSB4248: Cannot expand metadata in expression "{0}". {1} - MSB4248: Cannot expand metadata in expression "{0}". {1} - {StrBegin="MSB4248: "}UE: This message is shown when metadata cannot be expanded in an expression for some reason e.g. trying to apply - %(RootDir) to an item-spec that's not a valid path would result in this error. - LOCALIZATION: "{1}" is a localized message explaining the problem. - - - MSB4271: Environment variable MSBuildDisableFeaturesFromVersion is set to an invalid format. Enabling all change wave versions. Entered value: {0}. Current Change Waves: {1}. - MSB4271: Environment variable MSBuildDisableFeaturesFromVersion is set to an invalid format. Enabling all change wave versions. Entered value: {0}. Current Change Waves: {1}. - {StrBegin="MSB4271: "}UE: Value should be of the format: xx.yy - - - MSB4272: Environment variable MSBuildDisableFeaturesFromVersion is set to a version that is out of rotation. Defaulting to Change Wave version: {0}. Entered value: {1}. Current Change Waves: {2}. - MSB4272: Environment variable MSBuildDisableFeaturesFromVersion is set to a version that is out of rotation. Defaulting to Change Wave version: {0}. Entered value: {1}. Current Change Waves: {2}. - {StrBegin="MSB4272: "} - - - MSB4006: There is a circular dependency in the target dependency graph involving target "{0}". - MSB4006: There is a circular dependency in the target dependency graph involving target "{0}". - {StrBegin="MSB4006: "}UE: This message is shown when the build engine detects a target referenced in a circular manner -- a project cannot - request a target to build itself (perhaps via a chain of other targets). - - - MSB4251: There is a circular dependency involving the following projects: {0} - MSB4251: There is a circular dependency involving the following projects: {0} - - {StrBegin="MSB4251:"} This message is shown when a graph build detects a target referenced in a circular manner -- a project cannot - request a target to build itself (perhaps via a chain of other targets) - - - - MSB4006: There is a circular dependency in the target dependency graph involving target "{0}". Since "{1}" has "{2}" dependence on "{3}", the circular is "{4}". - MSB4006: There is a circular dependency in the target dependency graph involving target "{0}". Since "{1}" has "{2}" dependence on "{3}", the circular is "{4}". - {StrBegin="MSB4006: "}UE: This message is shown when the build engine detects a target referenced in a circular manner -- a project cannot - request a target to build itself (perhaps via a chain of other targets). - - - MSB4257: The specified output result cache file is empty. - MSB4257: The specified output result cache file is empty. - - - - Read environment variable "{0}" - Read environment variable "{0}" - - - - MSB4256: Reading input result cache files from path "{0}" encountered an error: {1} - MSB4256: Reading input result cache files from path "{0}" encountered an error: {1} - - - - MSB4258: Writing output result cache file in path "{0}" encountered an error: {1} - MSB4258: Writing output result cache file in path "{0}" encountered an error: {1} - - - - MSB4259: Unexpected space at position "{1}" of condition "{0}". Did you forget to remove a space? - MSB4259: Unexpected space at position "{1}" of condition "{0}". Did you forget to remove a space? - {StrBegin="MSB4259: "} - - - MSB4255: The following input result cache files do not exist: "{0}" - MSB4255: The following input result cache files do not exist: "{0}" - - - - Version string was not in a correct format. - Version string was not in a correct format. - - - - EvaluationContext objects created with SharingPolicy.Isolated do not support being passed an MSBuildFileSystemBase file system. - EvaluationContext objects created with SharingPolicy.Isolated do not support being passed an MSBuildFileSystemBase file system. - - - - Killing process with pid = {0}. - Killing process with pid = {0}. - - - - Loading the following project cache plugin: - {0} - Loading the following project cache plugin: - {0} - - - - Logging verbosity is set to: {0}. - Logging verbosity is set to: {0}. - - LOCALIZATION: {0} is an enum value of LoggerVerbosity. - - - - The parameters have been truncated beyond this point. To view all parameters, clear the MSBUILDTRUNCATETASKINPUTLOGGING environment variable. - The parameters have been truncated beyond this point. To view all parameters, clear the MSBUILDTRUNCATETASKINPUTLOGGING environment variable. - - - - Metaproject "{0}" generated. - Metaproject "{0}" generated. - - - - The operation cannot be completed because BeginBuild has not yet been called. - The operation cannot be completed because BeginBuild has not yet been called. - - - - MSB4270: No project cache plugins found in assembly "{0}". Expected one. - MSB4270: No project cache plugins found in assembly "{0}". Expected one. - - - - MSB4269: When any static graph node defines a project cache, all nodes must define the same project cache. The following project(s) do not contain a "{0}" item declaration: {1} - MSB4269: When any static graph node defines a project cache, all nodes must define the same project cache. The following project(s) do not contain a "{0}" item declaration: {1} - - - - A required NuGet assembly was not found. Expected Path: {0} - A required NuGet assembly was not found. Expected Path: {0} - - - - MSB4253: A null reference was returned from a user-provided ProjectInstanceFactoryFunc callback. This is not allowed. - MSB4253: A null reference was returned from a user-provided ProjectInstanceFactoryFunc callback. This is not allowed. - - {StrBegin="MSB4253: "} - LOCALIZATION: Do not localize the following words: ProjectInstanceFactoryFunc. - - - - Only item types may be referenced when removing with MatchOnMetadata. - Only item types may be referenced when removing with MatchOnMetadata. - - - - MatchOnMetadata only applies to Remove operations on items. - MatchOnMetadata only applies to Remove operations on items. - - - - MatchOnMetadataOptions is valid only when removing items using MatchOnMetadata. - MatchOnMetadataOptions is valid only when removing items using MatchOnMetadata. - - - - MatchOnMetadata cannot be used outside of a <Target>. - MatchOnMetadata cannot be used outside of a <Target>. - - - - Method {0} cannot be called with a collection containing null or empty target names. - Method {0} cannot be called with a collection containing null or empty target names. - - - - MSB4265: A single project cache plugin must be specified but multiple where found: {0} - MSB4265: A single project cache plugin must be specified but multiple where found: {0} - - - - MSB4273: The project cache threw an unhandled exception from the {0} method. - MSB4273: The project cache threw an unhandled exception from the {0} method. - - - - MSB4266: Failed to initialize the project cache. - MSB4266: Failed to initialize the project cache. - - - - MSB4267: The project cache failed while being queried for the following project: {0}. The cache is queried in parallel for multiple projects so this specific project might not be the cause. - MSB4267: The project cache failed while being queried for the following project: {0}. The cache is queried in parallel for multiple projects so this specific project might not be the cause. - - - - MSB4268: The project cache failed to shut down properly. - MSB4268: The project cache failed to shut down properly. - - - - MSB4250: ProjectGraph does not support ProjectReference items with the ToolsVersion metadata set. Found ProjectReference "{0}" with ToolsVersion in file "{1}" - MSB4250: ProjectGraph does not support ProjectReference items with the ToolsVersion metadata set. Found ProjectReference "{0}" with ToolsVersion in file "{1}" - - {StrBegin="MSB4250: "} - LOCALIZATION: Do not localize the following words: ProjectGraph, ProjectReference, ToolsVersion. - - - - Project "{0}" was not imported by "{1}" at ({2},{3}), due to the expression evaluating to an empty string. - Project "{0}" was not imported by "{1}" at ({2},{3}), due to the expression evaluating to an empty string. - - - - Property initial value: $({0})="{1}" Source: {2} - Property initial value: $({0})="{1}" Source: {2} - - - - MSB4274: Disabling the inproc node leads to performance degradation when using project cache plugins that emit proxy build requests. - MSB4274: Disabling the inproc node leads to performance degradation when using project cache plugins that emit proxy build requests. - - - - MSB4260: Project "{0}" skipped graph isolation constraints on referenced project "{1}" - MSB4260: Project "{0}" skipped graph isolation constraints on referenced project "{1}" - - LOCALIZATION: {0} and {1} are file paths - - - - "MSB4264: Invalid $(SolutionPath) property: {0}" - "MSB4264: Invalid $(SolutionPath) property: {0}" - - - - MSB4261: Multiple entry points with solutions detected: {0}. If static graph is loaded from a solution, that that solution must be the only entry point. - MSB4261: Multiple entry points with solutions detected: {0}. If static graph is loaded from a solution, that that solution must be the only entry point. - - LOCALIZATION: {0} is a semicolon delimited list of files - - - - Static graph loaded in {0} seconds: {1} nodes, {2} edges - Static graph loaded in {0} seconds: {1} nodes, {2} edges - - - - MSB4263: Project "{0}" has a reference to solution file "{1}". Referencing solutions is not supported in static graph. - - MSB4263: Project "{0}" has a reference to solution file "{1}". Referencing solutions is not supported in static graph. - - - LOCALIZATION: {0} and {1} are file paths - - - - MSB4262: Solution file "{0}" contains the following warnings and errors: - Warnings: {1} - Errors: {2} - - MSB4262: Solution file "{0}" contains the following warnings and errors: - Warnings: {1} - Errors: {2} - - - LOCALIZATION: {0} is a file, {1} and {2} are semicolon delimited lists of messages - - - - Task "{0}" requested {1} cores, acquired {2} cores, and now holds {3} cores total. - Task "{0}" requested {1} cores, acquired {2} cores, and now holds {3} cores total. - - - - Task "{0}" released {1} cores and now holds {2} cores total. - Task "{0}" released {1} cores and now holds {2} cores total. - - - - Task "{0}" asked to release {1} cores while holding only {2} and now holds {3} cores total. - Task "{0}" asked to release {1} cores while holding only {2} and now holds {3} cores total. - - - - MSB4181: The "{0}" task returned false but did not log an error. - MSB4181: The "{0}" task returned false but did not log an error. - {StrBegin="MSB4181: "} - - - MSB4254: The MSBuild task is building project(s) "{0}" which are not specified in the ProjectReference item. In isolated builds this probably means that the references are not explicitly specified as a ProjectReference item in "{1}" - MSB4254: The MSBuild task is building project(s) "{0}" which are not specified in the ProjectReference item. In isolated builds this probably means that the references are not explicitly specified as a ProjectReference item in "{1}" - - {StrBegin="MSB4254:"} - LOCALIZATION: Do not localize the following words: ProjectReference, MSBuild, task. - - - - Read uninitialized property "{0}" - Read uninitialized property "{0}" - - - - Using input build results caches: {0} - Using input build results caches: {0} - - LOCALIZATION: {0} is a list of semicolon separated file paths - - - - The operation cannot be completed because EndBuild has already been called but existing submissions have not yet completed. - The operation cannot be completed because EndBuild has already been called but existing submissions have not yet completed. - - - - The operation cannot be completed because the submission has already been executed. - The operation cannot be completed because the submission has already been executed. - - - - Cannot dispose the build manager because it is not idle. - Cannot dispose the build manager because it is not idle. - - - - MSB4197: Build was canceled. {0} - MSB4197: Build was canceled. {0} - {StrBegin="MSB4197: "} Error when the build stops suddenly for some reason. For example, because a child node died. - - - Build FAILED. - Build FAILED. - - - - Build succeeded. - Build succeeded. - - - - Build started {0}. - Build started {0}. - - - - Building target "{0}" completely. - Building target "{0}" completely. - {0} is the name of the target. - - - No input files were specified. - No input files were specified. - - - - Input file "{0}" is newer than output file "{1}". - Input file "{0}" is newer than output file "{1}". - {0} and {1} are filenames on disk. - - - Output file "{0}" does not exist. - Output file "{0}" does not exist. - {0} is a filename on disk. - - - Input file "{0}" does not exist. - Input file "{0}" does not exist. - {0} is a filename on disk. - - - Building target "{0}" partially, because some output files are out of date with respect to their input files. - Building target "{0}" partially, because some output files are out of date with respect to their input files. - {0} is the name of the target. - - - [{0}: Input={1}, Output={2}] Input file is newer than output file. - [{0}: Input={1}, Output={2}] Input file is newer than output file. - {0} is the name of an MSBuild item. {1} and {2} are filenames on disk. - - - [{0}: Input={1}, Output={2}] Output file does not exist. - [{0}: Input={1}, Output={2}] Output file does not exist. - {0} is the name of an MSBuild item. {1} and {2} are filenames on disk. - - - [{0}: Input={1}, Output={2}] Input file does not exist. - [{0}: Input={1}, Output={2}] Input file does not exist. - {0} is the name of an MSBuild item. {1} and {2} are filenames on disk. - - - The attribute "{0}" is a known MSBuild attribute, and cannot be accessed using this method. - The attribute "{0}" is a known MSBuild attribute, and cannot be accessed using this method. - - - - MSB4023: Cannot evaluate the item metadata "%({0})". {1} - MSB4023: Cannot evaluate the item metadata "%({0})". {1} - {StrBegin="MSB4023: "}UE: This message is shown when the value of an item metadata cannot be computed for some reason e.g. trying to apply - %(RootDir) to an item-spec that's not a valid path, would result in this error. - LOCALIZATION: "{1}" is a localized message explaining the problem. - - - MSB4193: MSBuild.exe could not be launched as a child node as it could not be found at the location "{0}". If necessary, specify the correct location in the BuildParameters, or with the MSBUILD_EXE_PATH environment variable. - MSB4193: MSBuild.exe could not be launched as a child node as it could not be found at the location "{0}". If necessary, specify the correct location in the BuildParameters, or with the MSBUILD_EXE_PATH environment variable. - {StrBegin="MSB4193: "} - - - MSB4218: Failed to successfully launch or connect to a child MSBuild.exe process. Verify that the MSBuild.exe "{0}" launches successfully, and that it is loading the same microsoft.build.dll that the launching process loaded. If the location seems incorrect, try specifying the correct location in the BuildParameters object, or with the MSBUILD_EXE_PATH environment variable. - MSB4218: Failed to successfully launch or connect to a child MSBuild.exe process. Verify that the MSBuild.exe "{0}" launches successfully, and that it is loading the same microsoft.build.dll that the launching process loaded. If the location seems incorrect, try specifying the correct location in the BuildParameters object, or with the MSBUILD_EXE_PATH environment variable. - {StrBegin="MSB4218: "} - - - MSB4117: The "{0}" item name is reserved, and cannot be used. - MSB4117: The "{0}" item name is reserved, and cannot be used. - {StrBegin="MSB4117: "}UE: This message is shown when the user tries to redefine one of the reserved MSBuild items e.g. @(Choose) - - - MSB4118: The "{0}" item metadata name is reserved, and cannot be used. - MSB4118: The "{0}" item metadata name is reserved, and cannot be used. - {StrBegin="MSB4118: "}UE: This message is shown when the user tries to redefine one of the reserved MSBuild item metadata names e.g. %(FullPath). Only MSBuild can set those. - - - MSB4004: The "{0}" property is reserved, and cannot be modified. - MSB4004: The "{0}" property is reserved, and cannot be modified. - {StrBegin="MSB4004: "}UE: This message is shown when the user tries to redefine one of the reserved MSBuild properties e.g. $(MSBuildProjectFile) - - - MSB4094: "{0}" is an invalid value for the "{1}" parameter of the "{3}" task. Multiple items cannot be passed into a parameter of type "{2}". - MSB4094: "{0}" is an invalid value for the "{1}" parameter of the "{3}" task. Multiple items cannot be passed into a parameter of type "{2}". - {StrBegin="MSB4094: "} - UE: This error is shown when a project tries to pass multiple items into a task parameter of type ITaskItem (singular). - - - - MSB4115: The "{0}" function only accepts a scalar value, but its argument "{1}" evaluates to "{2}" which is not a scalar value. - MSB4115: The "{0}" function only accepts a scalar value, but its argument "{1}" evaluates to "{2}" which is not a scalar value. - {StrBegin="MSB4115: "} - UE: This error is shown when a project tries to pass multiple items into a function in a conditional expression, that can only accept a scalar value (such as the "exists()" function). - - - - MSB4095: The item metadata %({0}) is being referenced without an item name. Specify the item name by using %(itemname.{0}). - MSB4095: The item metadata %({0}) is being referenced without an item name. Specify the item name by using %(itemname.{0}). - {StrBegin="MSB4095: "} - - - MSB4162: <{0}> is not valid. Child elements are not allowed below a item remove element. - MSB4162: <{0}> is not valid. Child elements are not allowed below a item remove element. - {StrBegin="MSB4162: "} - - - MSB4166: Child node "{0}" exited prematurely. Shutting down. Diagnostic information may be found in files in "{1}" and will be named MSBuild_*.failure.txt. This location can be changed by setting the MSBUILDDEBUGPATH environment variable to a different directory.{2} - MSB4166: Child node "{0}" exited prematurely. Shutting down. Diagnostic information may be found in files in "{1}" and will be named MSBuild_*.failure.txt. This location can be changed by setting the MSBUILDDEBUGPATH environment variable to a different directory.{2} - {StrBegin="MSB4166: "} {2} is exception text if any - - - MSB4085: A <Choose> must contain at least one <When>. - MSB4085: A <Choose> must contain at least one <When>. - {StrBegin="MSB4085: "} - - - MSB4114: <Choose> elements cannot be nested more than {0} levels deep. - MSB4114: <Choose> elements cannot be nested more than {0} levels deep. - {StrBegin="MSB4114: "}UE: This message appears if the project file contains unreasonably nested Choose elements. - LOCALIZATION: Do not localize "Choose" as it is an XML element name. - - - MSB4086: A numeric comparison was attempted on "{1}" that evaluates to "{2}" instead of a number, in condition "{0}". - MSB4086: A numeric comparison was attempted on "{1}" that evaluates to "{2}" instead of a number, in condition "{0}". - {StrBegin="MSB4086: "} - - - MSB4130: The condition "{0}" may have been evaluated incorrectly in an earlier version of MSBuild. Please verify that the order of the AND and OR clauses is written as intended. To avoid this warning, add parentheses to make the evaluation order explicit. - MSB4130: The condition "{0}" may have been evaluated incorrectly in an earlier version of MSBuild. Please verify that the order of the AND and OR clauses is written as intended. To avoid this warning, add parentheses to make the evaluation order explicit. - {StrBegin="MSB4130: "} - - - MSB4087: Specified condition "{0}" does not evaluate to a boolean. - MSB4087: Specified condition "{0}" does not evaluate to a boolean. - {StrBegin="MSB4087: "} - - - MSB4113: Specified condition "{0}" evaluates to "{1}" instead of a boolean. - MSB4113: Specified condition "{0}" evaluates to "{1}" instead of a boolean. - {StrBegin="MSB4113: "} - - - MSB4136: Error reading the toolset information from the configuration file "{0}". {1} - MSB4136: Error reading the toolset information from the configuration file "{0}". {1} - {StrBegin="MSB4136: "} - - - MSB4142: MSBuildToolsPath is not the same as MSBuildBinPath for the ToolsVersion "{0}" defined at "{1}". If both are present they must have the same value. - MSB4142: MSBuildToolsPath is not the same as MSBuildBinPath for the ToolsVersion "{0}" defined at "{1}". If both are present they must have the same value. - {StrBegin="MSB4142: "} - - - MSB4009: The default tasks file could not be successfully loaded. {0} - MSB4009: The default tasks file could not be successfully loaded. {0} - {StrBegin="MSB4009: "}UE: This message is shown when one of the default tasks file (*.tasks) located alongside the MSBuild binaries cannot - be opened/parsed. "{0}" contains a message explaining why. The filename itself is not part of the message but is provided - separately to loggers. - LOCALIZATION: "{0}" is a message from some FX method and is already localized. - - - MSB4010: The "{0}" files could not be successfully loaded from their expected location "{1}". Default tasks will not be available. {2} - MSB4010: The "{0}" files could not be successfully loaded from their expected location "{1}". Default tasks will not be available. {2} - {StrBegin="MSB4010: "}UE: This message is shown when the default tasks files that are located alongside the MSBuild binaries cannot be - found, either because they don't exist, or because of lack of permissions. "{2}" contains a message explaining why. - LOCALIZATION: "{2}" is a message from some FX method and is already localized. - - - Importing the file "{0}" into the file "{1}" results in a circular dependency. - Importing the file "{0}" into the file "{1}" results in a circular dependency. - - {0} is a file imported into the file "{1}" such that it results in a circular dependency. For e.g. if t1.targets imports - t2.targets and t2.targets tries to import t1.targets, then it results in a circular dependency. - - - - Search paths being used for {0} are {1} - Search paths being used for {0} are {1} - - - - Trying to import {0} using extensions path {1} - Trying to import {0} using extensions path {1} - - - - MSB4194: The override tasks file could not be successfully loaded. {0} - MSB4194: The override tasks file could not be successfully loaded. {0} - - {StrBegin="MSB4194: "}UE: This message is shown when one of the override tasks file (*.overridetasks) located alongside the MSBuild binaries cannot - be opened/parsed. "{0}" contains a message explaining why. The filename itself is not part of the message but is provided - separately to loggers. - LOCALIZATION: "{0}" is a message from some FX method and is already localized. - - - - The override tasks path "{0}" must not be a relative path and must exist on disk. Default tasks will not be overridden. - The override tasks path "{0}" must not be a relative path and must exist on disk. Default tasks will not be overridden. - - UE: This message is shown when the override tasks path in the registry or passed to the toolset is not a full path. - - - - A problem occurred loading the override tasks path "{0}". {1} - A problem occurred loading the override tasks path "{0}". {1} - - UE: This message is shown when the override tasks path in the registry or passed to the toolset is not a full path. - - - - MSB4196: The "{0}" files could not be successfully loaded from their expected location "{1}". Default tasks will not be overridden. {2} - MSB4196: The "{0}" files could not be successfully loaded from their expected location "{1}". Default tasks will not be overridden. {2} - - {StrBegin="MSB4196: "}UE: This message is shown when the override tasks files that are located alongside the MSBuild binaries cannot be - found, either because they don't exist, or because of lack of permissions. "{2}" contains a message explaining why. - LOCALIZATION: "{2}" is a message from some FX method and is already localized. - - - - MSB4195: There was an error gathering properties for tasks file evaluation. {0} - MSB4195: There was an error gathering properties for tasks file evaluation. {0} - - {StrBegin="MSB4195: "}UE: This message is shown when the gathering of properties for the evaluation of override and defaults tasks has an exception. "{0"} will be the exception message - - - MSB4133: A default tools version "{0}" was specified, but its definition could not be found. - MSB4133: A default tools version "{0}" was specified, but its definition could not be found. - {StrBegin="MSB4133: "} - - - MSB4011: "{0}" cannot be imported again. It was already imported at "{1}". This is most likely a build authoring error. This subsequent import will be ignored. {2} - MSB4011: "{0}" cannot be imported again. It was already imported at "{1}". This is most likely a build authoring error. This subsequent import will be ignored. {2} - {StrBegin="MSB4011: "} - - - MSB4211: The property "{0}" is being set to a value for the first time, but it was already consumed at "{1}". - MSB4211: The property "{0}" is being set to a value for the first time, but it was already consumed at "{1}". - {StrBegin="MSB4211: "} - - - MSB4210: "{0}" is attempting to import itself, directly or indirectly. This is most likely a build authoring error. The import will be ignored. - MSB4210: "{0}" is attempting to import itself, directly or indirectly. This is most likely a build authoring error. The import will be ignored. - {StrBegin="MSB4210: "} - - - MSB4079: The <ProjectExtensions> element occurs more than once. - MSB4079: The <ProjectExtensions> element occurs more than once. - {StrBegin="MSB4079: "} - - - MSB4012: The expression "{0}" cannot be used in this context. Item lists cannot be concatenated with other strings where an item list is expected. Use a semicolon to separate multiple item lists. - MSB4012: The expression "{0}" cannot be used in this context. Item lists cannot be concatenated with other strings where an item list is expected. Use a semicolon to separate multiple item lists. - {StrBegin="MSB4012: "}UE: This message is shown when the user does not properly specify an item list when an item list is expected - e.g. "badprefix@(foo)badsuffix" instead of "prefix; @(foo); suffix" - - - end of input - end of input - This is the name of the "EndOfInput" token. It is displayed in quotes as the - unexpected char or token when the end of a conditional was unexpectedly reached. - - - The previous error was converted to a warning because the task was called with ContinueOnError=true. - The previous error was converted to a warning because the task was called with ContinueOnError=true. - - - - {0} Error(s) - {0} Error(s) - - - - MSB4159: Error creating the toolset "{0}". {1} - MSB4159: Error creating the toolset "{0}". {1} - {StrBegin="MSB4159: "} - - - MSB4146: Cannot evaluate the property expression "{0}" found at "{1}". {2} - MSB4146: Cannot evaluate the property expression "{0}" found at "{1}". {2} - {StrBegin="MSB4146: "} - - - The <{0}> tag is no longer supported as a child of the <Project> element. Place this tag within a target, and add the name of the target to the "InitialTargets" attribute of the <Project> element. - The <{0}> tag is no longer supported as a child of the <Project> element. Place this tag within a target, and add the name of the target to the "InitialTargets" attribute of the <Project> element. - - - - Evaluation started ("{0}") - Evaluation started ("{0}") - - - - Evaluation finished ("{0}") - Evaluation finished ("{0}") - - - - Launching task "{0}" from assembly "{1}" in an external task host with a runtime of "{2}" and a process architecture of "{3}". - Launching task "{0}" from assembly "{1}" in an external task host with a runtime of "{2}" and a process architecture of "{3}". - - - - MSB4100: Expected "{0}" to evaluate to a boolean instead of "{1}", in condition "{2}". - MSB4100: Expected "{0}" to evaluate to a boolean instead of "{1}", in condition "{2}". - {StrBegin="MSB4100: "} - - - MSB4028: The "{0}" task's outputs could not be retrieved from the "{1}" parameter. {2} - MSB4028: The "{0}" task's outputs could not be retrieved from the "{1}" parameter. {2} - {StrBegin="MSB4028: "} - - - MSB4014: The build stopped unexpectedly because of an internal failure. - MSB4014: The build stopped unexpectedly because of an internal failure. - {StrBegin="MSB4014: "}UE: This message is shown when an unhandled exception terminates the build. The cause is most likely a programming - error in the build engine. - - - MSB4015: The build stopped unexpectedly because the "{0}" logger failed unexpectedly during shutdown. - MSB4015: The build stopped unexpectedly because the "{0}" logger failed unexpectedly during shutdown. - {StrBegin="MSB4015: "}UE: This message is used for a special exception that is thrown when a logger fails while shutting down (most likely - because of a programming error in the logger). When a logger dies, we cannot proceed with the build, and we throw a special - exception to abort the build. - - - MSB4016: The build stopped unexpectedly because the "{0}" logger failed unexpectedly during initialization. - MSB4016: The build stopped unexpectedly because the "{0}" logger failed unexpectedly during initialization. - {StrBegin="MSB4016: "}UE: This message is used for a special exception that is thrown when a logger fails while initializing itself (most - likely because of a programming error in the logger). When a logger dies, we cannot proceed with the build, and we throw a - special exception to abort the build. - - - MSB4017: The build stopped unexpectedly because of an unexpected logger failure. - MSB4017: The build stopped unexpectedly because of an unexpected logger failure. - {StrBegin="MSB4017: "}UE: This message is used for a special exception that is thrown when a logger fails while logging an event (most - likely because of a programming error in the logger). When a logger dies, we cannot proceed with the build, and we throw a - special exception to abort the build. - - - MSB4018: The "{0}" task failed unexpectedly. - MSB4018: The "{0}" task failed unexpectedly. - {StrBegin="MSB4018: "}UE: This message is shown when a task terminates because of an unhandled exception. The cause is most likely a - programming error in the task; however, it is also possible that the unhandled exception originated in the engine, and was - surfaced through the task when the task called into the engine. - - - MSB4187: Failed to receive a response from the task thread in the timeout period "{0}" ms. Shutting down. - MSB4187: Failed to receive a response from the task thread in the timeout period "{0}" ms. Shutting down. - {StrBegin="MSB4187: "} - - - MSB4088: Condition "{0}" is improperly constructed. - MSB4088: Condition "{0}" is improperly constructed. - {StrBegin="MSB4088: "} - - - MSB4105: Found an unexpected character '{2}' at position {1} in condition "{0}". Did you intend to use "=="? - MSB4105: Found an unexpected character '{2}' at position {1} in condition "{0}". Did you intend to use "=="? - {StrBegin="MSB4105: "} - - - MSB4106: Expected an item list at position {1} in condition "{0}". Did you forget the closing parenthesis? - MSB4106: Expected an item list at position {1} in condition "{0}". Did you forget the closing parenthesis? - {StrBegin="MSB4106: "} - - - MSB4107: Expected an item list at position {1} in condition "{0}". Did you forget the opening parenthesis after the '@'? To use a literal '@', use '%40' instead. - MSB4107: Expected an item list at position {1} in condition "{0}". Did you forget the opening parenthesis after the '@'? To use a literal '@', use '%40' instead. - {StrBegin="MSB4107: "} - - - MSB4108: Expected an item list at position {1} in condition "{0}". Did you forget to close a quote inside the item list expression? - MSB4108: Expected an item list at position {1} in condition "{0}". Did you forget to close a quote inside the item list expression? - {StrBegin="MSB4108: "} - - - MSB4109: Expected a property at position {1} in condition "{0}". Did you forget the closing parenthesis? - MSB4109: Expected a property at position {1} in condition "{0}". Did you forget the closing parenthesis? - {StrBegin="MSB4109: "} - - - MSB4110: Expected a property at position {1} in condition "{0}". Did you forget the opening parenthesis after the '$'? To use a literal '$', use '%24' instead. - MSB4110: Expected a property at position {1} in condition "{0}". Did you forget the opening parenthesis after the '$'? To use a literal '$', use '%24' instead. - {StrBegin="MSB4110: "} - - - MSB4101: Expected a closing quote after position {1} in condition "{0}". - MSB4101: Expected a closing quote after position {1} in condition "{0}". - {StrBegin="MSB4101: "} - - - MSB4019: The imported project "{0}" was not found. Confirm that the expression in the Import declaration "{1}" is correct, and that the file exists on disk. - MSB4019: The imported project "{0}" was not found. Confirm that the expression in the Import declaration "{1}" is correct, and that the file exists on disk. - {StrBegin="MSB4019: "}LOCALIZATION: <Import> should not be localized. - - - MSB4226: The imported project "{0}" was not found. Also, tried to find "{1}" in the fallback search path(s) for {2} - {3} . These search paths are defined in "{4}". Confirm that the path in the <Import> declaration is correct, and that the file exists on disk in one of the search paths. - MSB4226: The imported project "{0}" was not found. Also, tried to find "{1}" in the fallback search path(s) for {2} - {3} . These search paths are defined in "{4}". Confirm that the path in the <Import> declaration is correct, and that the file exists on disk in one of the search paths. - {StrBegin="MSB4226: "}LOCALIZATION: <Import> should not be localized. - - - MSB4226: The imported project "{0}" was not found. Also, tried to find "{1}" in the fallback search path(s) for {2} - {3} . Confirm that the path in the <Import> declaration is correct, and that the file exists on disk in one of the search paths. - MSB4226: The imported project "{0}" was not found. Also, tried to find "{1}" in the fallback search path(s) for {2} - {3} . Confirm that the path in the <Import> declaration is correct, and that the file exists on disk in one of the search paths. - {StrBegin="MSB4226: "}LOCALIZATION: <Import> should not be localized. - - - MSB4089: Incorrect number of arguments to function in condition "{0}". Found {1} argument(s) when expecting {2}. - MSB4089: Incorrect number of arguments to function in condition "{0}". Found {1} argument(s) when expecting {2}. - {StrBegin="MSB4089: "} - - - MSB4020: The value "{0}" of the "{1}" attribute in element <{2}> is invalid. - MSB4020: The value "{0}" of the "{1}" attribute in element <{2}> is invalid. - {StrBegin="MSB4020: "}UE: This is a generic message that is displayed when we find a project element with an incorrect value for one of its - attributes e.g. <Import Project=""> -- the value of Project should not be an empty string. - - - MSB4111: At most one of the include, remove, and update attributes may be specified for an item element. - MSB4111: At most one of the include, remove, and update attributes may be specified for an item element. - - - - MSB4102: The value "{0}" of the "{1}" attribute in element <{2}> is invalid. {3} - MSB4102: The value "{0}" of the "{1}" attribute in element <{2}> is invalid. {3} - {StrBegin="MSB4102: "}UE: This is a generic message that is displayed when we find a project element with an incorrect value for one of its - attributes. At the end of the message we show the exception text we got trying to use the value. - - - MSB4234: Invalid binary logger parameter(s): "{0}". Expected: ProjectImports={{None,Embed,ZipFile}} and/or [LogFile=]filePath.binlog (the log file name or path, must have the ".binlog" extension). - MSB4234: Invalid binary logger parameter(s): "{0}". Expected: ProjectImports={{None,Embed,ZipFile}} and/or [LogFile=]filePath.binlog (the log file name or path, must have the ".binlog" extension). - - - - MSB4021: The "ContinueOnError" attribute of the "{0}" task is not valid. {1} - MSB4021: The "ContinueOnError" attribute of the "{0}" task is not valid. {1} - {StrBegin="MSB4021: "}LOCALIZATION: "ContinueOnError" should not be localized. "{1}" is a message from another exception explaining the problem. - - - MSB4022: The result "{0}" of evaluating the value "{1}" of the "{2}" attribute in element <{3}> is not valid. - MSB4022: The result "{0}" of evaluating the value "{1}" of the "{2}" attribute in element <{3}> is not valid. - {StrBegin="MSB4022: "}UE: This message is shown when the engine is checking the correctness of the value (after evaluating embedded - properties/items) assigned to an XML attribute of an XML element in the project file. - - - MSB4104: Failed to write to log file "{0}". {1} - MSB4104: Failed to write to log file "{0}". {1} - {StrBegin="MSB4104: "}UE: This is shown when the File Logger can't create or write to the file it was instructed to log to. - - - MSB4024: The imported project file "{0}" could not be loaded. {1} - MSB4024: The imported project file "{0}" could not be loaded. {1} - {StrBegin="MSB4024: "}UE: This message is shown when an imported project file cannot be loaded because of incorrect XML. The project - filename is not part of the message because it is provided separately to loggers. - LOCALIZATION: {0} is a localized message from the CLR/FX explaining why the project is invalid. - - - MSB4147: The property "{0}" at "{1}" is invalid. {2} - MSB4147: The property "{0}" at "{1}" is invalid. {2} - {StrBegin="MSB4147: "} - - - MSB4177: Invalid property. {0} - MSB4177: Invalid property. {0} - {StrBegin="MSB4177: "} - UE: {0} is a localized message indicating what the problem was. - - - MSB4143: The registry expression "{0}" cannot be evaluated. {1} - MSB4143: The registry expression "{0}" cannot be evaluated. {1} - {StrBegin="MSB4143: "} - UE: This message is shown when the user attempts to provide an expression like "$(Registry:HKEY_LOCAL_MACHINE\Software\Vendor\Tools@TaskLocation)" - LOCALIZATION: "{0}" is the expression that was bad. "{1}" is a message from an FX exception that describes why the expression is bad. - - - - MSB4184: The expression "{0}" cannot be evaluated. {1} - MSB4184: The expression "{0}" cannot be evaluated. {1} - {StrBegin="MSB4184: "} - Double quotes as the expression will typically have single quotes in it. - UE: This message is shown when the user attempts to provide an expression like "$(SomeProperty.ToLower())" or "@(Foo->Bar())" - LOCALIZATION: "{0}" is the expression that was bad. "{1}" is a message from an FX exception that describes why the expression is bad. - - - - The quotes were mismatched. - The quotes were mismatched. - This is a potential suffix to "InvalidFunctionPropertyExpression" so it has no error code. - - - The parentheses were mismatched. - The parentheses were mismatched. - This is a potential suffix to "InvalidFunctionPropertyExpression" so it has no error code. - - - The square brackets were mismatched. - The square brackets were mismatched. - This is a potential suffix to "InvalidFunctionPropertyExpression" so it has no error code. - - - MSB4185: The function "{0}" on type "{1}" is not available for execution as an MSBuild property function. - MSB4185: The function "{0}" on type "{1}" is not available for execution as an MSBuild property function. - - {StrBegin="MSB4185: "} - UE: This message is shown when the user attempts to provide an expression like "$([System.DateTime]::Now)", but the expression has not been enabled - LOCALIZATION: "{0}" is the static function name, "{1}" is the .NET Framework type name - - - - MSB4212: Invalid static method invocation syntax: "{0}". The type "{1}" is either not available for execution in an MSBuild property function or could not be found. - MSB4212: Invalid static method invocation syntax: "{0}". The type "{1}" is either not available for execution in an MSBuild property function or could not be found. - - {StrBegin="MSB4212: "} - UE: This message is shown when the user attempts to provide an expression like "$([System.DateTime]::Now)", but the expression has not been enabled - LOCALIZATION: "{0}" is the function expression which is in error. "{1}" is the .NET Framework type name - - - - MSB4186: Invalid static method invocation syntax: "{0}". {1} Static method invocation should be of the form: $([FullTypeName]::Method()), e.g. $([System.IO.Path]::Combine(`a`, `b`)). Check that all parameters are defined, are of the correct type, and are specified in the right order. - MSB4186: Invalid static method invocation syntax: "{0}". {1} Static method invocation should be of the form: $([FullTypeName]::Method()), e.g. $([System.IO.Path]::Combine(`a`, `b`)). Check that all parameters are defined, are of the correct type, and are specified in the right order. - {StrBegin="MSB4186: "} - UE: This message is shown when the user attempts to call a static method on a type, but has used the incorrect syntax - LOCALIZATION: "{0}" is the function expression which is in error. "{1}" is a message from an FX exception that describes why the expression is bad. - - - - MSB4198: The expression "{0}" cannot be evaluated on item "{1}". {2} - MSB4198: The expression "{0}" cannot be evaluated on item "{1}". {2} - - {StrBegin="MSB4198: "} - Double quotes as the expression will typically have single quotes in it. - UE: This message is shown when the user attempts to provide an expression like "@(SomeItem->DirectoryName())" - LOCALIZATION: "{0}" is the expression that was bad, "{1}" is the item or file that was being worked on. "{2}" is a message from an FX exception that describes why the expression is bad. - - - - MSB4199: Invalid transformation syntax "{0}". An item function was not found with that name and {1} parameters. - MSB4199: Invalid transformation syntax "{0}". An item function was not found with that name and {1} parameters. - - {StrBegin="MSB4199: "} - UE: This message is shown when the user attempts to call a transformation on an item, but has used the incorrect syntax - LOCALIZATION: "{0}" is the function which is in error - - - - MSB4200: Unknown item transformation function "{0}". - MSB4200: Unknown item transformation function "{0}". - - {StrBegin="MSB4200: "} - UE: This message is shown when the user attempts to provide an expression like @(Item->SomeTransform()), but SomeTransform is unknown - LOCALIZATION: "{0}" is the function name - - - - MSB4026: The "{0}={1}" parameter for the "{2}" task is invalid. - MSB4026: The "{0}={1}" parameter for the "{2}" task is invalid. - {StrBegin="MSB4026: "}UE: This message is displayed when a task has an invalid parameter that cannot be initialized. - - - MSB4027: The "{0}" task generated invalid items from the "{1}" output parameter. {2} - MSB4027: The "{0}" task generated invalid items from the "{1}" output parameter. {2} - {StrBegin="MSB4027: "} - - - MSB4029: The "{0}" task has an invalid output specification. The "TaskParameter" attribute is required, and either the "ItemName" or "PropertyName" attribute must be specified (but not both). - MSB4029: The "{0}" task has an invalid output specification. The "TaskParameter" attribute is required, and either the "ItemName" or "PropertyName" attribute must be specified (but not both). - {StrBegin="MSB4029: "}LOCALIZATION: "TaskParameter", "ItemName" and "PropertyName" should not be localized. - - - MSB4030: "{0}" is an invalid value for the "{1}" parameter of the "{3}" task. The "{1}" parameter is of type "{2}". - MSB4030: "{0}" is an invalid value for the "{1}" parameter of the "{3}" task. The "{1}" parameter is of type "{2}". - {StrBegin="MSB4030: "}UE: This error is shown when a type mis-match occurs between the value assigned to task parameter in the project file - and the type of the .NET property that corresponds to the task parameter. For example, if an int task parameter called "Count" - is assigned the value "x", this error would be displayed: <MyTask Count="x" /> - - - MSB4137: Invalid value specified in the configuration file at "{0}". Property name or tools version name is an empty string. - MSB4137: Invalid value specified in the configuration file at "{0}". Property name or tools version name is an empty string. - {StrBegin="MSB4137: "} - - - MSB4163: <ItemDefinitionGroup> is not allowed inside a target. - MSB4163: <ItemDefinitionGroup> is not allowed inside a target. - {StrBegin="MSB4163: "} - - - MSB4096: The item "{0}" in item list "{1}" does not define a value for metadata "{2}". In order to use this metadata, either qualify it by specifying %({1}.{2}), or ensure that all items in this list define a value for this metadata. - MSB4096: The item "{0}" in item list "{1}" does not define a value for metadata "{2}". In order to use this metadata, either qualify it by specifying %({1}.{2}), or ensure that all items in this list define a value for this metadata. - {StrBegin="MSB4096: "} - - - MSB4099: A reference to an item list at position {1} is not allowed in this condition "{0}". - MSB4099: A reference to an item list at position {1} is not allowed in this condition "{0}". - {StrBegin="MSB4099: "} - - - MSB4191: The reference to custom metadata "{2}" at position {1} is not allowed in this condition "{0}". - MSB4191: The reference to custom metadata "{2}" at position {1} is not allowed in this condition "{0}". - {StrBegin="MSB4191: "} - - - MSB4190: The reference to the built-in metadata "{2}" at position {1} is not allowed in this condition "{0}". - MSB4190: The reference to the built-in metadata "{2}" at position {1} is not allowed in this condition "{0}". - {StrBegin="MSB4190: "} - - - MSB4033: "{0}" is a reserved item metadata, and cannot be redefined as a custom metadata on the item. - MSB4033: "{0}" is a reserved item metadata, and cannot be redefined as a custom metadata on the item. - {StrBegin="MSB4033: "} - - - An InternalLoggerException can only be thrown by the MSBuild engine. The public constructors of this class cannot be used to create an instance of the exception. - An InternalLoggerException can only be thrown by the MSBuild engine. The public constructors of this class cannot be used to create an instance of the exception. - UE: This message is shown when a user tries to instantiate a special exception called InternalLoggerException through the OM -- - only the engine is allowed to create and throw this exception. - LOCALIZATION: "InternalLoggerException" and "MSBuild" should not be localized. - - - Initial Items: - Initial Items: - - - - Environment at start of build: - Environment at start of build: - - - - MSB4164: The value "{0}" of metadata "{1}" contains an item list expression. Item list expressions are not allowed on default metadata values. - MSB4164: The value "{0}" of metadata "{1}" contains an item list expression. Item list expressions are not allowed on default metadata values. - {StrBegin="MSB4164: "} - - - MSB4035: The required attribute "{0}" is empty or missing from the element <{1}>. - MSB4035: The required attribute "{0}" is empty or missing from the element <{1}>. - {StrBegin="MSB4035: "}UE: This message is shown when a user leaves off a required attribute from a project element - e.g. <UsingTask AssemblyName="foo"> -- this is missing the "TaskName" attribute. - - - MSB4232: Items that are outside Target elements must have one of the following operations: Include, Update, or Remove. - MSB4232: Items that are outside Target elements must have one of the following operations: Include, Update, or Remove. - {StrBegin="MSB4232: "} Target, Include, Update, and Remove should not be localized and their casing should not be changed - - - MSB4036: The "{0}" task was not found. Check the following: 1.) The name of the task in the project file is the same as the name of the task class. 2.) The task class is "public" and implements the Microsoft.Build.Framework.ITask interface. 3.) The task is correctly declared with <UsingTask> in the project file, or in the *.tasks files located in the "{1}" directory. - MSB4036: The "{0}" task was not found. Check the following: 1.) The name of the task in the project file is the same as the name of the task class. 2.) The task class is "public" and implements the Microsoft.Build.Framework.ITask interface. 3.) The task is correctly declared with <UsingTask> in the project file, or in the *.tasks files located in the "{1}" directory. - {StrBegin="MSB4036: "}LOCALIZATION: <UsingTask> and "*.tasks" should not be localized. - - - MSB4141: MSBuildToolsPath is not specified for the ToolsVersion "{0}" defined at "{1}", or the value specified evaluates to the empty string. - MSB4141: MSBuildToolsPath is not specified for the ToolsVersion "{0}" defined at "{1}", or the value specified evaluates to the empty string. - {StrBegin="MSB4141: "} - - - MSB4222: ToolsVersion "{0}", defined at "{1}", contains sub-toolset "{2}" which sets MSBuildBinPath or MSBuildToolsPath. This is not supported in sub-toolsets. - MSB4222: ToolsVersion "{0}", defined at "{1}", contains sub-toolset "{2}" which sets MSBuildBinPath or MSBuildToolsPath. This is not supported in sub-toolsets. - - - - MSB4144: Multiple definitions were found for the toolset "{0}". - MSB4144: Multiple definitions were found for the toolset "{0}". - {StrBegin="MSB4144: "} - - - MSB4225: Toolset contains multiple definitions of searchPaths for the OS "{0}" at "{1}". - MSB4225: Toolset contains multiple definitions of searchPaths for the OS "{0}" at "{1}". - {StrBegin="MSB4225: "} - - - MSB4145: Multiple definitions were found for the property "{0}". - MSB4145: Multiple definitions were found for the property "{0}". - {StrBegin="MSB4145: "} - - - MSB4082: Choose has more than one <Otherwise> element. - MSB4082: Choose has more than one <Otherwise> element. - {StrBegin="MSB4082: "} - - - MSB4038: The element <{0}> must be last under element <{1}>. Found element <{2}> instead. - MSB4038: The element <{0}> must be last under element <{1}>. Found element <{2}> instead. - {StrBegin="MSB4038: "} - - - MSB4138: Non-string data was specified at the registry location "{0}". - MSB4138: Non-string data was specified at the registry location "{0}". - {StrBegin="MSB4138: "} - - - MSB4039: No "{0}" element was found in the project file. - MSB4039: No "{0}" element was found in the project file. - {StrBegin="MSB4039: "} - - - MSB4040: There is no target in the project. - MSB4040: There is no target in the project. - {StrBegin="MSB4040: "} - - - A null entry was found in the collection of loggers. - A null entry was found in the collection of loggers. - - - - MaxNodeCount may only be assigned a value greater than zero. - MaxNodeCount may only be assigned a value greater than zero. - - - - Overriding target "{0}" in project "{1}" with target "{2}" from project "{3}". - Overriding target "{0}" in project "{1}" with target "{2}" from project "{3}". - - - - {0} ms {1} {2} calls - {0} ms {1} {2} calls - - - - (* = timing was not recorded because of reentrancy) - (* = timing was not recorded because of reentrancy) - - - - The project file "{0}" was not found. - The project file "{0}" was not found. - UE: This message is shown when the user calls into the OM to build a project that doesn't exist on disk. - - - Done building project "{0}" -- FAILED. - Done building project "{0}" -- FAILED. - - - - Done building project "{0}". - Done building project "{0}". - - - - Done Building Project "{0}" ({1} target(s)). - Done Building Project "{0}" ({1} target(s)). - - - - Done Building Project "{0}" (default targets). - Done Building Project "{0}" (default targets). - - - - Done Building Project "{0}" ({1} target(s)) -- FAILED. - Done Building Project "{0}" ({1} target(s)) -- FAILED. - - - - Done Building Project "{0}" (default targets) -- FAILED. - Done Building Project "{0}" (default targets) -- FAILED. - - - - MSB4041: The default XML namespace of the project must be the MSBuild XML namespace or no namespace. If the project is authored in the MSBuild 2003 format, please add xmlns="{0}" to the <Project> element. If the project has been authored in the old 1.0 or 1.2 format, please convert it to MSBuild 2003 format. - MSB4041: The default XML namespace of the project must be the MSBuild XML namespace or no namespace. If the project is authored in the MSBuild 2003 format, please add xmlns="{0}" to the <Project> element. If the project has been authored in the old 1.0 or 1.2 format, please convert it to MSBuild 2003 format. - {StrBegin="MSB4041: "}UE: This is a Beta 1 message only. - LOCALIZATION: <Project>, "MSBuild" and "xmlns" should not be localized. - - - Project Performance Summary: - Project Performance Summary: - - - - Project "{0}" is building "{1}" ({2} target(s)): - Project "{0}" is building "{1}" ({2} target(s)): - - - - Project "{0}" is building "{1}" (default targets): - Project "{0}" is building "{1}" (default targets): - - - - Project "{0}" ({1} target(s)): - Project "{0}" ({1} target(s)): - - - - Project "{0}" (default targets): - Project "{0}" (default targets): - - - - Task name cannot be empty. - Task name cannot be empty. - - - - MSB4075: The project file "{0}" must be opened in the Visual Studio IDE and converted to the latest version before it can be built by MSBuild. - MSB4075: The project file "{0}" must be opened in the Visual Studio IDE and converted to the latest version before it can be built by MSBuild. - {StrBegin="MSB4075: "} - - - MSB4192: The project file "{0}" is in the ".vcproj" file format, which MSBuild no longer supports. Please convert the project by opening it in the Visual Studio IDE or running the conversion tool, or use MSBuild 3.5 or earlier to build it. - MSB4192: The project file "{0}" is in the ".vcproj" file format, which MSBuild no longer supports. Please convert the project by opening it in the Visual Studio IDE or running the conversion tool, or use MSBuild 3.5 or earlier to build it. - {StrBegin="MSB4192: "} LOC: ".vcproj" should not be localized - - - Initial Properties: - Initial Properties: - - - - MSB4148: The name of a property stored under the registry key "{0}" has zero length. - MSB4148: The name of a property stored under the registry key "{0}" has zero length. - {StrBegin="MSB4148: "} - - - Property reassignment: $({0})="{1}" (previous value: "{2}") at {3} - Property reassignment: $({0})="{1}" (previous value: "{2}") at {3} - - - - MSB4043: The item metadata reference "{0}" is invalid because it is qualified with an item name. Item metadata referenced in transforms do not need to be qualified, because the item name is automatically deduced from the items being transformed. Change "{0}" to "%({1})". - MSB4043: The item metadata reference "{0}" is invalid because it is qualified with an item name. Item metadata referenced in transforms do not need to be qualified, because the item name is automatically deduced from the items being transformed. Change "{0}" to "%({1})". - {StrBegin="MSB4043: "}UE: This message is shown when the user does something like this: @(foo->'%(foo.metadata)'). There is no need to specify - "foo.metadata", because "foo" is automatically deduced. In corollary, "bar.metadata" is not allowed either, where "bar" is a different - item list type. - - - MSB4135: Error reading the toolset information from the registry location "{0}". {1} - MSB4135: Error reading the toolset information from the registry location "{0}". {1} - {StrBegin="MSB4135: "} - - - MSB4044: The "{0}" task was not given a value for the required parameter "{1}". - MSB4044: The "{0}" task was not given a value for the required parameter "{1}". - {StrBegin="MSB4044: "}UE: This message is shown when a task parameter designated as "required" is not set in the project file. - - - MSB4112: The targets in this project have been disabled by the host and therefore cannot be built at this time. This may have been done for security reasons. To enable the targets, the host must set Project.BuildEnabled to "true". - MSB4112: The targets in this project have been disabled by the host and therefore cannot be built at this time. This may have been done for security reasons. To enable the targets, the host must set Project.BuildEnabled to "true". - {StrBegin="MSB4112: "} - - - MSB4093: The "{0}" parameter of the "{1}" task cannot be written to because it does not have a "set" accessor. - MSB4093: The "{0}" parameter of the "{1}" task cannot be written to because it does not have a "set" accessor. - {StrBegin="MSB4093: "}UE: This error is shown when a project tries to assign a value to a task parameter that does not have a "set" - accessor on the corresponding .NET property on the task class. - - - Skipping target "{0}" because it has no inputs. - Skipping target "{0}" because it has no inputs. - - - - Though the target has declared its inputs, the input specification only references empty properties and/or empty item lists. - Though the target has declared its inputs, the input specification only references empty properties and/or empty item lists. - - - - Skipping target "{0}" because it has no outputs. - Skipping target "{0}" because it has no outputs. - - - - Though the target has declared its outputs, the output specification only references empty properties and/or empty item lists. - Though the target has declared its outputs, the output specification only references empty properties and/or empty item lists. - - - - Skipping target "{0}" because all output files are up-to-date with respect to the input files. - Skipping target "{0}" because all output files are up-to-date with respect to the input files. - - - - Input files: {0} - Input files: {0} - {0} is a semicolon-separated list of filenames. - - - Output files: {0} - Output files: {0} - {0} is a semicolon-separated list of filenames. - - - {0}: Defaulting .NET Framework v{1} to the .NET Framework v4.0 version of aspnet_compiler.exe. To change the version of the tool used, please set the "ToolPath" parameter with the correct path to the tool. - {0}: Defaulting .NET Framework v{1} to the .NET Framework v4.0 version of aspnet_compiler.exe. To change the version of the tool used, please set the "ToolPath" parameter with the correct path to the tool. - - - - MSB4203: {0}: Invalid TargetFrameworkMoniker {1}. The AspNetCompiler task only supports targeting the .NET Framework. - MSB4203: {0}: Invalid TargetFrameworkMoniker {1}. The AspNetCompiler task only supports targeting the .NET Framework. - {StrBegin="MSB4203: "} - - - MSB4205: The website project in this solution is targeting the v2.0 runtime, but it is not installed. - MSB4205: The website project in this solution is targeting the v2.0 runtime, but it is not installed. - {StrBegin="MSB4205: "} - - - MSB4204: {0}: Invalid TargetFrameworkMoniker {1}. {2}. - MSB4204: {0}: Invalid TargetFrameworkMoniker {1}. {2}. - {StrBegin="MSB4204: "} - - - Using the MSBuild v3.5 solution wrapper generator because the tools version was set to {0}. - Using the MSBuild v3.5 solution wrapper generator because the tools version was set to {0}. - - - - Using the MSBuild v3.5 solution wrapper generator with a tools version of {0} because the solution file format was version {1} and no tools version was supplied. - Using the MSBuild v3.5 solution wrapper generator with a tools version of {0} because the solution file format was version {1} and no tools version was supplied. - - - - Building solution configuration "{0}". - Building solution configuration "{0}". - UE: This is not an error, so doesn't need an error code. - - - MSB4160: A circular dependency involving project "{0}" has been detected. - MSB4160: A circular dependency involving project "{0}" has been detected. - {StrBegin="MSB4160: "} - - - MSB4126: The specified solution configuration "{0}" is invalid. Please specify a valid solution configuration using the Configuration and Platform properties (e.g. MSBuild.exe Solution.sln /p:Configuration=Debug /p:Platform="Any CPU") or leave those properties blank to use the default solution configuration. - MSB4126: The specified solution configuration "{0}" is invalid. Please specify a valid solution configuration using the Configuration and Platform properties (e.g. MSBuild.exe Solution.sln /p:Configuration=Debug /p:Platform="Any CPU") or leave those properties blank to use the default solution configuration. - {StrBegin="MSB4126: "}UE: The solution filename is provided separately to loggers. - - - MSB4046: Error reading project file "{0}": {1} - MSB4046: Error reading project file "{0}": {1} - {StrBegin="MSB4046: "} - - - MSB4125: The project file name "{0}" is invalid. {1} - MSB4125: The project file name "{0}" is invalid. {1} - {StrBegin="MSB4125: "}UE: The solution filename is provided separately to loggers. - - - MSB4051: Project {0} is referencing a project with GUID {1}, but a project with this GUID was not found in the .SLN file. - MSB4051: Project {0} is referencing a project with GUID {1}, but a project with this GUID was not found in the .SLN file. - {StrBegin="MSB4051: "}UE: The solution filename is provided separately to loggers. - - - MSB4078: The project file "{0}" is not supported by MSBuild and cannot be built. - MSB4078: The project file "{0}" is not supported by MSBuild and cannot be built. - {StrBegin="MSB4078: "} - - - MSB4054: The solution file must be opened in the Visual Studio IDE and converted to the latest version before it can be built by MSBuild. - MSB4054: The solution file must be opened in the Visual Studio IDE and converted to the latest version before it can be built by MSBuild. - {StrBegin="MSB4054: "}UE: The solution filename is provided separately to loggers. - - - MSB4121: The project configuration for project "{0}" was not specified in the solution file for the solution configuration "{1}". - MSB4121: The project configuration for project "{0}" was not specified in the solution file for the solution configuration "{1}". - {StrBegin="MSB4121: "} - - - The project "{0}" is not selected for building in solution configuration "{1}". - The project "{0}" is not selected for building in solution configuration "{1}". - - UE: This is not an error, so doesn't need an error code. - - - - MSB4122: Scanning project dependencies for project "{0}" failed. {1} - MSB4122: Scanning project dependencies for project "{0}" failed. {1} - {StrBegin="MSB4122: "} - - - MSB4149: The tools version "{0}" of the solution does not support building projects with a different tools version. - MSB4149: The tools version "{0}" of the solution does not support building projects with a different tools version. - {StrBegin="MSB4149: "} - - - Web projects do not support the "Clean" target. Continuing with remaining projects ... - Web projects do not support the "Clean" target. Continuing with remaining projects ... - UE: This is not an error, so doesn't need an error code. - LOCALIZATION: Do not localize "Clean". - - - Web projects do not support the "Publish" target. Continuing with remaining projects ... - Web projects do not support the "Publish" target. Continuing with remaining projects ... - UE: This is not an error, so doesn't need an error code. - LOCALIZATION: Do not localize "Publish". - - - Skipping because the "$(AspNetConfiguration)" configuration is not supported for this web project. You can use the AspNetConfiguration property to override the configuration used for building web projects, by adding /p:AspNetConfiguration=<value> to the command line. Currently web projects only support Debug and Release configurations. - Skipping because the "$(AspNetConfiguration)" configuration is not supported for this web project. You can use the AspNetConfiguration property to override the configuration used for building web projects, by adding /p:AspNetConfiguration=<value> to the command line. Currently web projects only support Debug and Release configurations. - - UE: This is not an error, so doesn't need an error code. - LOCALIZATION: Do NOT localize "AspNetConfiguration", "Debug", "Release". - - - - Target "{0}" skipped. Previously built unsuccessfully. - Target "{0}" skipped. Previously built unsuccessfully. - - - - Target "{0}" skipped. Previously built successfully. - Target "{0}" skipped. Previously built successfully. - - - - MSB4116: The condition "{1}" on the "{0}" target has a reference to item metadata. References to item metadata are not allowed in target conditions unless they are part of an item transform. - MSB4116: The condition "{1}" on the "{0}" target has a reference to item metadata. References to item metadata are not allowed in target conditions unless they are part of an item transform. - {StrBegin="MSB4116: "} - - - MSB4057: The target "{0}" does not exist in the project. - MSB4057: The target "{0}" does not exist in the project. - {StrBegin="MSB4057: "} - - - The target "{0}" listed in a BeforeTargets attribute at "{1}" does not exist in the project, and will be ignored. - The target "{0}" listed in a BeforeTargets attribute at "{1}" does not exist in the project, and will be ignored. - - - - The target "{0}" listed in an AfterTargets attribute at "{1}" does not exist in the project, and will be ignored. - The target "{0}" listed in an AfterTargets attribute at "{1}" does not exist in the project, and will be ignored. - - - - Done building target "{0}" in project "{1}" -- FAILED. - Done building target "{0}" in project "{1}" -- FAILED. - - - - Done building target "{0}" in project "{1}". - Done building target "{0}" in project "{1}". - - - - {0}: (TargetId:{1}) - {0}: (TargetId:{1}) - - - - Target output items: - Target output items: - - - - {0} - {0} - - - - MSB4058: The "{0}" target is missing its output specification. If a target declares inputs, it must also declare outputs. - MSB4058: The "{0}" target is missing its output specification. If a target declares inputs, it must also declare outputs. - {StrBegin="MSB4058: "} - - - Target Performance Summary: - Target Performance Summary: - - - - Target "{0}" skipped, due to false condition; ({1}) was evaluated as ({2}). - Target "{0}" skipped, due to false condition; ({1}) was evaluated as ({2}). - - - - Target "{0}" skipped. The target does not exist in the project and SkipNonexistentTargets is set to true. - Target "{0}" skipped. The target does not exist in the project and SkipNonexistentTargets is set to true. - LOCALIZATION: Do NOT localize "SkipNonexistentTargets" or "true". - - - Target "{0}" in file "{1}" from project "{2}": - Target "{0}" in file "{1}" from project "{2}": - - - - Target "{0}" in file "{1}" from project "{2}" (entry point): - Target "{0}" in file "{1}" from project "{2}" (entry point): - - - - Target "{0}" in file "{1}" from project "{2}" (target "{3}" depends on it): - Target "{0}" in file "{1}" from project "{2}" (target "{3}" depends on it): - - - - Target "{0}" in file "{1}" from project "{2}" (designated to run before target "{3}"): - Target "{0}" in file "{1}" from project "{2}" (designated to run before target "{3}"): - - - - Target "{0}" in file "{1}" from project "{2}" (designated to run after target "{3}"): - Target "{0}" in file "{1}" from project "{2}" (designated to run after target "{3}"): - - - - Target "{0}" in project "{1}": - Target "{0}" in project "{1}": - - - - Target "{0}" in project "{1}" (entry point): - Target "{0}" in project "{1}" (entry point): - - - - Target "{0}" in project "{1}" (target "{2}" depends on it): - Target "{0}" in project "{1}" (target "{2}" depends on it): - - - - Target "{0}" in project "{1}" (designated to run before target "{2}"): - Target "{0}" in project "{1}" (designated to run before target "{2}"): - - - - Target "{0}" in project "{1}" (designated to run after target "{2}"): - Target "{0}" in project "{1}" (designated to run after target "{2}"): - - - - Target {0}: - Target {0}: - - - - Target "{0}" in file "{1}": - Target "{0}" in file "{1}": - - - - Target {0} from project "{1}": - Target {0} from project "{1}": - - - - Target "{0}" in file "{1}" from project "{2}": - Target "{0}" in file "{1}" from project "{2}": - - - - Added Item(s): - Added Item(s): - - - - Removed Item(s): - Removed Item(s): - - - - Set Property: {0}={1} - Set Property: {0}={1} - - - - Output Item(s): - Output Item(s): - - - - Output Property: {0}={1} - Output Property: {0}={1} - - - - Build continuing because "{0}" on the task "{1}" is set to "{2}". - Build continuing because "{0}" on the task "{1}" is set to "{2}". - - - - MSB4060: The "{0}" task has been declared or used incorrectly, or failed during construction. Check the spelling of the task name and the assembly name. - MSB4060: The "{0}" task has been declared or used incorrectly, or failed during construction. Check the spelling of the task name and the assembly name. - {StrBegin="MSB4060: "} - - - MSB4214: The "{0}" task has been defined, but cannot be used due to the fact that the identity defined in the UsingTask declaration (Runtime="{1}", Architecture="{2}") does not match the identity specified by the task invocation (MSBuildRuntime="{3}", MSBuildArchitecture="{4}"). - MSB4214: The "{0}" task has been defined, but cannot be used due to the fact that the identity defined in the UsingTask declaration (Runtime="{1}", Architecture="{2}") does not match the identity specified by the task invocation (MSBuildRuntime="{3}", MSBuildArchitecture="{4}"). - {StrBegin="MSB4214: "}LOCALIZATION: Runtime, Architecture, MSBuildRuntime, and MSBuildArchitecture should not be localized. - - - Done executing task "{0}" -- FAILED. - Done executing task "{0}" -- FAILED. - - - - Done executing task "{0}". - Done executing task "{0}". - - - - {0} (TaskId:{1}) - {0} (TaskId:{1}) - - - - Using "{0}" task from assembly "{1}". - Using "{0}" task from assembly "{1}". - UE: This informational message helps users determine which assemblies their tasks were loaded from. - - - Using "{0}" task from the task factory "{1}". - Using "{0}" task from the task factory "{1}". - UE: This informational message helps users determine which assemblies their tasks were loaded from. - - - Task "{0}" will be run in a single-threaded apartment thread. - Task "{0}" will be run in a single-threaded apartment thread. - UE: This informational message helps users determine if their tasks are run in the STA or MTA. - - - MSB4061: The "{0}" task could not be instantiated from "{1}". {2} - MSB4061: The "{0}" task could not be instantiated from "{1}". {2} - {StrBegin="MSB4061: "}LOCALIZATION: "{2}" is a localized message from a CLR/FX exception. - - - MSB4127: The "{0}" task could not be instantiated from the assembly "{1}". Please verify the task assembly has been built using the same version of the Microsoft.Build.Framework assembly as the one installed on your computer and that your host application is not missing a binding redirect for Microsoft.Build.Framework. {2} - MSB4127: The "{0}" task could not be instantiated from the assembly "{1}". Please verify the task assembly has been built using the same version of the Microsoft.Build.Framework assembly as the one installed on your computer and that your host application is not missing a binding redirect for Microsoft.Build.Framework. {2} - {StrBegin="MSB4127: "}UE: This message is a specialized version of the TaskInstantiationFailureError message and can probably reuse some of its docs. - LOCALIZATION: "{2}" is a localized message from a CLR/FX exception. Also, Microsoft.Build.Framework should not be localized - - - MSB4180: The "{0}" logger could not be instantiated from the assembly "{1}". Please verify the logger assembly has been built using the same version of the Microsoft.Build.Framework assembly as the one installed on your computer and that your host application is not missing a binding redirect for Microsoft.Build.Framework. {2} - MSB4180: The "{0}" logger could not be instantiated from the assembly "{1}". Please verify the logger assembly has been built using the same version of the Microsoft.Build.Framework assembly as the one installed on your computer and that your host application is not missing a binding redirect for Microsoft.Build.Framework. {2} - - {StrBegin="MSB4180: "} - LOCALIZATION: "{2}" is a localized message from a CLR/FX exception. Also, Microsoft.Build.Framework should not be localized - - - - MSB1021: Cannot create an instance of the logger. {0} - MSB1021: Cannot create an instance of the logger. {0} - {StrBegin="MSB1021: "} - UE: This error is shown when a logger cannot be loaded and instantiated from its assembly. - LOCALIZATION: The prefix "MSBxxxx: " should not be localized. {0} contains a message explaining why the - logger could not be created -- this message comes from the CLR/FX and is localized. - - - MSB1020: The logger was not found. Check the following: 1.) The logger name specified is the same as the name of the logger class. 2.) The logger class is "public" and implements the Microsoft.Build.Framework.ILogger interface. 3.) The path to the logger assembly is correct, or the logger can be loaded using only the assembly name provided. - MSB1020: The logger was not found. Check the following: 1.) The logger name specified is the same as the name of the logger class. 2.) The logger class is "public" and implements the Microsoft.Build.Framework.ILogger interface. 3.) The path to the logger assembly is correct, or the logger can be loaded using only the assembly name provided. - - {StrBegin="MSB1020: "}UE: This message does not need in-line parameters because the exception takes care of displaying the invalid arg. - This error is shown when a user specifies an logger that does not exist e.g. "msbuild /logger:FooLoggerClass,FooAssembly". The - logger class must exist in the given assembly. - LOCALIZATION: The prefix "MSBxxxx: " should not be localized. - - - - MSB4179: The task factory instance for the "{0}" task could not be instantiated from the task factory "{1}". {2} - MSB4179: The task factory instance for the "{0}" task could not be instantiated from the task factory "{1}". {2} - {StrBegin="MSB4179: "} - LOCALIZATION: "{2}" is a localized message from a CLR/FX exception. - - - MSB4176: The "{0}" task factory could not be instantiated from the assembly "{1}". Please verify the task assembly has been built using the same version of the Microsoft.Build.Framework assembly as the one installed on your computer and that your host application is not missing a binding redirect for Microsoft.Build.Framework. {2} - MSB4176: The "{0}" task factory could not be instantiated from the assembly "{1}". Please verify the task assembly has been built using the same version of the Microsoft.Build.Framework assembly as the one installed on your computer and that your host application is not missing a binding redirect for Microsoft.Build.Framework. {2} - {StrBegin="MSB4176: "}UE: This message is a specialized version of the TaskFactoryInstantiationFailureError message and can probably reuse some of its docs. - LOCALIZATION: "{2}" is a localized message from a CLR/FX exception. Also, Microsoft.Build.Framework should not be localized - - - MSB4219: The TaskFactory "{0}" does not implement ITaskFactory2. The attributes "{1}" and/or "{2}" on the UsingTask declaration for task "{3}" will be be ignored. - MSB4219: The TaskFactory "{0}" does not implement ITaskFactory2. The attributes "{1}" and/or "{2}" on the UsingTask declaration for task "{3}" will be be ignored. - {StrBegin="MSB4219: "} - LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized. - - - - The task factory must return a value for the "TaskType" property. - The task factory must return a value for the "TaskType" property. - - - - MSB4062: The "{0}" task could not be loaded from the assembly {1}. {2} Confirm that the <UsingTask> declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask. - MSB4062: The "{0}" task could not be loaded from the assembly {1}. {2} Confirm that the <UsingTask> declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask. - {StrBegin="MSB4062: "}UE: This message is shown when a task cannot be loaded from its assembly for various reasons e.g. corrupt assembly, - invalid task declaration, disk error, etc. "{2}" contains a message explaining what happened. - LOCALIZATION: "{2}" is a message from the CLR loader and is already localized. Also, <UsingTask> should not be localized. - - - MSB4215: The "{0}" task could not be loaded. "{1}" is an invalid value for the task host parameter "{2}". Valid values are: "{3}", "{4}", "{5}", and "{6}"; not specifying a value is also valid. - MSB4215: The "{0}" task could not be loaded. "{1}" is an invalid value for the task host parameter "{2}". Valid values are: "{3}", "{4}", "{5}", and "{6}"; not specifying a value is also valid. - {StrBegin="MSB4215: "} - - - "{0}" is an invalid value for the task host parameter "{1}". Valid values are: "{2}", "{3}", "{4}", and "{5}"; not specifying a value is also valid. - "{0}" is an invalid value for the task host parameter "{1}". Valid values are: "{2}", "{3}", "{4}", and "{5}"; not specifying a value is also valid. - - - - MSB4216: Could not run the "{0}" task because MSBuild could not create or connect to a task host with runtime "{1}" and architecture "{2}". Please ensure that (1) the requested runtime and/or architecture are available on the machine, and (2) that the required executable "{3}" exists and can be run. - MSB4216: Could not run the "{0}" task because MSBuild could not create or connect to a task host with runtime "{1}" and architecture "{2}". Please ensure that (1) the requested runtime and/or architecture are available on the machine, and (2) that the required executable "{3}" exists and can be run. - {StrBegin="MSB4216: "} - - - MSB4221: Could not run the "{0}" task because MSBuild could not create or connect to a task host with runtime "{1}" and architecture "{2}". Please ensure that (1) the requested runtime and/or architecture are available on the machine, and (2) that the required executable "{3}" exists and can be run. Error {4} {5}. - MSB4221: Could not run the "{0}" task because MSBuild could not create or connect to a task host with runtime "{1}" and architecture "{2}". Please ensure that (1) the requested runtime and/or architecture are available on the machine, and (2) that the required executable "{3}" exists and can be run. Error {4} {5}. - {StrBegin="MSB4221: "} - - - A task requested launch of the .NET 3.5 version of the MSBuild task host, but .NET 3.5 is not installed on this machine so the task host could not be launched. To fix this error, please either install .NET 3.5 or retarget your project. - A task requested launch of the .NET 3.5 version of the MSBuild task host, but .NET 3.5 is not installed on this machine so the task host could not be launched. To fix this error, please either install .NET 3.5 or retarget your project. - - - - MSB4217: Task host node exited prematurely. Diagnostic information may be found in files in the temporary files directory named MSBuild_*.failure.txt. {0} - MSB4217: Task host node exited prematurely. Diagnostic information may be found in files in the temporary files directory named MSBuild_*.failure.txt. {0} - {StrBegin="MSB4217: "} - - - MSB4063: The "{0}" task could not be initialized with its input parameters. {1} - MSB4063: The "{0}" task could not be initialized with its input parameters. {1} - {StrBegin="MSB4063: "} - - - Task Parameter: - Task Parameter: - - - - Task Performance Summary: - Task Performance Summary: - - - - Project Evaluation Performance Summary: - Project Evaluation Performance Summary: - - - - Task "{0}" skipped, due to false condition; ({1}) was evaluated as ({2}). - Task "{0}" skipped, due to false condition; ({1}) was evaluated as ({2}). - - - - Task "{0}" - Task "{0}" - - - - Time Elapsed {0} - Time Elapsed {0} - - - - Building with tools version "{0}". - Building with tools version "{0}". - - - - Project file contains ToolsVersion="{0}". This toolset may be unknown or missing, in which case you may be able to resolve this by installing the appropriate version of MSBuild, or the build may have been forced to a particular ToolsVersion for policy reasons. Treating the project as if it had ToolsVersion="{1}". For more information, please see http://go.microsoft.com/fwlink/?LinkId=293424. - Project file contains ToolsVersion="{0}". This toolset may be unknown or missing, in which case you may be able to resolve this by installing the appropriate version of MSBuild, or the build may have been forced to a particular ToolsVersion for policy reasons. Treating the project as if it had ToolsVersion="{1}". For more information, please see http://go.microsoft.com/fwlink/?LinkId=293424. - - - - Deferred Messages - Deferred Messages - - - - MSB4090: Found an unexpected character '{2}' at position {1} in condition "{0}". - MSB4090: Found an unexpected character '{2}' at position {1} in condition "{0}". - {StrBegin="MSB4090: "} - - - MSB4091: Found a call to an undefined function "{1}" in condition "{0}". - MSB4091: Found a call to an undefined function "{1}" in condition "{0}". - {StrBegin="MSB4091: "} - - - MSB4064: The "{0}" parameter is not supported by the "{1}" task loaded from assembly: {2} from the path: {3}. Verify that the parameter exists on the task, the <UsingTask> points to the correct assembly, and it is a settable public instance property. - MSB4064: The "{0}" parameter is not supported by the "{1}" task loaded from assembly: {2} from the path: {3}. Verify that the parameter exists on the task, the <UsingTask> points to the correct assembly, and it is a settable public instance property. - {StrBegin="MSB4064: "} - - - MSB4131: The "{0}" parameter is not supported by the "{1}" task. Verify the parameter exists on the task, and it is a gettable public instance property. - MSB4131: The "{0}" parameter is not supported by the "{1}" task. Verify the parameter exists on the task, and it is a gettable public instance property. - {StrBegin="MSB4131: "} - - - MSB4092: An unexpected token "{1}" was found at character position {2} in condition "{0}". - MSB4092: An unexpected token "{1}" was found at character position {2} in condition "{0}". - {StrBegin="MSB4092: "} - - - MSB4065: The "{0}" parameter is not marked for output by the "{1}" task. - MSB4065: The "{0}" parameter is not marked for output by the "{1}" task. - {StrBegin="MSB4065: "} - - - MSB4066: The attribute "{0}" in element <{1}> is unrecognized. - MSB4066: The attribute "{0}" in element <{1}> is unrecognized. - {StrBegin="MSB4066: "} - - - MSB4067: The element <{0}> beneath element <{1}> is unrecognized. - MSB4067: The element <{0}> beneath element <{1}> is unrecognized. - {StrBegin="MSB4067: "} - - - MSB4173: The element <{0}> beneath element <{1}> is invalid because a child element with that name already exists - MSB4173: The element <{0}> beneath element <{1}> is invalid because a child element with that name already exists - {StrBegin="MSB4173: "} - - - MSB4227: The attribute "{0}" on element <{1}> is invalid because an attribute with that name already exists - MSB4227: The attribute "{0}" on element <{1}> is invalid because an attribute with that name already exists - {StrBegin="MSB4227: "} - - - MSB4228: The name "{0}" is not valid for metadata expressed as an attribute (on element <{1}>) - MSB4228: The name "{0}" is not valid for metadata expressed as an attribute (on element <{1}>) - {StrBegin="MSB4228: "} - - - MSB4229: The value "{0}" is not valid for an Sdk specification. The attribute should be a semicolon-delimited list of Sdk-name/minimum-version pairs, separated by a forward slash. - MSB4229: The value "{0}" is not valid for an Sdk specification. The attribute should be a semicolon-delimited list of Sdk-name/minimum-version pairs, separated by a forward slash. - {StrBegin="MSB4229: "} - - - MSB4236: The SDK '{0}' specified could not be found. - MSB4236: The SDK '{0}' specified could not be found. - {StrBegin="MSB4236: "} - - - MSB4237: The SDK resolver type "{0}" failed to load. {1} - MSB4237: The SDK resolver type "{0}" failed to load. {1} - {StrBegin="MSB4237: "} - - - MSB4238: The name "{0}" is not a valid SDK name. - MSB4238: The name "{0}" is not a valid SDK name. - {StrBegin="MSB4238: "} - - - MSB4189: <{1}> is not a valid child of the <{0}> element. - MSB4189: <{1}> is not a valid child of the <{0}> element. - {StrBegin="MSB4189: "} - - - MSB4068: The element <{0}> is unrecognized, or not supported in this context. - MSB4068: The element <{0}> is unrecognized, or not supported in this context. - {StrBegin="MSB4068: "} - - - MSB4235: The log file format version is {0}, whereas this version of MSBuild only supports versions up to {1}. - MSB4235: The log file format version is {0}, whereas this version of MSBuild only supports versions up to {1}. - {StrBegin="MSB4235: "} - - - MSB4069: The "{0}" type of the "{1}" parameter of the "{2}" task is not supported by MSBuild. - MSB4069: The "{0}" type of the "{1}" parameter of the "{2}" task is not supported by MSBuild. - {StrBegin="MSB4069: "}LOCALIZATION: "MSBuild" should not be localized. - - - MSB4072: A <{0}> element must contain either the "{1}" attribute or the "{2}" attribute (but not both). - MSB4072: A <{0}> element must contain either the "{1}" attribute or the "{2}" attribute (but not both). - {StrBegin="MSB4072: "} - - - {0} Warning(s) - {0} Warning(s) - - - - MSB4084: A <When> element may not follow an <Otherwise> element in a <Choose>. - MSB4084: A <When> element may not follow an <Otherwise> element in a <Choose>. - {StrBegin="MSB4084: "} - - - MSB4150: Must initialize the console logger using the initialize method before using ApplyParameter - MSB4150: Must initialize the console logger using the initialize method before using ApplyParameter - {StrBegin="MSB4150: "} - - - MSB4206: A non-null host object cannot be specified for a project which has an affinity set to out-of-process. - MSB4206: A non-null host object cannot be specified for a project which has an affinity set to out-of-process. - {StrBegin="MSB4206: "} - - - MSB4207: Only an in-process affinity may be specified for projects which have registered host objects. - MSB4207: Only an in-process affinity may be specified for projects which have registered host objects. - {StrBegin="MSB4207: "} - - - MSB4209: The specified project instance conflicts with the affinity specified in the HostServices. - MSB4209: The specified project instance conflicts with the affinity specified in the HostServices. - {StrBegin="MSB4209: "} - - - MSB4213: The specified request affinity {0} conflicts with a previous affinity {1} specified for this project. - MSB4213: The specified request affinity {0} conflicts with a previous affinity {1} specified for this project. - {StrBegin="MSB4213: "} - - - MSB4223: A node of the required type {0} could not be created. - MSB4223: A node of the required type {0} could not be created. - {StrBegin="MSB4223: "} - - - MSB4224: KeepMetadata and RemoveMetadata are mutually exclusive. - MSB4224: KeepMetadata and RemoveMetadata are mutually exclusive. - {StrBegin="MSB4224: "} - - - "{0}" ({1} target) ({2}) -> - "{0}" ({1} target) ({2}) -> - - - - "{0}" (default target) ({1}) -> - "{0}" (default target) ({1}) -> - - - - {0} {1,5} - {0} {1,5} - - - - Project "{0}" on node {1} ({2} target(s)). - Project "{0}" on node {1} ({2} target(s)). - - - - Project "{0}" on node {1} (default targets). - Project "{0}" on node {1} (default targets). - - - - Project "{0}" ({1}) is building "{2}" ({3}) on node {4} ({5} target(s)). - Project "{0}" ({1}) is building "{2}" ({3}) on node {4} ({5} target(s)). - - - - Project "{0}" ({1}) is building "{2}" ({3}) on node {4} (default targets). - Project "{0}" ({1}) is building "{2}" ({3}) on node {4} (default targets). - - - - ({0} target) -> - ({0} target) -> - - - - The property "{0}" with value "{1}" is being overridden by another batch. The property is now: "{2}" - The property "{0}" with value "{1}" is being overridden by another batch. The property is now: "{2}" - - - - Writing build results caches to: {0} - Writing build results caches to: {0} - - LOCALIZATION: {0} is a file path - - - - The log file path cannot be null or empty. - The log file path cannot be null or empty. - - - - [default] - [default] - - - - MSB4174: The task factory "{0}" could not be found in the assembly "{1}". - MSB4174: The task factory "{0}" could not be found in the assembly "{1}". - {StrBegin="MSB4174: "} - - - MSB4175: The task factory "{0}" could not be loaded from the assembly "{1}". {2} - MSB4175: The task factory "{0}" could not be loaded from the assembly "{1}". {2} - {StrBegin="MSB4175: "} - - - MSB4201: The cancel operation was unable to complete because the currently executing task is not responding. - MSB4201: The cancel operation was unable to complete because the currently executing task is not responding. - {StrBegin="MSB4201: "} - - - MSB4220: Waiting for the currently executing task "{0}" to cancel. - MSB4220: Waiting for the currently executing task "{0}" to cancel. - {StrBegin="MSB4220: "} - - - MSB4202: The request to build submission {0} cannot proceed because submission {1} is already using the main thread. - MSB4202: The request to build submission {0} cannot proceed because submission {1} is already using the main thread. - {StrBegin="MSB4202: "} - - - The request to build this submission cannot proceed because a project with the same configuration is already building. - The request to build this submission cannot proceed because a project with the same configuration is already building. - - - - Initializing task factory "{0}" from assembly "{1}". - Initializing task factory "{0}" from assembly "{1}". - - - - Initializing task host factory for task "{0}" from assembly "{1}" - Initializing task host factory for task "{0}" from assembly "{1}" - - - - The build plan could not be written. Check that the build process has permissions to write to {0}. - The build plan could not be written. Check that the build process has permissions to write to {0}. - - - - The MSBuild cache file "{0}" is inaccessible. Ensure you have access to the directory and that this file is not deleted during the build. {1} - The MSBuild cache file "{0}" is inaccessible. Ensure you have access to the directory and that this file is not deleted during the build. {1} - - LOCALIZATION: "{1}" is a localized message from a CLR/FX exception. - - - - The build plan could not be read. Check that the build process has permissions to read {0}. - The build plan could not be read. Check that the build process has permissions to read {0}. - - - - The build plan at {0} appears to be corrupt and cannot be used. - The build plan at {0} appears to be corrupt and cannot be used. - - - - -Detailed Build Summary -====================== - - -Detailed Build Summary -====================== - - - - - -============================== Build Hierarchy (IDs represent configurations) ===================================================== -Id : Exclusive Time Total Time Path (Targets) ------------------------------------------------------------------------------------------------------------------------------------ - -============================== Build Hierarchy (IDs represent configurations) ===================================================== -Id : Exclusive Time Total Time Path (Targets) ------------------------------------------------------------------------------------------------------------------------------------ - - - - {0}{1,-3}{2}: {3:0.000}s {4:0.000}s {5} ({6}) - {0}{1,-3}{2}: {3:0.000}s {4:0.000}s {5} ({6}) - Fields 3 and 4 represent seconds, and the 's' following them should reflect the localized abbreviation for seconds. - - - -============================== Node Utilization (IDs represent configurations) ==================================================== -Timestamp: {0} Duration Cumulative ------------------------------------------------------------------------------------------------------------------------------------ - -============================== Node Utilization (IDs represent configurations) ==================================================== -Timestamp: {0} Duration Cumulative ------------------------------------------------------------------------------------------------------------------------------------ - Spacing is important. Preserve the number of characters between the start of each word. - - - {0} {1:0.000}s {2:0.000}s {3} - {0} {1:0.000}s {2:0.000}s {3} - Fields 1 and 2 represents seconds, and the 's' following it should reflect the localized abbreviation for seconds. - - - ----------------------------------------------------------------------------------------------------------------------------------- -Utilization: {0} Average Utilization: {1:###.0} - ----------------------------------------------------------------------------------------------------------------------------------- -Utilization: {0} Average Utilization: {1:###.0} - Spacing is important. Preserve the number of characters between the start of each word. - - - This collection cannot convert from the specified value to the backing value. - This collection cannot convert from the specified value to the backing value. - - - - The "{0}" property name is reserved. - The "{0}" property name is reserved. - UE: This message is shown when the user tries to redefine one of the reserved MSBuild properties e.g. $(MSBuildProjectFile) through the object model - - - The <{0}> element must have either the "{1}" attribute or the "{2}" attribute but not both. - The <{0}> element must have either the "{1}" attribute or the "{2}" attribute but not both. - - - - The <{0}> element must have either the "{1}" attribute, the "{2}" attribute, or the "{3}" attribute, but not more than one. - The <{0}> element must have either the "{1}" attribute, the "{2}" attribute, or the "{3}" attribute, but not more than one. - - - - The "Remove" attribute is not permitted on an item outside of a <Target>. - The "Remove" attribute is not permitted on an item outside of a <Target>. - - - - The "KeepMetadata" attribute is not permitted on an item outside of a <Target>. - The "KeepMetadata" attribute is not permitted on an item outside of a <Target>. - - - - The "RemoveMetadata" attribute is not permitted on an item outside of a <Target>. - The "RemoveMetadata" attribute is not permitted on an item outside of a <Target>. - - - - The "KeepDuplicates" attribute is not permitted on an item outside of a <Target>. - The "KeepDuplicates" attribute is not permitted on an item outside of a <Target>. - - - - Elements of this type do not have a condition. - Elements of this type do not have a condition. - For example, it is not legal for a <ProjectExtensions> element to have a condition attribute. - - - The node already has a parent. Remove it from its parent before moving it. - The node already has a parent. Remove it from its parent before moving it. - - - - The node is not parented by this object so it cannot be removed from it. - The node is not parented by this object so it cannot be removed from it. - - - - The reference node is not a child of this node. - The reference node is not a child of this node. - - - - Cannot make a node or an ancestor of that node a child of itself. - Cannot make a node or an ancestor of that node a child of itself. - - - - Cannot create a relationship between nodes that were created from different projects. - Cannot create a relationship between nodes that were created from different projects. - - - - The parent node is not itself parented. - The parent node is not itself parented. - - - - This parent is not a valid parent for the item. - This parent is not a valid parent for the item. - - - - An item not parented under a Target must have a value for Include or Update or Remove. - An item not parented under a Target must have a value for Include or Update or Remove. - LOCALIZATION: Please do not localize "Target", "Include", "Update", and "Remove". - - - The name "{0}" contains an invalid character "{1}". - The name "{0}" contains an invalid character "{1}". - - - - An <Otherwise> element cannot be located before a <When> or <Otherwise> element. - An <Otherwise> element cannot be located before a <When> or <Otherwise> element. - - - - Project has not been given a path to save to. - Project has not been given a path to save to. - - - - Project was not loaded with the ProjectLoadSettings.RecordDuplicateImports flag. - Project was not loaded with the ProjectLoadSettings.RecordDuplicateImports flag. - - - - Project or targets file "{0}" was loaded in read-only mode, and cannot be saved. - Project or targets file "{0}" was loaded in read-only mode, and cannot be saved. - - - - The "{0}" object specified does not belong to the correct "{1}" object. - The "{0}" object specified does not belong to the correct "{1}" object. - - - - The "{0}" name is reserved, and cannot be used. - The "{0}" name is reserved, and cannot be used. - - - - The "{0}" property is a global property, and cannot be modified. - The "{0}" property is a global property, and cannot be modified. - - - - An equivalent project (a project with the same global properties and tools version) is already present in the project collection, with the path "{0}". To load an equivalent into this project collection, unload this project first. - An equivalent project (a project with the same global properties and tools version) is already present in the project collection, with the path "{0}". To load an equivalent into this project collection, unload this project first. - - - - The project provided was not loaded in the collection. - The project provided was not loaded in the collection. - - - - Cannot modify an evaluated object originating in an imported file "{0}". - Cannot modify an evaluated object originating in an imported file "{0}". - - - - Cannot remove the metadata named "{0}" as it originates from an item definition, rather than being directly defined on this item. - Cannot remove the metadata named "{0}" as it originates from an item definition, rather than being directly defined on this item. - - - - The requested operation needs to split the item element at location {0} into individual elements but item element splitting is disabled with {1}. - The requested operation needs to split the item element at location {0} into individual elements but item element splitting is disabled with {1}. - - - - The project cannot be used as it is no longer loaded into a project collection. - The project cannot be used as it is no longer loaded into a project collection. - - - - The operation is not allowed because currently this object is not parented. - The operation is not allowed because currently this object is not parented. - - - - The project XML file "{0}" cannot be unloaded because at least one project "{1}" is still loaded which references that project XML. - The project XML file "{0}" cannot be unloaded because at least one project "{1}" is still loaded which references that project XML. - - - - Instance object was created as immutable. - Instance object was created as immutable. - - - - The specified API "{0}" is not available because ProjectLoadSettings.DoNotEvaluateElementsWithFalseCondition was set when loading this project. - The specified API "{0}" is not available because ProjectLoadSettings.DoNotEvaluateElementsWithFalseCondition was set when loading this project. - - - - All build submissions in a build must use project instances originating from the same project collection. - All build submissions in a build must use project instances originating from the same project collection. - This occurs if a client tries to add two BuildSubmissions to a build, each involving a ProjectInstance originating in different ProjectCollection. This is not allowed. - - - Build started. - Build started. - - - - {0} ({1},{2}) - {0} ({1},{2}) - A file location to be embedded in a string. - - - MSB3203: The output path "{0}" cannot be rebased. {1} - MSB3203: The output path "{0}" cannot be rebased. {1} - {StrBegin="MSB3203: "}UE: This message is shown when the user asks the "MSBuild" task to rebase the paths of its output items relative to the project from where the "MSBuild" task is called (as opposed to the project(s) on which the "MSBuild" task is called), and one of the output item paths is invalid. LOCALIZATION: "{1}" is a localized message from a CLR/FX exception explaining the problem. - - - MSB3202: The project file "{0}" was not found. - MSB3202: The project file "{0}" was not found. - - {StrBegin="MSB3202: "}UE: This message is shown when the user passes a non-existent project file to the MSBuild task, in the "Projects" parameter. - and they have not specified the SkipNonexistentProjects parameter, or it is set to false. - - - - Skipping project "{0}" because it was not found. - Skipping project "{0}" because it was not found. - UE: This message is shown when the user passes a non-existent project file to the MSBuild task, in the "Projects" parameter, and they have specified the SkipNonexistentProjects parameter. - - - MSB3204: The project file "{0}" is in the ".vcproj" file format, which MSBuild no longer supports. Please convert the project by opening it in the Visual Studio IDE or running the conversion tool, or use MSBuild 3.5 or earlier to build it. - MSB3204: The project file "{0}" is in the ".vcproj" file format, which MSBuild no longer supports. Please convert the project by opening it in the Visual Studio IDE or running the conversion tool, or use MSBuild 3.5 or earlier to build it. - {StrBegin="MSB3204: "} LOC: ".vcproj" should not be localized - - - MSB3205: SkipNonexistentProject can only accept values of "True", "False" and "Build". - MSB3205: SkipNonexistentProject can only accept values of "True", "False" and "Build". - {StrBegin="MSB3205: "} LOC: "SkipNonexistentProject", "True", "False" and "Build" should not be localized - - - The MSBuild task is skipping the remaining projects because the StopOnFirstFailure parameter was set to true. - The MSBuild task is skipping the remaining projects because the StopOnFirstFailure parameter was set to true. - LOCALIZATION: Do not localize the words "MSBuild" or "StopOnFirstFailure". - - - The MSBuild task is skipping the remaining targets because the StopOnFirstFailure parameter was set to true. - The MSBuild task is skipping the remaining targets because the StopOnFirstFailure parameter was set to true. - LOCALIZATION: Do not localize the words "MSBuild" or "StopOnFirstFailure". - - - Overriding the BuildingInParallel property by setting it to false. This is due to the system being run in single process mode with StopOnFirstFailure set to true. - Overriding the BuildingInParallel property by setting it to false. This is due to the system being run in single process mode with StopOnFirstFailure set to true. - LOCALIZATION: Do not localize the words "MSBuild", "BuildingInParallel", or "StopOnFirstFailure". - - - StopOnFirstFailure will have no effect when the following conditions are all present: 1) The system is running in multiple process mode 2) The BuildInParallel property is true. 3) The RunEachTargetSeparately property is false. - StopOnFirstFailure will have no effect when the following conditions are all present: 1) The system is running in multiple process mode 2) The BuildInParallel property is true. 3) The RunEachTargetSeparately property is false. - LOCALIZATION: Do not localize the words "RunEachTargetSeparately", "BuildingInParallel", or "StopOnFirstFailure". - - - MSB3100: Syntax for "{0}" parameter is not valid ({1}). Correct syntax is {0}="<name>=<value>". - MSB3100: Syntax for "{0}" parameter is not valid ({1}). Correct syntax is {0}="<name>=<value>". - {StrBegin="MSB3100: "}This error is shown if the user does any of the following: - Properties="foo" (missing property value) - Properties="=4" (missing property name) - The user must pass in an actual property name and value, as in Properties="Configuration=Debug". - - - Global Properties: - Global Properties: - - - - Removing Properties: - Removing Properties: - - - - Overriding Global Properties for project "{0}" with: - Overriding Global Properties for project "{0}" with: - - - - Additional Properties for project "{0}": - Additional Properties for project "{0}": - - - - Removing Properties for project "{0}": - Removing Properties for project "{0}": - - - - MSB4802: The "{0}" task could not be instantiated from "{1}". This version of MSBuild does not support {2}. - MSB4802: The "{0}" task could not be instantiated from "{1}". This version of MSBuild does not support {2}. - {StrBegin="MSB4802: "} - - - The parameter '{0}' can only be a file name and cannot include a directory. - The parameter '{0}' can only be a file name and cannot include a directory. - - - - MSB4229: File to reload from does not exist: {0} - MSB4229: File to reload from does not exist: {0} - {StrBegin="MSB4229: "} - - - MSB4230: Value not set: {0} - MSB4230: Value not set: {0} - {StrBegin="MSB4230: "} - - - MSB4231: ProjectRootElement can't reload if it contains unsaved changes. - MSB4231: ProjectRootElement can't reload if it contains unsaved changes. - {StrBegin="MSB4231: "} - - - Project "{0}" was not imported by "{1}" at ({2},{3}), due to false condition; ({4}) was evaluated as ({5}). - Project "{0}" was not imported by "{1}" at ({2},{3}), due to false condition; ({4}) was evaluated as ({5}). - - - - Project "{0}" was not imported by "{1}" at ({2},{3}), due to no matching files. - Project "{0}" was not imported by "{1}" at ({2},{3}), due to no matching files. - - - - Project "{0}" was not imported by "{1}" at ({2},{3}), due to the file being empty. - Project "{0}" was not imported by "{1}" at ({2},{3}), due to the file being empty. - - - - Project "{0}" was not imported by "{1}" at ({2},{3}), due to the file being invalid. - Project "{0}" was not imported by "{1}" at ({2},{3}), due to the file being invalid. - - - - Project "{0}" was not imported by "{1}" at ({2},{3}), due to the file not existing. - Project "{0}" was not imported by "{1}" at ({2},{3}), due to the file not existing. - - - - Importing project "{0}" into project "{1}" at ({2},{3}). - Importing project "{0}" into project "{1}" at ({2},{3}). - - - - MSBUILD : error MSB4239: Error writing profiling report. {0} - MSBUILD : error MSB4239: Error writing profiling report. {0} - - - - Writing profiler report to '{0}'... - Writing profiler report to '{0}'... - - - - Done writing report. - Done writing report. - - - - MSB4242: The SDK resolver "{0}" failed to run. {1} - MSB4242: The SDK resolver "{0}" failed to run. {1} - {StrBegin="MSB4242: "} - - - MSB4243: The NuGet-based SDK resolver failed to run because NuGet assemblies could not be located. Check your installation of MSBuild or set the environment variable "{0}" to the folder that contains the required NuGet assemblies. {1} - MSB4243: The NuGet-based SDK resolver failed to run because NuGet assemblies could not be located. Check your installation of MSBuild or set the environment variable "{0}" to the folder that contains the required NuGet assemblies. {1} - {StrBegin="MSB4243: "} - - - MSB4240: Multiple versions of the same SDK "{0}" cannot be specified. The previously resolved SDK version "{1}" from location "{2}" will be used and the version "{3}" will be ignored. - MSB4240: Multiple versions of the same SDK "{0}" cannot be specified. The previously resolved SDK version "{1}" from location "{2}" will be used and the version "{3}" will be ignored. - {StrBegin="MSB4240: "} - LOCALIZATION: Do not localize the word SDK. - - - - MSB4241: The SDK reference "{0}" version "{1}" was resolved to version "{2}" instead. You could be using a different version than expected if you do not update the referenced version to match. - MSB4241: The SDK reference "{0}" version "{1}" was resolved to version "{2}" instead. You could be using a different version than expected if you do not update the referenced version to match. - {StrBegin="MSB4241: "} - LOCALIZATION: Do not localize the word SDK. - - - - Resolving SDK '{0}'... - Resolving SDK '{0}'... - - LOCALIZATION: Do not localize the word SDK. - - - - MSB4244: The SDK resolver assembly "{0}" could not be loaded. {1} - MSB4244: The SDK resolver assembly "{0}" could not be loaded. {1} - {StrBegin="MSB4244: "} - - - MSB4245: SDK Resolver manifest file is invalid. This may indicate a corrupt or invalid installation of MSBuild. Manifest file path '{0}'. Message: {1} - MSB4245: SDK Resolver manifest file is invalid. This may indicate a corrupt or invalid installation of MSBuild. Manifest file path '{0}'. Message: {1} - {StrBegin="MSB4245: "} - - - MSB4246: SDK Resolver folder exists but without an SDK Resolver DLL or manifest file. This may indicate a corrupt or invalid installation of MSBuild. SDK resolver path: {0} - MSB4246: SDK Resolver folder exists but without an SDK Resolver DLL or manifest file. This may indicate a corrupt or invalid installation of MSBuild. SDK resolver path: {0} - {StrBegin="MSB4246: "} - - - MSB4247: Could not load SDK Resolver. A manifest file exists, but the path to the SDK Resolver DLL file could not be found. Manifest file path '{0}'. SDK resolver path: {1} - MSB4247: Could not load SDK Resolver. A manifest file exists, but the path to the SDK Resolver DLL file could not be found. Manifest file path '{0}'. SDK resolver path: {1} - {StrBegin="MSB4247: "} - - - - \ No newline at end of file diff --git a/src/Deprecated/Conversion/Resources/xlf/Strings.en.xlf b/src/Deprecated/Conversion/Resources/xlf/Strings.en.xlf deleted file mode 100644 index 73f4ab526f7..00000000000 --- a/src/Deprecated/Conversion/Resources/xlf/Strings.en.xlf +++ /dev/null @@ -1,87 +0,0 @@ - - - - - - MSB2013: The project-to-project reference with GUID {0} could not be converted because a valid .SLN file containing all projects could not be found. - MSB2013: The project-to-project reference with GUID {0} could not be converted because a valid .SLN file containing all projects could not be found. - {StrBegin="MSB2013: "} - - - MSB2016: Found an empty .RESX file in the project ({0}). Removing it from the converted project. - MSB2016: Found an empty .RESX file in the project ({0}). Removing it from the converted project. - {StrBegin="MSB2016: "} - - - MSB2015: Found an <Exclude> element in the original project file. This cannot be converted to Visual Studio .NET and is being ignored. - MSB2015: Found an <Exclude> element in the original project file. This cannot be converted to Visual Studio .NET and is being ignored. - {StrBegin="MSB2015: "} - - - MSB2001: Element <{0}> does not contain the required attribute "{1}". - MSB2001: Element <{0}> does not contain the required attribute "{1}". - {StrBegin="MSB2001: "}It appears we've been asked to convert a project that either wasn't created by Visual Studio, or that has been hand-modified or corrupted. - - - MSB2002: The file name of the new project must be specified. - MSB2002: The file name of the new project must be specified. - {StrBegin="MSB2002: "}This error shouldn't be possible when converting through Visual Studio, but we have it just in case. - - - MSB2003: The file name of the old project must be specified. - MSB2003: The file name of the old project must be specified. - {StrBegin="MSB2003: "}This error shouldn't be possible when converting through Visual Studio, but we have it just in case. - - - MSB2004: Element <{0}> cannot contain more than one language node. - MSB2004: Element <{0}> cannot contain more than one language node. - {StrBegin="MSB2004: "}It appears we've been asked to convert a project that either wasn't created by Visual Studio, or that has been hand-modified or corrupted. The {0} in this case is going to be "VisualStudioProject". - - - MSB2005: Element <{0}> cannot contain attributes. - MSB2005: Element <{0}> cannot contain attributes. - {StrBegin="MSB2005: "}It appears we've been asked to convert a project that either wasn't created by Visual Studio, or that has been hand-modified or corrupted. - - - MSB2006: The project file does not contain the root element <{0}>. - MSB2006: The project file does not contain the root element <{0}>. - {StrBegin="MSB2006: "}It appears we've been asked to convert a project that either wasn't created by Visual Studio, or that has been hand-modified or corrupted. - - - MSB2007: Visual Studio cannot find the project file "{0}". - MSB2007: Visual Studio cannot find the project file "{0}". - {StrBegin="MSB2007: "}This error shouldn't be possible when converting through Visual Studio, but we have it just in case. - - - MSB2014: The project-to-project reference with GUID {0} cannot be converted because it is not listed in the file '{1}'. - MSB2014: The project-to-project reference with GUID {0} cannot be converted because it is not listed in the file '{1}'. - {StrBegin="MSB2014: "} - - - MSB2008: This Visual Studio project system cannot convert "{0}" projects. It can only be used to convert C#, VB, and VJ# client projects. - MSB2008: This Visual Studio project system cannot convert "{0}" projects. It can only be used to convert C#, VB, and VJ# client projects. - {StrBegin="MSB2008: "}It appears we've been asked to convert a project that either wasn't created by the Visual Studio managed client project system (C#, VB, J#), or that has been hand-modified or corrupted. You would get this error if this conversion utility was invoked on a VC++ project (.VCPROJ) for example. In this case, the {0} would be replaced with "Visual C++". - - - MSB2009: Attribute "{0}" of element <{1}> is not valid. - MSB2009: Attribute "{0}" of element <{1}> is not valid. - {StrBegin="MSB2009: "}It appears we've been asked to convert a project that either wasn't created by Visual Studio, or that has been hand-modified or corrupted. - - - MSB2010: Child element <{0}> of element <{1}> is not valid. - MSB2010: Child element <{0}> of element <{1}> is not valid. - {StrBegin="MSB2010: "}It appears we've been asked to convert a project that either wasn't created by Visual Studio, or that has been hand-modified or corrupted. - - - MSB2011: Element <{0}> is not valid. - MSB2011: Element <{0}> is not valid. - {StrBegin="MSB2011: "}It appears we've been asked to convert a project that either wasn't created by Visual Studio, or that has been hand-modified or corrupted. - - - MSB2012: Project-to-project references to web projects are no longer supported and therefore cannot be converted. Please remove the reference to project {0} and add it again. - MSB2012: Project-to-project references to web projects are no longer supported and therefore cannot be converted. Please remove the reference to project {0} and add it again. - {StrBegin="MSB2012: "} - - - - \ No newline at end of file diff --git a/src/Deprecated/Engine/Resources/xlf/Strings.en.xlf b/src/Deprecated/Engine/Resources/xlf/Strings.en.xlf deleted file mode 100644 index 5fdd9a1a8ef..00000000000 --- a/src/Deprecated/Engine/Resources/xlf/Strings.en.xlf +++ /dev/null @@ -1,1516 +0,0 @@ - - - - - - MSB4001: The "{0}" task has more than one parameter called "{1}". - MSB4001: The "{0}" task has more than one parameter called "{1}". - {StrBegin="MSB4001: "}UE: This message is shown when a task has more than one .NET property with the same name -- it's unclear which of - those properties the task wants to use as a parameter in project files. - - - MSB4081: The value "{0}" of the "ItemName" attribute in element <Output> contains an "@" character. If you intended to use an item name then remove the @( ) around the item name. - MSB4081: The value "{0}" of the "ItemName" attribute in element <Output> contains an "@" character. If you intended to use an item name then remove the @( ) around the item name. - {StrBegin="MSB4081: "}UE: This message is shown when an output tag has an itemname that contains an @. They probably typed @(foo) instead of foo in the ItemName.LOCALIZATION: Output and ItemName should not be localized. - - - MSB4002: There was a failure retrieving the attributes for parameters in the "{0}" task. {1} - MSB4002: There was a failure retrieving the attributes for parameters in the "{0}" task. {1} - {StrBegin="MSB4002: "}UE: This message is shown when the .NET attributes that a task's .NET properties are decorated with, cannot be - retrieved -- this is typically because the .NET classes that define the .NET attributes cannot be loaded because the assembly - they are defined in cannot be found, or the classes themselves cannot be found. - - - MSB4003: "{0}" is a reserved attribute of the <{1}> element, and must be spelled with the correct casing. This attribute cannot be used as a parameter to the "{2}" task. - MSB4003: "{0}" is a reserved attribute of the <{1}> element, and must be spelled with the correct casing. This attribute cannot be used as a parameter to the "{2}" task. - {StrBegin="MSB4003: "}UE: Tasks are not allowed to use incorrect case for reserved attributes on the task nodes e.g. "continueonerror" - instead of the "ContinueOnError". - - - The "REQUESTBATCHSIZE" must be a number greater than 1. "{0}" is an invalid value. The value 10 will be used instead. - The "REQUESTBATCHSIZE" must be a number greater than 1. "{0}" is an invalid value. The value 10 will be used instead. - The name "REQUESTBATCHSIZE" is an environment variable - - - Build completed in {0}. - Build completed in {0}. - - - - Build FAILED. - Build FAILED. - - - - Build succeeded. - Build succeeded. - - - - Build started. - Build started. - - - - Build started {0}. - Build started {0}. - - - - Building target "{0}" completely. - Building target "{0}" completely. - {0} is the name of the target. - - - No input files were specified. - No input files were specified. - - - - Input file "{0}" is newer than output file "{1}". - Input file "{0}" is newer than output file "{1}". - {0} and {1} are filenames on disk. - - - Output file "{0}" does not exist. - Output file "{0}" does not exist. - {0} is a filename on disk. - - - Input file "{0}" does not exist. - Input file "{0}" does not exist. - {0} is a filename on disk. - - - Building target "{0}" partially, because some output files are out of date with respect to their input files. - Building target "{0}" partially, because some output files are out of date with respect to their input files. - {0} is the name of the target. - - - [{0}: Input={1}, Output={2}] Input file is newer than output file. - [{0}: Input={1}, Output={2}] Input file is newer than output file. - {0} is the name of an MSBuild item. {1} and {2} are filenames on disk. - - - [{0}: Input={1}, Output={2}] Output file does not exist. - [{0}: Input={1}, Output={2}] Output file does not exist. - {0} is the name of an MSBuild item. {1} and {2} are filenames on disk. - - - [{0}: Input={1}, Output={2}] Input file does not exist. - [{0}: Input={1}, Output={2}] Input file does not exist. - {0} is the name of an MSBuild item. {1} and {2} are filenames on disk. - - - The attribute "{0}" is a known MSBuild attribute, and cannot be accessed using this method. - The attribute "{0}" is a known MSBuild attribute, and cannot be accessed using this method. - - - - Properties in persisted property groups cannot be accessed by name. - Properties in persisted property groups cannot be accessed by name. - - - - MSB4023: Cannot evaluate the item metadata "%({0})". {1} - MSB4023: Cannot evaluate the item metadata "%({0})". {1} - {StrBegin="MSB4023: "}UE: This message is shown when the value of an item metadata cannot be computed for some reason e.g. trying to apply - %(RootDir) to an item-spec that's not a valid path, would result in this error. - LOCALIZATION: "{1}" is a localized message explaining the problem. - - - Cannot execute a task not associated with a project object. - Cannot execute a task not associated with a project object. - - - - The cache entry has already been set to a different value and cannot be modified. - The cache entry has already been set to a different value and cannot be modified. - - - - The "{0}" property comes from an environment variable, and cannot be modified. - The "{0}" property comes from an environment variable, and cannot be modified. - - - - The "{0}" property is a global property, and cannot be modified through an evaluated property group. Use "{1}" instead. - The "{0}" property is a global property, and cannot be modified through an evaluated property group. Use "{1}" instead. - - - - Modifying the XML of an imported project file is not allowed. Open that project file directly. - Modifying the XML of an imported project file is not allowed. Open that project file directly. - - - - MSB4117: The "{0}" item name is reserved, and cannot be used. - MSB4117: The "{0}" item name is reserved, and cannot be used. - {StrBegin="MSB4117: "}UE: This message is shown when the user tries to redefine one of the reserved MSBuild items e.g. @(Choose) - - - MSB4118: The "{0}" item metadata name is reserved, and cannot be used. - MSB4118: The "{0}" item metadata name is reserved, and cannot be used. - {StrBegin="MSB4118: "}UE: This message is shown when the user tries to redefine one of the reserved MSBuild items e.g. @(Choose) - - - MSB4004: The "{0}" property is reserved, and cannot be modified. - MSB4004: The "{0}" property is reserved, and cannot be modified. - {StrBegin="MSB4004: "}UE: This message is shown when the user tries to redefine one of the reserved MSBuild properties e.g. $(MSBuildProjectFile) - - - MSB4094: "{0}" is an invalid value for the "{1}" parameter of the "{3}" task. Multiple items cannot be passed into a parameter of type "{2}". - MSB4094: "{0}" is an invalid value for the "{1}" parameter of the "{3}" task. Multiple items cannot be passed into a parameter of type "{2}". - {StrBegin="MSB4094: "} - UE: This error is shown when a project tries to pass multiple items into a task parameter of type ITaskItem (singular). - - - - MSB4115: The "{0}" function only accepts a scalar value, but its argument "{1}" evaluates to "{2}" which is not a scalar value. - MSB4115: The "{0}" function only accepts a scalar value, but its argument "{1}" evaluates to "{2}" which is not a scalar value. - {StrBegin="MSB4115: "} - UE: This error is shown when a project tries to pass multiple items into a function in a conditional expression, that can only accept a scalar value (such as the "exists()" function). - - - - The task is currently associated with a project object, and should not be added to a different one. - The task is currently associated with a project object, and should not be added to a different one. - - - - MSB4095: The item metadata %({0}) is being referenced without an item name. Specify the item name by using %(itemname.{0}). - MSB4095: The item metadata %({0}) is being referenced without an item name. Specify the item name by using %(itemname.{0}). - {StrBegin="MSB4095: "} - - - The task is not associated with the specified target element collection, and should not be removed from it. - The task is not associated with the specified target element collection, and should not be removed from it. - - - - MSB4005: The current working directory could not be restored to {0}. {1} - MSB4005: The current working directory could not be restored to {0}. {1} - {StrBegin="MSB4005: "}UE: This message is shown when the current working directory cannot be reset after a build. "{1}" contains a message explaining why. - LOCALIZATION: "{1}" is a message from an CLR/FX exception and is already localized. - - - Cannot set a condition on an object not represented by an XML element in the project file. - Cannot set a condition on an object not represented by an XML element in the project file. - - - - Cannot set ContinueOnError on an object not represented by an XML element in the project file. - Cannot set ContinueOnError on an object not represented by an XML element in the project file. - - - - MSB4134: DefaultToolsVersion cannot be set after a project has been loaded into the Engine. - MSB4134: DefaultToolsVersion cannot be set after a project has been loaded into the Engine. - {StrBegin="MSB4134: "} - - - Assigning the "{0}" attribute on an item that has been evaluated is not allowed. This operation is only allowed on the original persisted item that came directly from the project file. - Assigning the "{0}" attribute on an item that has been evaluated is not allowed. This operation is only allowed on the original persisted item that came directly from the project file. - - - - Assigning the "{0}" attribute of a virtual item is not allowed. - Assigning the "{0}" attribute of a virtual item is not allowed. - - - - A property cannot be set while building. - A property cannot be set while building. - - - - A property cannot be set to null. - A property cannot be set to null. - - - - Cannot get or set parameters on a task not associated with a project object. - Cannot get or set parameters on a task not associated with a project object. - - - - MSB4162: <{0}> is not valid. Child elements are not allowed below a item remove element. - MSB4162: <{0}> is not valid. Child elements are not allowed below a item remove element. - {StrBegin="MSB4162: "} - - - MSB4166: Child node "{0}" exited prematurely. Shutting down. - MSB4166: Child node "{0}" exited prematurely. Shutting down. - {StrBegin="MSB4166: "} - - - MSB4085: A <Choose> must contain at least one <When>. - MSB4085: A <Choose> must contain at least one <When>. - {StrBegin="MSB4085: "} - - - MSB4114: <Choose> elements cannot be nested more than {0} levels deep. - MSB4114: <Choose> elements cannot be nested more than {0} levels deep. - {StrBegin="MSB4114: "}UE: This message appears if the project file contains unreasonably nested Choose elements. - LOCALIZATION: Do not localize "Choose" as it is an XML element name. - - - MSB4006: There is a circular dependency in the target dependency graph involving target "{0}". - MSB4006: There is a circular dependency in the target dependency graph involving target "{0}". - {StrBegin="MSB4006: "}UE: This message is shown when the build engine detects a target referenced in a circular manner -- a project cannot - request a target to build itself (perhaps via a chain of other targets). - - - MSB4086: A numeric comparison was attempted on "{1}" that evaluates to "{2}" instead of a number, in condition "{0}". - MSB4086: A numeric comparison was attempted on "{1}" that evaluates to "{2}" instead of a number, in condition "{0}". - {StrBegin="MSB4086: "} - - - MSB4007: The clause "{0}", specified in the "{1}" attribute is invalid. - MSB4007: The clause "{0}", specified in the "{1}" attribute is invalid. - {StrBegin="MSB4007: "}UE: This message is shown when the Condition on an element is invalid in some way -- e.g. syntax error, unrecognized operator. - - - MSB4130: The condition "{0}" may have been evaluated incorrectly in an earlier version of MSBuild. Please verify that the order of the AND and OR clauses is written as intended. To avoid this warning, add parentheses to make the evaluation order explicit. - MSB4130: The condition "{0}" may have been evaluated incorrectly in an earlier version of MSBuild. Please verify that the order of the AND and OR clauses is written as intended. To avoid this warning, add parentheses to make the evaluation order explicit. - {StrBegin="MSB4130: "} - - - MSB4087: Specified condition "{0}" does not evaluate to a boolean. - MSB4087: Specified condition "{0}" does not evaluate to a boolean. - {StrBegin="MSB4087: "} - - - MSB4113: Specified condition "{0}" evaluates to "{1}" instead of a boolean. - MSB4113: Specified condition "{0}" evaluates to "{1}" instead of a boolean. - {StrBegin="MSB4113: "} - - - {0}, line {1} - {0}, line {1} - - - - MSB4136: Error reading the toolset information from the configuration file "{0}". {1} - MSB4136: Error reading the toolset information from the configuration file "{0}". {1} - {StrBegin="MSB4136: "} - - - MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{1}". - MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{1}". - {StrBegin="MSB4008: "}UE: This message is shown when the type/class of a task cannot be resolved uniquely from a single assembly. - - - MSB4142: MSBuildToolsPath is not the same as MSBuildBinPath for the ToolsVersion "{0}" defined at "{1}". If both are present they must have the same value. - MSB4142: MSBuildToolsPath is not the same as MSBuildBinPath for the ToolsVersion "{0}" defined at "{1}". If both are present they must have the same value. - {StrBegin="MSB4142: "} - - - MSB4097: The element <{0}> beneath element <{1}> may not have a custom XML namespace. - MSB4097: The element <{0}> beneath element <{1}> may not have a custom XML namespace. - {StrBegin="MSB4097: "} - - - MSB4009: The default tasks file could not be successfully loaded. {0} - MSB4009: The default tasks file could not be successfully loaded. {0} - {StrBegin="MSB4009: "}UE: This message is shown when one of the default tasks file (*.tasks) located alongside the MSBuild binaries cannot - be opened/parsed. "{0}" contains a message explaining why. The filename itself is not part of the message but is provided - separately to loggers. - LOCALIZATION: "{0}" is a message from some FX method and is already localized. - - - MSB4010: The "{0}" files could not be successfully loaded from their expected location "{1}". Default tasks will not be available. {2} - MSB4010: The "{0}" files could not be successfully loaded from their expected location "{1}". Default tasks will not be available. {2} - {StrBegin="MSB4010: "}UE: This message is shown when the default tasks files that are located alongside the MSBuild binaries cannot be - found, either because they don't exist, or because of lack of permissions. "{2}" contains a message explaining why. - LOCALIZATION: "{2}" is a message from some FX method and is already localized. - - - MSB4140: Default tools version is specified in neither the registry nor the configuration file. - MSB4140: Default tools version is specified in neither the registry nor the configuration file. - {StrBegin="MSB4140: "} - - - MSB4133: A default tools version "{0}" was specified, but its definition could not be found. - MSB4133: A default tools version "{0}" was specified, but its definition could not be found. - {StrBegin="MSB4133: "} - - - MSB4080: The value "{0}" of the "PropertyName" attribute in element <Output> contains a "$" character. If you intended to use a property name then remove the $( ) around the property name. - MSB4080: The value "{0}" of the "PropertyName" attribute in element <Output> contains a "$" character. If you intended to use a property name then remove the $( ) around the property name. - {StrBegin="MSB4080: "}UE: This message is shown when an output tag has an property name that contains an $. They probably typed $(foo) instead of foo in the PropertyName. LOCALIZATION: Output and PropertyName should not be localized. - - - MSB4011: There is a circular reference involving the import of file "{0}". This file may have been imported more than once, or you may have attempted to import the main project file. All except the first instance of this file will be ignored. - MSB4011: There is a circular reference involving the import of file "{0}". This file may have been imported more than once, or you may have attempted to import the main project file. All except the first instance of this file will be ignored. - {StrBegin="MSB4011: "} - - - MSB4079: The <ProjectExtensions> element occurs more than once. - MSB4079: The <ProjectExtensions> element occurs more than once. - {StrBegin="MSB4079: "} - - - MSB4012: The expression "{0}" cannot be used in this context. Item lists cannot be concatenated with other strings where an item list is expected. Use a semicolon to separate multiple item lists. - MSB4012: The expression "{0}" cannot be used in this context. Item lists cannot be concatenated with other strings where an item list is expected. Use a semicolon to separate multiple item lists. - {StrBegin="MSB4012: "}UE: This message is shown when the user does not properly specify an item list when an item list is expected - e.g. "badprefix@(foo)badsuffix" instead of "prefix; @(foo); suffix" - - - Need to specify the project file name. - Need to specify the project file name. - UE: This message is shown when the user calls into the engine to build a project without specifying a filename. - - - end of input - end of input - This is the name of the "EndOfInput" token. It is displayed in quotes as the - unexpected char or token when the end of a conditional was unexpectedly reached. - - - The previous error was converted to a warning because the task was called with ContinueOnError=true. - The previous error was converted to a warning because the task was called with ContinueOnError=true. - - - - {0} Error(s) - {0} Error(s) - - - - MSB4159: Error creating the toolset "{0}". {1} - MSB4159: Error creating the toolset "{0}". {1} - {StrBegin="MSB4159: "} - - - MSB4146: Cannot evaluate the property expression "{0}" found at "{1}". {2} - MSB4146: Cannot evaluate the property expression "{0}" found at "{1}". {2} - {StrBegin="MSB4146: "} - - - The <{0}> tag is no longer supported as a child of the <Project> element. Place this tag within a target, and add the name of the target to the "InitialTargets" attribute of the <Project> element. - The <{0}> tag is no longer supported as a child of the <Project> element. Place this tag within a target, and add the name of the target to the "InitialTargets" attribute of the <Project> element. - - - - MSB4100: Expected "{0}" to evaluate to a boolean instead of "{1}", in condition "{2}". - MSB4100: Expected "{0}" to evaluate to a boolean instead of "{1}", in condition "{2}". - {StrBegin="MSB4100: "} - - - MSB4028: The "{0}" task's outputs could not be retrieved from the "{1}" parameter. {2} - MSB4028: The "{0}" task's outputs could not be retrieved from the "{1}" parameter. {2} - {StrBegin="MSB4028: "} - - - MSB4014: The build was aborted because of an internal failure. - MSB4014: The build was aborted because of an internal failure. - {StrBegin="MSB4014: "}UE: This message is shown when an unhandled exception terminates the build. The cause is most likely a programming - error in the build engine. - - - MSB4015: The build was aborted because the "{0}" logger failed unexpectedly during shutdown. - MSB4015: The build was aborted because the "{0}" logger failed unexpectedly during shutdown. - {StrBegin="MSB4015: "}UE: This message is used for a special exception that is thrown when a logger fails while shutting down (most likely - because of a programming error in the logger). When a logger dies, we cannot proceed with the build, and we throw a special - exception to abort the build. - - - MSB4016: The build was aborted because the "{0}" logger failed unexpectedly during initialization. - MSB4016: The build was aborted because the "{0}" logger failed unexpectedly during initialization. - {StrBegin="MSB4016: "}UE: This message is used for a special exception that is thrown when a logger fails while initializing itself (most - likely because of a programming error in the logger). When a logger dies, we cannot proceed with the build, and we throw a - special exception to abort the build. - - - MSB4017: The build was aborted because of an unexpected logger failure. - MSB4017: The build was aborted because of an unexpected logger failure. - {StrBegin="MSB4017: "}UE: This message is used for a special exception that is thrown when a logger fails while logging an event (most - likely because of a programming error in the logger). When a logger dies, we cannot proceed with the build, and we throw a - special exception to abort the build. - - - MSB4018: The "{0}" task failed unexpectedly. - MSB4018: The "{0}" task failed unexpectedly. - {StrBegin="MSB4018: "}UE: This message is shown when a task terminates because of an unhandled exception. The cause is most likely a - programming error in the task; however, it is also possible that the unhandled exception originated in the engine, and was - surfaced through the task when the task called into the engine. - - - MSB4165: Failed to receive a response from the child node "{0}" in the timeout period "{1}" ms. Shutting down. - MSB4165: Failed to receive a response from the child node "{0}" in the timeout period "{1}" ms. Shutting down. - {StrBegin="MSB4165: "} - - - MSB4088: Condition "{0}" is improperly constructed. - MSB4088: Condition "{0}" is improperly constructed. - {StrBegin="MSB4088: "} - - - MSB4105: Found an unexpected character '{2}' at position {1} in condition "{0}". Did you intend to use "=="? - MSB4105: Found an unexpected character '{2}' at position {1} in condition "{0}". Did you intend to use "=="? - {StrBegin="MSB4105: "} - - - MSB4106: Expected an item list at position {1} in condition "{0}". Did you forget the closing parenthesis? - MSB4106: Expected an item list at position {1} in condition "{0}". Did you forget the closing parenthesis? - {StrBegin="MSB4106: "} - - - MSB4107: Expected an item list at position {1} in condition "{0}". Did you forget the opening parenthesis after the '@'? To use a literal '@', use '%40' instead. - MSB4107: Expected an item list at position {1} in condition "{0}". Did you forget the opening parenthesis after the '@'? To use a literal '@', use '%40' instead. - {StrBegin="MSB4107: "} - - - MSB4108: Expected an item list at position {1} in condition "{0}". Did you forget to close a quote inside the item list expression? - MSB4108: Expected an item list at position {1} in condition "{0}". Did you forget to close a quote inside the item list expression? - {StrBegin="MSB4108: "} - - - MSB4109: Expected a property at position {1} in condition "{0}". Did you forget the closing parenthesis? - MSB4109: Expected a property at position {1} in condition "{0}". Did you forget the closing parenthesis? - {StrBegin="MSB4109: "} - - - MSB4110: Expected a property at position {1} in condition "{0}". Did you forget the opening parenthesis after the '$'? To use a literal '$', use '%24' instead. - MSB4110: Expected a property at position {1} in condition "{0}". Did you forget the opening parenthesis after the '$'? To use a literal '$', use '%24' instead. - {StrBegin="MSB4110: "} - - - MSB4101: Expected a closing quote after position {1} in condition "{0}". - MSB4101: Expected a closing quote after position {1} in condition "{0}". - {StrBegin="MSB4101: "} - - - MSB4019: The imported project "{0}" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk. - MSB4019: The imported project "{0}" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk. - {StrBegin="MSB4019: "}LOCALIZATION: <Import> should not be localized. - - - MSB4089: Incorrect number of arguments to function in condition "{0}". Found {1} argument(s) when expecting {2}. - MSB4089: Incorrect number of arguments to function in condition "{0}". Found {1} argument(s) when expecting {2}. - {StrBegin="MSB4089: "} - - - The "{0}" object specified does not belong to the correct "{1}" object. - The "{0}" object specified does not belong to the correct "{1}" object. - - - - MSB4020: The value "{0}" of the "{1}" attribute in element <{2}> is invalid. - MSB4020: The value "{0}" of the "{1}" attribute in element <{2}> is invalid. - {StrBegin="MSB4020: "}UE: This is a generic message that is displayed when we find a project element with an incorrect value for one of its - attributes e.g. <Import Project=""> -- the value of Project should not be an empty string. - - - MSB4102: The value "{0}" of the "{1}" attribute in element <{2}> is invalid. {3} - MSB4102: The value "{0}" of the "{1}" attribute in element <{2}> is invalid. {3} - {StrBegin="MSB4102: "}UE: This is a generic message that is displayed when we find a project element with an incorrect value for one of its - attributes. At the end of the message we show the exception text we got trying to use the value. - - - MSB4021: The "ContinueOnError" attribute of the "{0}" task is not valid. {1} - MSB4021: The "ContinueOnError" attribute of the "{0}" task is not valid. {1} - {StrBegin="MSB4021: "}LOCALIZATION: "ContinueOnError" should not be localized. "{1}" is a message from another exception explaining the problem. - - - MSB4139: Invalid value for default ToolsVersion is specified in registry key "{0}". - MSB4139: Invalid value for default ToolsVersion is specified in registry key "{0}". - {StrBegin="MSB4139: "} - - - MSB4022: The result "{0}" of evaluating the value "{1}" of the "{2}" attribute in element <{3}> is not valid. - MSB4022: The result "{0}" of evaluating the value "{1}" of the "{2}" attribute in element <{3}> is not valid. - {StrBegin="MSB4022: "}UE: This message is shown when the engine is checking the correctness of the value (after evaluating embedded - properties/items) assigned to an XML attribute of an XML element in the project file. - - - "{0}" is not a valid event category. To raise a custom event, use the "{1}" category. - "{0}" is not a valid event category. To raise a custom event, use the "{1}" category. - - - - "{0}" is not a valid importance level for events. - "{0}" is not a valid importance level for events. - - - - MSB4104: Failed to write to log file "{0}". {1} - MSB4104: Failed to write to log file "{0}". {1} - {StrBegin="MSB4104: "}UE: This is shown when the File Logger can't create or write to the file it was instructed to log to. - - - MSB4024: The imported project file could not be loaded. {0} - MSB4024: The imported project file could not be loaded. {0} - {StrBegin="MSB4024: "}UE: This message is shown when an imported project file cannot be loaded because of incorrect XML. The project - filename is not part of the message because it is provided separately to loggers. - LOCALIZATION: {0} is a localized message from the CLR/FX explaining why the project is invalid. - - - Operation invalid for a persisted item group. - Operation invalid for a persisted item group. - - - - Operation invalid for a virtual item group. - Operation invalid for a virtual item group. - - - - MSB4071: The value Importance="{0}" in the <Message> element is invalid. Valid values are: High, Normal and Low. - MSB4071: The value Importance="{0}" in the <Message> element is invalid. Valid values are: High, Normal and Low. - {StrBegin="MSB4071: "}UE: This message is shown when a user specifies a value for the importance attribute of Message which is not valid. - The importance enumeration is: High, Normal and Low. Specifying any other importance will result in this message being shown - LOCALIZATION: "Importance" should not be localized. - "Message" should not be localized. - High should not be localized. - Normal should not be localized. - Low should not be localized. - - - MSB4025: The project file could not be loaded. {0} - MSB4025: The project file could not be loaded. {0} - {StrBegin="MSB4025: "}UE: This message is shown when the project file given to the engine cannot be loaded because the filename/path is - invalid, or due to lack of permissions, or incorrect XML. The project filename is not part of the message because it is - provided separately to loggers. - LOCALIZATION: {0} is a localized message from the CLR/FX explaining why the project is invalid. - - - MSB4147: The property "{0}" at "{1}" is invalid. {2} - MSB4147: The property "{0}" at "{1}" is invalid. {2} - {StrBegin="MSB4147: "} - - - "{0}" is an invalid "ProjectFileEncoding" value. - "{0}" is an invalid "ProjectFileEncoding" value. - LOCALIZATION: "ProjectFileEncoding" should not be localized. - - - MSB4143: The expression "{0}" cannot be evaluated. {1} - MSB4143: The expression "{0}" cannot be evaluated. {1} - {StrBegin="MSB4143: "} - UE: This message is shown when the user attempts to provide an expression like "$(Registry:HKEY_LOCAL_MACHINE\Software\Vendor\Tools@TaskLocation)" - LOCALIZATION: "{0}" is the expression that was bad. "{1}" is a message from an FX exception that describes why the expression is bad. - - - - MSB4184: The expression "{0}" cannot be evaluated. {1} - MSB4184: The expression "{0}" cannot be evaluated. {1} - {StrBegin="MSB4184: "} - Single quotes as the expression will typically have double quotes in it. - UE: This message is shown when the user attempts to provide an expression like "$(SomeProperty.ToLower())" - LOCALIZATION: "{0}" is the expression that was bad. "{1}" is a message from an FX exception that describes why the expression is bad. - - - - MSB4185: The function "{0}" on type "{1}" has not been enabled for execution. - MSB4185: The function "{0}" on type "{1}" has not been enabled for execution. - {StrBegin="MSB4185: "} - UE: This message is shown when the user attempts to provide an expression like "$([System.DateTime]::Now)", but the expression has not been enabled - LOCALIZATION: "{0}" is the static function name, "{1}" is the .NET Framework type name - - - - MSB4186: Invalid static method invocation syntax: "{0}". Static method invocation should be of the form: $([FullTypeName]::Method()), e.g. $([System.IO.Path]::Combine(`a`, `b`)) - MSB4186: Invalid static method invocation syntax: "{0}". Static method invocation should be of the form: $([FullTypeName]::Method()), e.g. $([System.IO.Path]::Combine(`a`, `b`)) - {StrBegin="MSB4186: "} - UE: This message is shown when the user attempts to call a static method on a type, but has used the incorrect syntax - LOCALIZATION: "{0}" is the function expression which is in error - - - - MSB4070: The schema "{0}" is not valid. {1} - MSB4070: The schema "{0}" is not valid. {1} - {StrBegin="MSB4070: "}UE: This message is shown when the schema file provided for the validation of a project is itself not valid. - LOCALIZATION: "{0}" is the schema file path. "{1}" is a message from an FX exception that describes why the schema file is bad. - - - MSB4026: The "{0}={1}" parameter for the "{2}" task is invalid. - MSB4026: The "{0}={1}" parameter for the "{2}" task is invalid. - {StrBegin="MSB4026: "}UE: This message is displayed when a task has an invalid parameter that cannot be initialized. - - - MSB4027: The "{0}" task generated invalid items from the "{1}" output parameter. {2} - MSB4027: The "{0}" task generated invalid items from the "{1}" output parameter. {2} - {StrBegin="MSB4027: "} - - - MSB4029: The "{0}" task has an invalid output specification. The "TaskParameter" attribute is required, and either the "ItemName" or "PropertyName" attribute must be specified (but not both). - MSB4029: The "{0}" task has an invalid output specification. The "TaskParameter" attribute is required, and either the "ItemName" or "PropertyName" attribute must be specified (but not both). - {StrBegin="MSB4029: "}LOCALIZATION: "TaskParameter", "ItemName" and "PropertyName" should not be localized. - - - MSB4030: "{0}" is an invalid value for the "{1}" parameter of the "{3}" task. The "{1}" parameter is of type "{2}". - MSB4030: "{0}" is an invalid value for the "{1}" parameter of the "{3}" task. The "{1}" parameter is of type "{2}". - {StrBegin="MSB4030: "}UE: This error is shown when a type mis-match occurs between the value assigned to task parameter in the project file - and the type of the .NET property that corresponds to the task parameter. For example, if an int task parameter called "Count" - is assigned the value "x", this error would be displayed: <MyTask Count="x" /> - - - MSB4137: Invalid value specified in the configuration file at "{0}". Property name or tools version name is an empty string. - MSB4137: Invalid value specified in the configuration file at "{0}". Property name or tools version name is an empty string. - {StrBegin="MSB4137: "} - - - MSB4103: "{0}" is not a valid logger verbosity level. - MSB4103: "{0}" is not a valid logger verbosity level. - {StrBegin="MSB4103: "} - - - MSB4163: <ItemDefinitionGroup> is not allowed inside a target. - MSB4163: <ItemDefinitionGroup> is not allowed inside a target. - {StrBegin="MSB4163: "} - - - The specified item does not belong to the current item group. - The specified item does not belong to the current item group. - - - - MSB4096: The item "{0}" in item list "{1}" does not define a value for metadata "{2}". In order to use this metadata, either qualify it by specifying %({1}.{2}), or ensure that all items in this list define a value for this metadata. - MSB4096: The item "{0}" in item list "{1}" does not define a value for metadata "{2}". In order to use this metadata, either qualify it by specifying %({1}.{2}), or ensure that all items in this list define a value for this metadata. - {StrBegin="MSB4096: "} - - - MSB4099: A reference to an item list at position {1} is not allowed in this condition "{0}". - MSB4099: A reference to an item list at position {1} is not allowed in this condition "{0}". - {StrBegin="MSB4099: "} - - - MSB4033: "{0}" is a reserved item metadata, and cannot be redefined as a custom metadata on the item. - MSB4033: "{0}" is a reserved item metadata, and cannot be redefined as a custom metadata on the item. - {StrBegin="MSB4033: "} - - - An InternalLoggerException can only be thrown by the MSBuild engine. The public constructors of this class cannot be used to create an instance of the exception. - An InternalLoggerException can only be thrown by the MSBuild engine. The public constructors of this class cannot be used to create an instance of the exception. - UE: This message is shown when a user tries to instantiate a special exception called InternalLoggerException through the OM -- - only the engine is allowed to create and throw this exception. - LOCALIZATION: "InternalLoggerException" and "MSBuild" should not be localized. - - - Initial Items: - Initial Items: - - - - MSB4083: Expected a Condition attribute on element "{0}". - MSB4083: Expected a Condition attribute on element "{0}". - {StrBegin="MSB4083: "} - - - MSB4164: The value "{0}" of metadata "{1}" contains an item list expression. Item list expressions are not allowed on default metadata values. - MSB4164: The value "{0}" of metadata "{1}" contains an item list expression. Item list expressions are not allowed on default metadata values. - {StrBegin="MSB4164: "} - - - MSBuild is expecting a valid "{0}" object. - MSBuild is expecting a valid "{0}" object. - - - - MSB4035: The required attribute "{0}" is missing from element <{1}>. - MSB4035: The required attribute "{0}" is missing from element <{1}>. - {StrBegin="MSB4035: "}UE: This message is shown when a user leaves off a required attribute from a project element - e.g. <UsingTask AssemblyName="foo"> -- this is missing the "TaskName" attribute. - - - MSB4036: The "{0}" task was not found. Check the following: 1.) The name of the task in the project file is the same as the name of the task class. 2.) The task class is "public" and implements the Microsoft.Build.Framework.ITask interface. 3.) The task is correctly declared with <UsingTask> in the project file, or in the *.tasks files located in the "{1}" directory. - MSB4036: The "{0}" task was not found. Check the following: 1.) The name of the task in the project file is the same as the name of the task class. 2.) The task class is "public" and implements the Microsoft.Build.Framework.ITask interface. 3.) The task is correctly declared with <UsingTask> in the project file, or in the *.tasks files located in the "{1}" directory. - {StrBegin="MSB4036: "}LOCALIZATION: <UsingTask> and "*.tasks" should not be localized. - - - MSB4141: MSBuildToolsPath is not specified for the ToolsVersion "{0}" defined at "{1}", or the value specified evaluates to the empty string. - MSB4141: MSBuildToolsPath is not specified for the ToolsVersion "{0}" defined at "{1}", or the value specified evaluates to the empty string. - {StrBegin="MSB4141: "} - - - MSB4031: The "MSBuildVersion" attribute is deprecated. If the project is authored in the MSBuild 2003 format, please remove the attribute from the <Project> tag. If the project has been authored in the old 1.0 or 1.2 format, please convert it to MSBuild 2003 format. - MSB4031: The "MSBuildVersion" attribute is deprecated. If the project is authored in the MSBuild 2003 format, please remove the attribute from the <Project> tag. If the project has been authored in the old 1.0 or 1.2 format, please convert it to MSBuild 2003 format. - {StrBegin="MSB4031: "}UE: This message is shown for projects that still contain the "MSBuildVersion" attribute in their <Project> - tag. We no longer need this attribute because the project's XML namespace (i.e. the "xmlns" attribute) gives us all the - version information we need. - LOCALIZATION: "MSBuild", "MSBuildVersion" and <Project> should not be localized. - - - MSB4144: Multiple definitions were found for the toolset "{0}". - MSB4144: Multiple definitions were found for the toolset "{0}". - {StrBegin="MSB4144: "} - - - MSB4145: Multiple definitions were found for the property "{0}". - MSB4145: Multiple definitions were found for the property "{0}". - {StrBegin="MSB4145: "} - - - MSB4082: Choose has more than one <Otherwise> element. - MSB4082: Choose has more than one <Otherwise> element. - {StrBegin="MSB4082: "} - - - This method is only valid for persisted <{0}> elements. - This method is only valid for persisted <{0}> elements. - - - - This method is only valid for virtual property groups, not <{0}> elements. - This method is only valid for virtual property groups, not <{0}> elements. - - - - MSB4038: The element <{0}> must be last under element <{1}>. Found element <{2}> instead. - MSB4038: The element <{0}> must be last under element <{1}>. Found element <{2}> instead. - {StrBegin="MSB4038: "} - - - MSB4138: Non-string data was specified at the registry location "{0}". - MSB4138: Non-string data was specified at the registry location "{0}". - {StrBegin="MSB4138: "} - - - MSB4039: No "{0}" element was found in the project file. - MSB4039: No "{0}" element was found in the project file. - {StrBegin="MSB4039: "} - - - MSB4040: There is no target in the project. - MSB4040: There is no target in the project. - {StrBegin="MSB4040: "} - - - Removing the "{0}" attribute of an item is not allowed. - Removing the "{0}" attribute of an item is not allowed. - - - - The object passed in is not part of the project. - The object passed in is not part of the project. - - - - Overriding target "{0}" in project "{1}" with target "{2}" from project "{3}". - Overriding target "{0}" in project "{1}" with target "{2}" from project "{3}". - - - - MSB4167: The parent process unexpectedly exited. Shutting down child node "{0}". - MSB4167: The parent process unexpectedly exited. Shutting down child node "{0}". - {StrBegin="MSB4167: "} - - - {0} ms {1} {2} calls - {0} ms {1} {2} calls - - - - (* = timing was not recorded because of reentrancy) - (* = timing was not recorded because of reentrancy) - - - - This project object has been unloaded from the MSBuild engine and is no longer valid. - This project object has been unloaded from the MSBuild engine and is no longer valid. - - - - The project file "{0}" was not found. - The project file "{0}" was not found. - UE: This message is shown when the user calls into the OM to build a project that doesn't exist on disk. - - - Done building project "{0}" -- FAILED. - Done building project "{0}" -- FAILED. - - - - Done building project "{0}". - Done building project "{0}". - - - - MSB4041: The default XML namespace of the project must be the MSBuild XML namespace. If the project is authored in the MSBuild 2003 format, please add xmlns="{0}" to the <Project> element. If the project has been authored in the old 1.0 or 1.2 format, please convert it to MSBuild 2003 format. - MSB4041: The default XML namespace of the project must be the MSBuild XML namespace. If the project is authored in the MSBuild 2003 format, please add xmlns="{0}" to the <Project> element. If the project has been authored in the old 1.0 or 1.2 format, please convert it to MSBuild 2003 format. - {StrBegin="MSB4041: "}UE: This is a Beta 1 message only. - LOCALIZATION: <Project>, "MSBuild" and "xmlns" should not be localized. - - - Project Performance Summary: - Project Performance Summary: - - - - MSB4042: Stopping because of syntax errors in project file. - MSB4042: Stopping because of syntax errors in project file. - {StrBegin="MSB4042: "} - - - Project "{0}" is building "{1}" ({2} target(s)): - Project "{0}" is building "{1}" ({2} target(s)): - - - - Project "{0}" is building "{1}" (default targets): - Project "{0}" is building "{1}" (default targets): - - - - Project "{0}" ({1} target(s)): - Project "{0}" ({1} target(s)): - - - - Project "{0}" (default targets): - Project "{0}" (default targets): - - - - Done Building Project "{0}" ({1} target(s)). - Done Building Project "{0}" ({1} target(s)). - - - - Done Building Project "{0}" (default targets). - Done Building Project "{0}" (default targets). - - - - Done Building Project "{0}" ({1} target(s)) -- FAILED. - Done Building Project "{0}" ({1} target(s)) -- FAILED. - - - - Done Building Project "{0}" (default targets) -- FAILED. - Done Building Project "{0}" (default targets) -- FAILED. - - - - MSB4075: The project file must be opened in the Visual Studio IDE and converted to the latest version before it can be built by MSBuild. - MSB4075: The project file must be opened in the Visual Studio IDE and converted to the latest version before it can be built by MSBuild. - {StrBegin="MSB4075: "} - - - MSB4192: The project file "{0}" is in the ".vcproj" file format, which MSBuild no longer supports. Please convert the project by opening it in the Visual Studio IDE or running the conversion tool, or use MSBuild 3.5 or earlier to build it. - MSB4192: The project file "{0}" is in the ".vcproj" file format, which MSBuild no longer supports. Please convert the project by opening it in the Visual Studio IDE or running the conversion tool, or use MSBuild 3.5 or earlier to build it. - {StrBegin="MSB4192: "} LOC: ".vcproj" should not be localized - - - The specified property does not belong to the current property group. - The specified property does not belong to the current property group. - - - - Initial Properties: - Initial Properties: - - - - MSB4148: The name of a property stored under the registry key "{0}" has zero length. - MSB4148: The name of a property stored under the registry key "{0}" has zero length. - {StrBegin="MSB4148: "} - - - The property names in the indexer and the "{0}" object do not match. - The property names in the indexer and the "{0}" object do not match. - - - - MSB4043: The item metadata reference "{0}" is invalid because it is qualified with an item name. Item metadata referenced in transforms do not need to be qualified, because the item name is automatically deduced from the items being transformed. Change "{0}" to "%({1})". - MSB4043: The item metadata reference "{0}" is invalid because it is qualified with an item name. Item metadata referenced in transforms do not need to be qualified, because the item name is automatically deduced from the items being transformed. Change "{0}" to "%({1})". - {StrBegin="MSB4043: "}UE: This message is shown when the user does something like this: @(foo->'%(foo.metadata)'). There is no need to specify - "foo.metadata", because "foo" is automatically deduced. In corollary, "bar.metadata" is not allowed either, where "bar" is a different - item list type. - - - MSB4135: Error reading the toolset information from the registry location "{0}". {1} - MSB4135: Error reading the toolset information from the registry location "{0}". {1} - {StrBegin="MSB4135: "} - - - MSB4044: The "{0}" task was not given a value for the required parameter "{1}". - MSB4044: The "{0}" task was not given a value for the required parameter "{1}". - {StrBegin="MSB4044: "}UE: This message is shown when a task parameter designated as "required" is not set in the project file. - - - Validating project using schema file "{0}". - Validating project using schema file "{0}". - LOCALIZATION: "{0}" is the location of the schema file. - - - MSB4045: Project is not valid. {0} - MSB4045: Project is not valid. {0} - {StrBegin="MSB4045: "}UE: This error is shown when the user asks his project to be validated against a schema (/val switch for - MSBuild.exe), and the project has errors. "{0}" contains a message explaining the problem. - LOCALIZATION: "{0}" is a message from the System.XML schema validator and is already localized. - - - MSB4112: The targets in this project have been disabled by the host and therefore cannot be built at this time. This may have been done for security reasons. To enable the targets, the host must set Project.BuildEnabled to "true". - MSB4112: The targets in this project have been disabled by the host and therefore cannot be built at this time. This may have been done for security reasons. To enable the targets, the host must set Project.BuildEnabled to "true". - {StrBegin="MSB4112: "} - - - MSB4093: The "{0}" parameter of the "{1}" task cannot be written to because it does not have a "set" accessor. - MSB4093: The "{0}" parameter of the "{1}" task cannot be written to because it does not have a "set" accessor. - {StrBegin="MSB4093: "}UE: This error is shown when a project tries to assign a value to a task parameter that does not have a "set" - accessor on the corresponding .NET property on the task class. - - - A shallow clone of this object cannot be created. - A shallow clone of this object cannot be created. - - - - Skipping target "{0}" because it has no inputs. - Skipping target "{0}" because it has no inputs. - - - - Though the target has declared its inputs, the input specification only references empty properties and/or empty item lists. - Though the target has declared its inputs, the input specification only references empty properties and/or empty item lists. - - - - Skipping target "{0}" because it has no outputs. - Skipping target "{0}" because it has no outputs. - - - - Though the target has declared its outputs, the output specification only references empty properties and/or empty item lists. - Though the target has declared its outputs, the output specification only references empty properties and/or empty item lists. - - - - Skipping target "{0}" because all output files are up-to-date with respect to the input files. - Skipping target "{0}" because all output files are up-to-date with respect to the input files. - - - - Input files: {0} - Input files: {0} - {0} is a semicolon-separated list of filenames. - - - Output files: {0} - Output files: {0} - {0} is a semicolon-separated list of filenames. - - - Building solution configuration "{0}". - Building solution configuration "{0}". - UE: This is not an error, so doesn't need an error code. - - - Using solution cache file "{0}" for configuration "{1}" and tools version "{2}". - Using solution cache file "{0}" for configuration "{1}" and tools version "{2}". - UE: This is not an error, so doesn't need an error code. - - - Failed to read solution cache file "{0}". {1} Using solution file directly. - Failed to read solution cache file "{0}". {1} Using solution file directly. - UE: This is not a true error, so doesn't need an error code. - - - Failed to write solution cache file "{0}". {1} - Failed to write solution cache file "{0}". {1} - UE: This is not a true error, so doesn't need an error code. - - - Solution cache file was created for a "{0}" value of "{1}" but the current value is "{2}". Refreshing cache file. - Solution cache file was created for a "{0}" value of "{1}" but the current value is "{2}". Refreshing cache file. - UE: This is not an error, so doesn't need an error code. - - - Solution cache file has an internal version number "{0}" but the current value is "{1}". Refreshing cache file. - Solution cache file has an internal version number "{0}" but the current value is "{1}". Refreshing cache file. - UE: This is not an error, so doesn't need an error code. - - - Solution cache file is out of date. Refreshing cache file. {0} - Solution cache file is out of date. Refreshing cache file. {0} - UE: This is not an error, so doesn't need an error code. - - - MSB4160: A circular dependency involving project "{0}" has been detected. - MSB4160: A circular dependency involving project "{0}" has been detected. - {StrBegin="MSB4160: "} - - - MSB4126: The specified solution configuration "{0}" is invalid. Please specify a valid solution configuration using the Configuration and Platform properties (e.g. MSBuild.exe Solution.sln /p:Configuration=Debug /p:Platform="Any CPU") or leave those properties blank to use the default solution configuration. - MSB4126: The specified solution configuration "{0}" is invalid. Please specify a valid solution configuration using the Configuration and Platform properties (e.g. MSBuild.exe Solution.sln /p:Configuration=Debug /p:Platform="Any CPU") or leave those properties blank to use the default solution configuration. - {StrBegin="MSB4126: "}UE: The solution filename is provided separately to loggers. - - - MSB4046: Error reading project file "{0}": {1} - MSB4046: Error reading project file "{0}": {1} - {StrBegin="MSB4046: "} - - - MSB4125: The project file name "{0}" is invalid. {1} - MSB4125: The project file name "{0}" is invalid. {1} - {StrBegin="MSB4125: "}UE: The solution filename is provided separately to loggers. - - - MSB4051: Project {0} is referencing a project with GUID {1}, but a project with this GUID was not found in the .SLN file. - MSB4051: Project {0} is referencing a project with GUID {1}, but a project with this GUID was not found in the .SLN file. - {StrBegin="MSB4051: "}UE: The solution filename is provided separately to loggers. - - - MSB4078: The project file "{0}" is not supported by MSBuild and cannot be built. - MSB4078: The project file "{0}" is not supported by MSBuild and cannot be built. - {StrBegin="MSB4078: "} - - - MSB4054: The solution file must be opened in the Visual Studio IDE and converted to the latest version before it can be built by MSBuild. - MSB4054: The solution file must be opened in the Visual Studio IDE and converted to the latest version before it can be built by MSBuild. - {StrBegin="MSB4054: "}UE: The solution filename is provided separately to loggers. - - - MSB4121: The project configuration for project "{0}" was not specified in the solution file for the solution configuration "{1}". - MSB4121: The project configuration for project "{0}" was not specified in the solution file for the solution configuration "{1}". - {StrBegin="MSB4121: "} - - - The project "{0}" is not selected for building in solution configuration "{1}". - The project "{0}" is not selected for building in solution configuration "{1}". - - UE: This is not an error, so doesn't need an error code. - - - - MSB4122: Scanning project dependencies for project "{0}" failed. {1} - MSB4122: Scanning project dependencies for project "{0}" failed. {1} - {StrBegin="MSB4122: "} - - - MSB4149: The tools version "{0}" of the solution does not support building projects with a different tools version. - MSB4149: The tools version "{0}" of the solution does not support building projects with a different tools version. - {StrBegin="MSB4149: "} - - - Web projects do not support the "Clean" target. Continuing with remaining projects ... - Web projects do not support the "Clean" target. Continuing with remaining projects ... - UE: This is not an error, so doesn't need an error code. - LOCALIZATION: Do not localize "Clean". - - - Web projects do not support the "Publish" target. Continuing with remaining projects ... - Web projects do not support the "Publish" target. Continuing with remaining projects ... - UE: This is not an error, so doesn't need an error code. - LOCALIZATION: Do not localize "Publish". - - - Skipping because the "$(AspNetConfiguration)" configuration is not supported for this web project. You can use the AspNetConfiguration property to override the configuration used for building web projects, by adding /p:AspNetConfiguration=<value> to the command line. Currently web projects only support Debug and Release configurations. - Skipping because the "$(AspNetConfiguration)" configuration is not supported for this web project. You can use the AspNetConfiguration property to override the configuration used for building web projects, by adding /p:AspNetConfiguration=<value> to the command line. Currently web projects only support Debug and Release configurations. - - UE: This is not an error, so doesn't need an error code. - LOCALIZATION: Do NOT localize "AspNetConfiguration", "Debug", "Release". - - - - MSB4076: VC projects do not support the "Publish" target. - MSB4076: VC projects do not support the "Publish" target. - {StrBegin="MSB4076: "}LOCALIZATION: Do not localize "Publish". - - - MSB4098: MSBuild is invoking VCBuild to build this project. Project-to-project references between VC++ projects (.VCPROJ) and C#/VB/VJ# projects (.CSPROJ, .VBPROJ, .VJSPROJ) are not supported by the command-line build systems when building stand-alone VC++ projects. Projects that contain such project-to-project references will fail to build. Please build the solution file containing this project instead. - MSB4098: MSBuild is invoking VCBuild to build this project. Project-to-project references between VC++ projects (.VCPROJ) and C#/VB/VJ# projects (.CSPROJ, .VBPROJ, .VJSPROJ) are not supported by the command-line build systems when building stand-alone VC++ projects. Projects that contain such project-to-project references will fail to build. Please build the solution file containing this project instead. - {StrBegin="MSB4098: "} - - - MSB4056: The MSBuild engine must be called on a single-threaded-apartment. Current threading model is "{0}". Proceeding, but some tasks may not function correctly. - MSB4056: The MSBuild engine must be called on a single-threaded-apartment. Current threading model is "{0}". Proceeding, but some tasks may not function correctly. - {StrBegin="MSB4056: "} - - - Schema validation - Schema validation - UE: this fragment is used to describe errors that are caused by schema validation. For example, if a normal error is - displayed like this: "MSBUILD : error MSB0000: This is an error.", then an error from schema validation would look like this: - "MSBUILD : Schema validation error MSB0000: This is an error." - LOCALIZATION: This fragment needs to be localized. - - - Target "{0}" skipped. Previously built unsuccessfully. - Target "{0}" skipped. Previously built unsuccessfully. - - - - Target "{0}" skipped. Previously built successfully. - Target "{0}" skipped. Previously built successfully. - - - - MSB4116: The condition "{1}" on the "{0}" target has a reference to item metadata. References to item metadata are not allowed in target conditions unless they are part of an item transform. - MSB4116: The condition "{1}" on the "{0}" target has a reference to item metadata. References to item metadata are not allowed in target conditions unless they are part of an item transform. - {StrBegin="MSB4116: "} - - - MSB4057: The target "{0}" does not exist in the project. - MSB4057: The target "{0}" does not exist in the project. - {StrBegin="MSB4057: "} - - - Done building target "{0}" in project "{1}" -- FAILED. - Done building target "{0}" in project "{1}" -- FAILED. - - - - Done building target "{0}" in project "{1}". - Done building target "{0}" in project "{1}". - - - - {0}: (TargetId:{1}) - {0}: (TargetId:{1}) - - - - MSB4058: The "{0}" target is missing its output specification. If a target declares inputs, it must also declare outputs. - MSB4058: The "{0}" target is missing its output specification. If a target declares inputs, it must also declare outputs. - {StrBegin="MSB4058: "} - - - MSB4168: The item "{0}" of type "{1}" does not define a value for the metadata in the expression "{2}". This expression is used in the target output for target "{3}". If a target declares outputs that are transforms, all items in the transform must have a value for the metadata in the transform. - MSB4168: The item "{0}" of type "{1}" does not define a value for the metadata in the expression "{2}". This expression is used in the target output for target "{3}". If a target declares outputs that are transforms, all items in the transform must have a value for the metadata in the transform. - {StrBegin="MSB4168: "} - - - Target Performance Summary: - Target Performance Summary: - - - - Target "{0}" skipped, due to false condition; ({1}) was evaluated as ({2}). - Target "{0}" skipped, due to false condition; ({1}) was evaluated as ({2}). - - - - Target "{0}" in project "{1}" - Target "{0}" in project "{1}" - - - - Target {0}: - Target {0}: - - - - Target "{0}" in file "{1}": - Target "{0}" in file "{1}": - - - - Build continuing because "{0}" on the task "{1}" is set to "{2}". - Build continuing because "{0}" on the task "{1}" is set to "{2}". - - - - Target {0} from project "{1}": - Target {0} from project "{1}": - - - - Target "{0}" in file "{1}" from project "{2}": - Target "{0}" in file "{1}" from project "{2}": - - - - MSB4060: The "{0}" task has been declared or used incorrectly, or failed during construction. Check the spelling of the task name and the assembly name. - MSB4060: The "{0}" task has been declared or used incorrectly, or failed during construction. Check the spelling of the task name and the assembly name. - {StrBegin="MSB4060: "} - - - MSB4077: The "{0}" task has been marked with the attribute LoadInSeparateAppDomain, but does not derive from MarshalByRefObject. Check that the task derives from MarshalByRefObject or AppDomainIsolatedTask. - MSB4077: The "{0}" task has been marked with the attribute LoadInSeparateAppDomain, but does not derive from MarshalByRefObject. Check that the task derives from MarshalByRefObject or AppDomainIsolatedTask. - {StrBegin="MSB4077: "}LOCALIZATION: <LoadInSeparateAppDomain>, <MarshalByRefObject>, <AppDomainIsolatedTask> should not be localized. - - - Done executing task "{0}" -- FAILED. - Done executing task "{0}" -- FAILED. - - - - Done executing task "{0}". - Done executing task "{0}". - - - - {0} (TaskId:{1}) - {0} (TaskId:{1}) - - - - Using "{0}" task from assembly "{1}". - Using "{0}" task from assembly "{1}". - UE: This informational message helps users determine which assemblies their tasks were loaded from. - - - MSB4061: The "{0}" task could not be instantiated from the assembly "{1}". {2} - MSB4061: The "{0}" task could not be instantiated from the assembly "{1}". {2} - {StrBegin="MSB4061: "}LOCALIZATION: "{2}" is a localized message from a CLR/FX exception. - - - MSB4127: The "{0}" task could not be instantiated from the assembly "{1}". Please verify the task assembly has been built using the same version of the Microsoft.Build.Framework assembly as the one installed on your computer and that your host application is not missing a binding redirect for Microsoft.Build.Framework. {2} - MSB4127: The "{0}" task could not be instantiated from the assembly "{1}". Please verify the task assembly has been built using the same version of the Microsoft.Build.Framework assembly as the one installed on your computer and that your host application is not missing a binding redirect for Microsoft.Build.Framework. {2} - {StrBegin="MSB4127: "}UE: This message is a specialized version of the TaskInstantiationFailureError message and can probably reuse some of its docs. - LOCALIZATION: "{2}" is a localized message from a CLR/FX exception. Also, Microsoft.Build.Framework should not be localized - - - MSB4062: The "{0}" task could not be loaded from the assembly {1}. {2} Confirm that the <UsingTask> declaration is correct, and that the assembly and all its dependencies are available. - MSB4062: The "{0}" task could not be loaded from the assembly {1}. {2} Confirm that the <UsingTask> declaration is correct, and that the assembly and all its dependencies are available. - {StrBegin="MSB4062: "}UE: This message is shown when a task cannot be loaded from its assembly for various reasons e.g. corrupt assembly, - invalid task declaration, disk error, etc. "{2}" contains a message explaining what happened. - LOCALIZATION: "{2}" is a message from the CLR loader and is already localized. Also, <UsingTask> should not be localized. - - - MSB4063: The "{0}" task could not be initialized with its input parameters. {1} - MSB4063: The "{0}" task could not be initialized with its input parameters. {1} - {StrBegin="MSB4063: "} - - - Task Performance Summary: - Task Performance Summary: - - - - Task "{0}" skipped, due to false condition; ({1}) was evaluated as ({2}). - Task "{0}" skipped, due to false condition; ({1}) was evaluated as ({2}). - - - - Task "{0}" - Task "{0}" - - - - Time Elapsed {0} - Time Elapsed {0} - - - - Building with tools version "{0}". - Building with tools version "{0}". - - - - Project file contains ToolsVersion="{0}". This toolset is unknown or missing. You may be able to resolve this by installing the appropriate .NET Framework for this toolset. Treating the project as if it had ToolsVersion="4.0". - Project file contains ToolsVersion="{0}". This toolset is unknown or missing. You may be able to resolve this by installing the appropriate .NET Framework for this toolset. Treating the project as if it had ToolsVersion="4.0". - - - - Deferred Messages - Deferred Messages - - - - Some messages did not display because they were not associated with any ProjectStarted events. Use diagnostic verbosity to view these messages. - Some messages did not display because they were not associated with any ProjectStarted events. Use diagnostic verbosity to view these messages. - - - - MSB4090: Found an unexpected character '{2}' at position {1} in condition "{0}". - MSB4090: Found an unexpected character '{2}' at position {1} in condition "{0}". - {StrBegin="MSB4090: "} - - - MSB4091: Found a call to an undefined function "{1}" in condition "{0}". - MSB4091: Found a call to an undefined function "{1}" in condition "{0}". - {StrBegin="MSB4091: "} - - - MSB4064: The "{0}" parameter is not supported by the "{1}" task. Verify the parameter exists on the task, and it is a settable public instance property. - MSB4064: The "{0}" parameter is not supported by the "{1}" task. Verify the parameter exists on the task, and it is a settable public instance property. - {StrBegin="MSB4064: "} - - - MSB4131: The "{0}" parameter is not supported by the "{1}" task. Verify the parameter exists on the task, and it is a gettable public instance property. - MSB4131: The "{0}" parameter is not supported by the "{1}" task. Verify the parameter exists on the task, and it is a gettable public instance property. - {StrBegin="MSB4131: "} - - - MSB4092: An unexpected token "{1}" was found at character position {2} in condition "{0}". - MSB4092: An unexpected token "{1}" was found at character position {2} in condition "{0}". - {StrBegin="MSB4092: "} - - - MSB4065: The "{0}" parameter is not marked for output by the "{1}" task. - MSB4065: The "{0}" parameter is not marked for output by the "{1}" task. - {StrBegin="MSB4065: "} - - - MSB4066: The attribute "{0}" in element <{1}> is unrecognized. - MSB4066: The attribute "{0}" in element <{1}> is unrecognized. - {StrBegin="MSB4066: "} - - - MSB4067: The element <{0}> beneath element <{1}> is unrecognized. - MSB4067: The element <{0}> beneath element <{1}> is unrecognized. - {StrBegin="MSB4067: "} - - - MSB4068: The element <{0}> is unrecognized, or not supported in this context. - MSB4068: The element <{0}> is unrecognized, or not supported in this context. - {StrBegin="MSB4068: "} - - - MSB4132: The tools version "{0}" is unrecognized. - MSB4132: The tools version "{0}" is unrecognized. - {StrBegin="MSB4132: "} - - - MSB4069: The "{0}" type of the "{1}" parameter of the "{2}" task is not supported by MSBuild. - MSB4069: The "{0}" type of the "{1}" parameter of the "{2}" task is not supported by MSBuild. - {StrBegin="MSB4069: "}LOCALIZATION: "MSBuild" should not be localized. - - - MSB4072: A <{0}> element must contain either the "{1}" attribute or the "{2}" attribute (but not both). - MSB4072: A <{0}> element must contain either the "{1}" attribute or the "{2}" attribute (but not both). - {StrBegin="MSB4072: "} - - - {0} Warning(s) - {0} Warning(s) - - - - MSB4084: A <When> element may not follow an <Otherwise> element in a <Choose>. - MSB4084: A <When> element may not follow an <Otherwise> element in a <Choose>. - {StrBegin="MSB4084: "} - - - Target Name: "{0}" Project Name: "{1}" - Target Name: "{0}" Project Name: "{1}" - - - - Cycle trace: - Cycle trace: - - - - MSB4150: Must initialize the console logger using the initialize method before using ApplyParameter - MSB4150: Must initialize the console logger using the initialize method before using ApplyParameter - {StrBegin="MSB4150: "} - - - MSB4151: An error occurred while building project "{0}", target "{1}". Please see innerException for detailed information. - MSB4151: An error occurred while building project "{0}", target "{1}". Please see innerException for detailed information. - {StrBegin="MSB4151: "} - - - MSB4152: An error occurred on the child node "{0}" and could not be passed to the parent node. {1} - MSB4152: An error occurred on the child node "{0}" and could not be passed to the parent node. {1} - {StrBegin="MSB4152: "} - - - MSB4153: A call is made on an inactive IBuildEngine interface corresponding to a task that already finished execution. - MSB4153: A call is made on an inactive IBuildEngine interface corresponding to a task that already finished execution. - {StrBegin="MSB4153: "} - - - MSB4154: A forwarding logger is attempting to forward BuildFinished event - MSB4154: A forwarding logger is attempting to forward BuildFinished event - {StrBegin="MSB4154: "} - - - MSB4155: There was an error while communicating with a node. - MSB4155: There was an error while communicating with a node. - {StrBegin="MSB4155: "} - - - MSB1021: Cannot create an instance of the logger - {0}. - MSB1021: Cannot create an instance of the logger - {0}. - {StrBegin="MSB1021: "}The error code for this message is duplicated from MSBuild.exe. - - - MSB1020: The logger {0} was not found. Check the following: 1.) The logger name specified is the same as the name of the logger class. 2.) The logger class is "public" and implements the Microsoft.Build.Framework.ILogger interface. 3.) The path to the logger assembly is correct, or the logger can be loaded using only the assembly name provided. - MSB1020: The logger {0} was not found. Check the following: 1.) The logger name specified is the same as the name of the logger class. 2.) The logger class is "public" and implements the Microsoft.Build.Framework.ILogger interface. 3.) The path to the logger assembly is correct, or the logger can be loaded using only the assembly name provided. - {StrBegin="MSB1020: "}The error code for this message is duplicated from MSBuild.exe. - - - MSB4156: A forwarding logger is attempting to forward BuildStarted event - MSB4156: A forwarding logger is attempting to forward BuildStarted event - {StrBegin="MSB4156: "} - - - "{0}" ({1} target) ({2}) -> - "{0}" ({1} target) ({2}) -> - - - - "{0}" (default target) ({1}) -> - "{0}" (default target) ({1}) -> - - - - {0} {1,5} - {0} {1,5} - - - - Project "{0}" on node {1} ({2} target(s)). - Project "{0}" on node {1} ({2} target(s)). - - - - Project "{0}" on node {1} (default targets). - Project "{0}" on node {1} (default targets). - - - - Project "{0}" ({1}) is building "{2}" ({3}) on node {4} ({5} target(s)). - Project "{0}" ({1}) is building "{2}" ({3}) on node {4} ({5} target(s)). - - - - Project "{0}" ({1}) is building "{2}" ({3}) on node {4} (default targets). - Project "{0}" ({1}) is building "{2}" ({3}) on node {4} (default targets). - - - - ({0} target) -> - ({0} target) -> - - - - MSB4157: The array of project files needs to contain at least one value. - MSB4157: The array of project files needs to contain at least one value. - {StrBegin="MSB4157: "} - - - MSB4158: The project file name at element {0} is empty. - MSB4158: The project file name at element {0} is empty. - {StrBegin="MSB4158: "} - - - The property "{0}" with value "{1}" is being overridden by another batch. The property is now: "{2}" - The property "{0}" with value "{1}" is being overridden by another batch. The property is now: "{2}" - - - - Please see inner exception for error information. - Please see inner exception for error information. - - - - Event type "{0}" was expected to be serializable. The event was not serializable and has been ignored. - Event type "{0}" was expected to be serializable. The event was not serializable and has been ignored. - - - - The log file path cannot be null or empty. - The log file path cannot be null or empty. - - - - MSB4161: Project "{0}" was loaded and unloaded during the current build. Reloading a project during the build can result in errors or an inconsistent build state. Either avoid unloading project "{0}" or cache the evaluation results of target(s) "{1}" before unloading the project. - MSB4161: Project "{0}" was loaded and unloaded during the current build. Reloading a project during the build can result in errors or an inconsistent build state. Either avoid unloading project "{0}" or cache the evaluation results of target(s) "{1}" before unloading the project. - {StrBegin="MSB4161: "} - - - [default] - [default] - - - - - \ No newline at end of file diff --git a/src/Directory.Build.props b/src/Directory.Build.props index b7413f2ced0..b0e23319446 100644 --- a/src/Directory.Build.props +++ b/src/Directory.Build.props @@ -39,9 +39,6 @@ false - - en;cs;de;es;fr;it;ja;ko;pl;pt-BR;ru;tr;zh-Hans;zh-Hant - true - @@ -38,7 +37,6 @@ - @@ -54,7 +52,6 @@ - @@ -70,7 +67,6 @@ - diff --git a/src/Package/MSBuild.VSSetup/files.swr b/src/Package/MSBuild.VSSetup/files.swr index eac0cd9b1b1..66aabe0c5e3 100644 --- a/src/Package/MSBuild.VSSetup/files.swr +++ b/src/Package/MSBuild.VSSetup/files.swr @@ -101,12 +101,6 @@ folder InstallDir:\MSBuild\Current\Bin\de file source=$(X86BinPath)de\Microsoft.Build.Utilities.Core.resources.dll vs.file.ngenArchitecture=all file source=$(X86BinPath)de\MSBuild.resources.dll vs.file.ngenArchitecture=all file source=$(TaskHostBinPath)de\MSBuildTaskHost.resources.dll vs.file.ngenArchitecture=all -folder InstallDir:\MSBuild\Current\Bin\en - file source=$(X86BinPath)en\Microsoft.Build.resources.dll vs.file.ngenArchitecture=all - file source=$(X86BinPath)en\Microsoft.Build.Tasks.Core.resources.dll vs.file.ngenArchitecture=all - file source=$(X86BinPath)en\Microsoft.Build.Utilities.Core.resources.dll vs.file.ngenArchitecture=all - file source=$(X86BinPath)en\MSBuild.resources.dll vs.file.ngenArchitecture=all - file source=$(TaskHostBinPath)en\MSBuildTaskHost.resources.dll vs.file.ngenArchitecture=all folder InstallDir:\MSBuild\Current\Bin\es file source=$(X86BinPath)es\Microsoft.Build.resources.dll vs.file.ngenArchitecture=all file source=$(X86BinPath)es\Microsoft.Build.Tasks.Core.resources.dll vs.file.ngenArchitecture=all @@ -245,12 +239,6 @@ folder InstallDir:\MSBuild\Current\Bin\amd64\de file source=$(X64BinPath)de\Microsoft.Build.Utilities.Core.resources.dll vs.file.ngenArchitecture=all file source=$(X64BinPath)de\MSBuild.resources.dll vs.file.ngenArchitecture=all file source=$(TaskHostX64BinPath)de\MSBuildTaskHost.resources.dll vs.file.ngenArchitecture=all -folder InstallDir:\MSBuild\Current\Bin\amd64\en - file source=$(X64BinPath)en\Microsoft.Build.resources.dll vs.file.ngenArchitecture=all - file source=$(X64BinPath)en\Microsoft.Build.Tasks.Core.resources.dll vs.file.ngenArchitecture=all - file source=$(X64BinPath)en\Microsoft.Build.Utilities.Core.resources.dll vs.file.ngenArchitecture=all - file source=$(X64BinPath)en\MSBuild.resources.dll vs.file.ngenArchitecture=all - file source=$(TaskHostX64BinPath)en\MSBuildTaskHost.resources.dll vs.file.ngenArchitecture=all folder InstallDir:\MSBuild\Current\Bin\amd64\es file source=$(X64BinPath)es\Microsoft.Build.resources.dll vs.file.ngenArchitecture=all file source=$(X64BinPath)es\Microsoft.Build.Tasks.Core.resources.dll vs.file.ngenArchitecture=all diff --git a/src/Shared/Resources/xlf/Strings.shared.en.xlf b/src/Shared/Resources/xlf/Strings.shared.en.xlf deleted file mode 100644 index 62bf77f50b8..00000000000 --- a/src/Shared/Resources/xlf/Strings.shared.en.xlf +++ /dev/null @@ -1,313 +0,0 @@ - - - - - - MSB4188: Build was canceled. - MSB4188: Build was canceled. - {StrBegin="MSB4188: "} Error when the build stops suddenly for some reason. For example, because a child node died. - - - MSB5022: The MSBuild task host does not support running tasks that perform IBuildEngine callbacks. If you wish to perform these operations, please run your task in the core MSBuild process instead. A task will automatically execute in the task host if the UsingTask has been attributed with a "Runtime" or "Architecture" value, or the task invocation has been attributed with an "MSBuildRuntime" or "MSBuildArchitecture" value, that does not match the current runtime or architecture of MSBuild. - MSB5022: The MSBuild task host does not support running tasks that perform IBuildEngine callbacks. If you wish to perform these operations, please run your task in the core MSBuild process instead. A task will automatically execute in the task host if the UsingTask has been attributed with a "Runtime" or "Architecture" value, or the task invocation has been attributed with an "MSBuildRuntime" or "MSBuildArchitecture" value, that does not match the current runtime or architecture of MSBuild. - {StrBegin="MSB5022: "} "Runtime", "Architecture", "MSBuildRuntime", and "MSBuildArchitecture" are all attributes in the project file, and thus should not be localized. - - - Build started. - Build started. - - - - MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{1}". - MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{1}". - {StrBegin="MSB4008: "}UE: This message is shown when the type/class of a task cannot be resolved uniquely from a single assembly. - - - Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. - Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored. - - - - {0} ({1},{2}) - {0} ({1},{2}) - A file location to be embedded in a string. - - - Making the following modifications to the environment received from the parent node before applying it to the task host: - Making the following modifications to the environment received from the parent node before applying it to the task host: - Only ever used when MSBuild is run under a "secret" environment variable switch, MSBuildTaskHostUpdateEnvironmentAndLog=1 - - - Setting '{0}' to '{1}' rather than the parent environment's value, '{2}'. - Setting '{0}' to '{1}' rather than the parent environment's value, '{2}'. - Only ever used when MSBuild is run under a "secret" environment variable switch, MSBuildTaskHostUpdateEnvironmentAndLog=1 - - - MSB4025: The project file could not be loaded. {0} - MSB4025: The project file could not be loaded. {0} - {StrBegin="MSB4025: "}UE: This message is shown when the project file given to the engine cannot be loaded because the filename/path is - invalid, or due to lack of permissions, or incorrect XML. The project filename is not part of the message because it is - provided separately to loggers. - LOCALIZATION: {0} is a localized message from the CLR/FX explaining why the project is invalid. - - - MSB4103: "{0}" is not a valid logger verbosity level. - MSB4103: "{0}" is not a valid logger verbosity level. - {StrBegin="MSB4103: "} - - - MSB4233: There was an exception while reading the log file: {0} - MSB4233: There was an exception while reading the log file: {0} - {StrBegin="MSB4233: "}This is shown when the Binary Logger can't read the log file. - - - MSBuild is expecting a valid "{0}" object. - MSBuild is expecting a valid "{0}" object. - - - - Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. - Path: {0} exceeds the OS max path limit. The fully qualified file name must be less than {1} characters. - - - - MSB5028: Solution filter file at "{0}" includes project "{1}" that is not in the solution file at "{2}". - MSB5028: Solution filter file at "{0}" includes project "{1}" that is not in the solution file at "{2}". - {StrBegin="MSB5028: "}UE: The project filename is provided separately to loggers. - - - MSB5025: Json in solution filter file "{0}" is incorrectly formatted. - MSB5025: Json in solution filter file "{0}" is incorrectly formatted. - {StrBegin="MSB5025: "}UE: The solution filename is provided separately to loggers. - - - MSB5026: The solution filter file at "{0}" specifies there will be a solution file at "{1}", but that file does not exist. - MSB5026: The solution filter file at "{0}" specifies there will be a solution file at "{1}", but that file does not exist. - {StrBegin="MSB5026: "}UE: The solution filename is provided separately to loggers. - - - MSB5009: Error parsing the project "{0}" section with GUID: "{1}". It is nested under "{2}" but that project is not found in the solution. - MSB5009: Error parsing the project "{0}" section with GUID: "{1}". It is nested under "{2}" but that project is not found in the solution. - {StrBegin="MSB5009: "}UE: The solution filename is provided separately to loggers. - - - MSB4132: The tools version "{0}" is unrecognized. Available tools versions are {1}. - MSB4132: The tools version "{0}" is unrecognized. Available tools versions are {1}. - {StrBegin="MSB4132: "}LOCALIZATION: {1} contains a comma separated list. - - - MSB5016: The name "{0}" contains an invalid character "{1}". - MSB5016: The name "{0}" contains an invalid character "{1}". - {StrBegin="MSB5016: "} - - - "{0}" is a reserved item metadata, and cannot be modified or deleted. - "{0}" is a reserved item metadata, and cannot be modified or deleted. - UE: Tasks and OM users are not allowed to remove or change the value of the built-in metadata on items e.g. the meta-data "FullPath", "RelativeDir", etc. are reserved. - - - The string "{0}" cannot be converted to a boolean (true/false) value. - The string "{0}" cannot be converted to a boolean (true/false) value. - - - - MSB5003: Failed to create a temporary file. Temporary files folder is full or its path is incorrect. {0} - MSB5003: Failed to create a temporary file. Temporary files folder is full or its path is incorrect. {0} - {StrBegin="MSB5003: "} - - - MSB5018: Failed to delete the temporary file "{0}". {1} - MSB5018: Failed to delete the temporary file "{0}". {1} - {StrBegin="MSB5018: "} - - - The item metadata "%({0})" cannot be applied to the path "{1}". {2} - The item metadata "%({0})" cannot be applied to the path "{1}". {2} - UE: This message is shown when the user tries to perform path manipulations using one of the built-in item metadata e.g. %(RootDir), on an item-spec that's not a valid path. LOCALIZATION: "{2}" is a localized message from a CLR/FX exception. - - - MSB4077: The "{0}" task has been marked with the attribute LoadInSeparateAppDomain, but does not derive from MarshalByRefObject. Check that the task derives from MarshalByRefObject or AppDomainIsolatedTask. - MSB4077: The "{0}" task has been marked with the attribute LoadInSeparateAppDomain, but does not derive from MarshalByRefObject. Check that the task derives from MarshalByRefObject or AppDomainIsolatedTask. - {StrBegin="MSB4077: "}LOCALIZATION: <LoadInSeparateAppDomain>, <MarshalByRefObject>, <AppDomainIsolatedTask> should not be localized. - - - .NET Framework version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. - .NET Framework version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. - - - - .NET Framework version "{0}" is not supported when explicitly targeting the Windows SDK, which is only supported on .NET 4.5 and later. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion that is Version45 or above. - .NET Framework version "{0}" is not supported when explicitly targeting the Windows SDK, which is only supported on .NET 4.5 and later. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion that is Version45 or above. - - - - Visual Studio version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.VisualStudioVersion. - Visual Studio version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.VisualStudioVersion. - - - - When attempting to generate a reference assembly path from the path "{0}" and the framework moniker "{1}" there was an error. {2} - When attempting to generate a reference assembly path from the path "{0}" and the framework moniker "{1}" there was an error. {2} - No Error code because this resource will be used in an exception. The error code is discarded if it is included - - - Could not find directory path: {0} - Could not find directory path: {0} - Directory must exist - - - You do not have access to: {0} - You do not have access to: {0} - Directory must have access - - - Schema validation - Schema validation - - UE: this fragment is used to describe errors that are caused by schema validation. For example, if a normal error is - displayed like this: "MSBUILD : error MSB0000: This is an error.", then an error from schema validation would look like this: - "MSBUILD : Schema validation error MSB0000: This is an error." - LOCALIZATION: This fragment needs to be localized. - - - - MSB5002: Terminating the task executable "{0}" because it did not finish within the specified limit of {1} milliseconds. - MSB5002: Terminating the task executable "{0}" because it did not finish within the specified limit of {1} milliseconds. - {StrBegin="MSB5002: "} - - - Parameter "{0}" cannot be null. - Parameter "{0}" cannot be null. - - - - Parameter "{0}" with assigned value "{1}" cannot have invalid path or invalid file characters. - Parameter "{0}" with assigned value "{1}" cannot have invalid path or invalid file characters. - - - - Parameter "{0}" cannot have zero length. - Parameter "{0}" cannot have zero length. - - - - Parameters "{0}" and "{1}" must have the same number of elements. - Parameters "{0}" and "{1}" must have the same number of elements. - - - - The resource string "{0}" for the "{1}" task cannot be found. Confirm that the resource name "{0}" is correctly spelled, and the resource exists in the task's assembly. - The resource string "{0}" for the "{1}" task cannot be found. Confirm that the resource name "{0}" is correctly spelled, and the resource exists in the task's assembly. - - - - The "{0}" task has not registered its resources. In order to use the "TaskLoggingHelper.FormatResourceString()" method this task needs to register its resources either during construction, or via the "TaskResources" property. - The "{0}" task has not registered its resources. In order to use the "TaskLoggingHelper.FormatResourceString()" method this task needs to register its resources either during construction, or via the "TaskResources" property. - LOCALIZATION: "TaskLoggingHelper.FormatResourceString()" and "TaskResources" should not be localized. - - - MSB5004: The solution file has two projects named "{0}". - MSB5004: The solution file has two projects named "{0}". - {StrBegin="MSB5004: "}UE: The solution filename is provided separately to loggers. - - - MSB5005: Error parsing project section for project "{0}". The project file name "{1}" contains invalid characters. - MSB5005: Error parsing project section for project "{0}". The project file name "{1}" contains invalid characters. - {StrBegin="MSB5005: "}UE: The solution filename is provided separately to loggers. - - - MSB5006: Error parsing project section for project "{0}". The project file name is empty. - MSB5006: Error parsing project section for project "{0}". The project file name is empty. - {StrBegin="MSB5006: "}UE: The solution filename is provided separately to loggers. - - - MSB5007: Error parsing the project configuration section in solution file. The entry "{0}" is invalid. - MSB5007: Error parsing the project configuration section in solution file. The entry "{0}" is invalid. - {StrBegin="MSB5007: "}UE: The solution filename is provided separately to loggers. - - - MSB5008: Error parsing the solution configuration section in solution file. The entry "{0}" is invalid. - MSB5008: Error parsing the solution configuration section in solution file. The entry "{0}" is invalid. - {StrBegin="MSB5008: "}UE: The solution filename is provided separately to loggers. - - - MSB5009: Error parsing the nested project section in solution file. - MSB5009: Error parsing the nested project section in solution file. - {StrBegin="MSB5009: "}UE: The solution filename is provided separately to loggers. - - - MSB5023: Error parsing the nested project section in solution file. A project with the GUID "{0}" is listed as being nested under project "{1}", but does not exist in the solution. - MSB5023: Error parsing the nested project section in solution file. A project with the GUID "{0}" is listed as being nested under project "{1}", but does not exist in the solution. - {StrBegin="MSB5023: "}UE: The solution filename is provided separately to loggers. - - - MSB5010: No file format header found. - MSB5010: No file format header found. - {StrBegin="MSB5010: "}UE: The solution filename is provided separately to loggers. - - - MSB5011: Parent project GUID not found in "{0}" project dependency section. - MSB5011: Parent project GUID not found in "{0}" project dependency section. - {StrBegin="MSB5011: "}UE: The solution filename is provided separately to loggers. - - - MSB5012: Unexpected end-of-file reached inside "{0}" project section. - MSB5012: Unexpected end-of-file reached inside "{0}" project section. - {StrBegin="MSB5012: "}UE: The solution filename is provided separately to loggers. - - - MSB5013: Error parsing a project section. - MSB5013: Error parsing a project section. - {StrBegin="MSB5013: "}UE: The solution filename is provided separately to loggers. - - - MSB5014: File format version is not recognized. MSBuild can only read solution files between versions {0}.0 and {1}.0, inclusive. - MSB5014: File format version is not recognized. MSBuild can only read solution files between versions {0}.0 and {1}.0, inclusive. - {StrBegin="MSB5014: "}UE: The solution filename is provided separately to loggers. - - - MSB5015: The properties could not be read from the WebsiteProperties section of the "{0}" project. - MSB5015: The properties could not be read from the WebsiteProperties section of the "{0}" project. - {StrBegin="MSB5015: "}UE: The solution filename is provided separately to loggers. - - - Unrecognized solution version "{0}", attempting to continue. - Unrecognized solution version "{0}", attempting to continue. - - - - Solution file - Solution file - UE: this fragment is used to describe errors found while parsing solution files. For example, if a normal error is - displayed like this: "MSBUILD : error MSB0000: This is an error.", then an error from solution parsing would look like this: - "MSBUILD : Solution file error MSB0000: This is an error." - LOCALIZATION: This fragment needs to be localized. - - - MSB5019: The project file is malformed: "{0}". {1} - MSB5019: The project file is malformed: "{0}". {1} - {StrBegin="MSB5019: "} - - - MSB5020: Could not load the project file: "{0}". {1} - MSB5020: Could not load the project file: "{0}". {1} - {StrBegin="MSB5020: "} - - - MSB5021: Terminating the task executable "{0}" and its child processes because the build was canceled. - MSB5021: Terminating the task executable "{0}" and its child processes because the build was canceled. - {StrBegin="MSB5021: "} - - - MSB5024: Could not determine a valid location to MSBuild. Try running this process from the Developer Command Prompt for Visual Studio. - MSB5024: Could not determine a valid location to MSBuild. Try running this process from the Developer Command Prompt for Visual Studio. - {StrBegin="MSB5024: "} - - - This collection is read-only. - This collection is read-only. - - - - - \ No newline at end of file diff --git a/src/Tasks/ManifestUtil/Resources/xlf/Strings.ManifestUtilities.en.xlf b/src/Tasks/ManifestUtil/Resources/xlf/Strings.ManifestUtilities.en.xlf deleted file mode 100644 index 5949f78fc3a..00000000000 --- a/src/Tasks/ManifestUtil/Resources/xlf/Strings.ManifestUtilities.en.xlf +++ /dev/null @@ -1,99 +0,0 @@ - - - - - - Out of process servers are not supported - Out of process servers are not supported - - - - Registry key '{0}' is missing value '{1}'. - Registry key '{0}' is missing value '{1}'. - - - - No registered classes were detected for this component. - No registered classes were detected for this component. - - - - Components under system file protection should not be isolated. - Components under system file protection should not be isolated. - - - - Could not load type library. - Could not load type library. - - - - Registry key '{0}' was not imported. - Registry key '{0}' was not imported. - - - - Registry value '{0}' was not imported. - Registry value '{0}' was not imported. - - - - The file to be signed {0} could not be found. - The file to be signed {0} could not be found. - - - - Failed to sign {0}. {1} - Failed to sign {0}. {1} - - - - Warning while signing {0}. {1} - Warning while signing {0}. {1} - - - - SignTool.exe was not found at path {0}. - SignTool.exe was not found at path {0}. - - - - Timestamp URL server name or address could not be resolved. - Timestamp URL server name or address could not be resolved. - - - - Only certificates using RSA encryption are valid for signing ClickOnce manifests. - Only certificates using RSA encryption are valid for signing ClickOnce manifests. - - - - - UAC Manifest Options - If you want to change the Windows User Account Control level replace the - requestedExecutionLevel node with one of the following. - - <requestedExecutionLevel level="asInvoker" uiAccess="false" /> - <requestedExecutionLevel level="requireAdministrator" uiAccess="false" /> - <requestedExecutionLevel level="highestAvailable" uiAccess="false" /> - - If you want to utilize File and Registry Virtualization for backward - compatibility then delete the requestedExecutionLevel node. - - - UAC Manifest Options - If you want to change the Windows User Account Control level replace the - requestedExecutionLevel node with one of the following. - - <requestedExecutionLevel level="asInvoker" uiAccess="false" /> - <requestedExecutionLevel level="requireAdministrator" uiAccess="false" /> - <requestedExecutionLevel level="highestAvailable" uiAccess="false" /> - - If you want to utilize File and Registry Virtualization for backward - compatibility then delete the requestedExecutionLevel node. - - - - - - diff --git a/src/Tasks/Resources/xlf/Strings.en.xlf b/src/Tasks/Resources/xlf/Strings.en.xlf deleted file mode 100644 index 751a0a265bf..00000000000 --- a/src/Tasks/Resources/xlf/Strings.en.xlf +++ /dev/null @@ -1,3355 +0,0 @@ - - - - - - BindingRedirect is missing required field 'oldVersion'. - BindingRedirect is missing required field 'oldVersion'. - - - - BindingRedirect is missing required field 'newVersion'. - BindingRedirect is missing required field 'newVersion'. - - - - Some attributes of the assemblyIdentity element are incorrect. - Some attributes of the assemblyIdentity element are incorrect. - - - - There was a problem parsing the oldVersion attribute. {0} - There was a problem parsing the oldVersion attribute. {0} - - - - There was a problem parsing the newVersion attribute. {0} - There was a problem parsing the newVersion attribute. {0} - - - - The platform mapping "{0}" in the platform mapping list "{1}" is malformed. Please only pass in a semicolon-delimited list of constant string values separated by "=", e.g., "foo=bar;foo2=bar2". - The platform mapping "{0}" in the platform mapping list "{1}" is malformed. Please only pass in a semicolon-delimited list of constant string values separated by "=", e.g., "foo=bar;foo2=bar2". - - - - Project reference "{0}" has not been resolved. - Project reference "{0}" has not been resolved. - - UE and LOCALIZATION: - This is not an error - we pass unresolved references to UnresolvedProjectReferences for further - processing in the .targets file. - - - - Project reference "{0}" has been assigned the "{1}" configuration. - Project reference "{0}" has been assigned the "{1}" configuration. - - - - MSB3461: The MetabasePath parameter cannot be combined with VirtualPath or PhysicalPath. - MSB3461: The MetabasePath parameter cannot be combined with VirtualPath or PhysicalPath. - {StrBegin="MSB3461: "} - - - MSB3462: Either MetabasePath or VirtualPath must be specified. - MSB3462: Either MetabasePath or VirtualPath must be specified. - {StrBegin="MSB3462: "} - - - MSB3463: The TargetPath parameter must be specified if the application is updatable. - MSB3463: The TargetPath parameter must be specified if the application is updatable. - {StrBegin="MSB3463: "} - - - MSB3464: The TargetPath parameter must be specified if the target directory needs to be overwritten. - MSB3464: The TargetPath parameter must be specified if the target directory needs to be overwritten. - {StrBegin="MSB3464: "} - - - MSB3001: Cannot extract culture information from file name "{0}". {1} - MSB3001: Cannot extract culture information from file name "{0}". {1} - {StrBegin="MSB3001: "} - - - Culture of "{0}" was assigned to file "{1}". - Culture of "{0}" was assigned to file "{1}". - - - - MSB3656: No input file has been passed to the task, exiting. - MSB3656: No input file has been passed to the task, exiting. - {StrBegin="MSB3656: "} - - - MSB3646: Cannot specify values for both KeyFile and KeyContainer. - MSB3646: Cannot specify values for both KeyFile and KeyContainer. - {StrBegin="MSB3646: "} - - - MSB3647: DelaySign parameter is true, but no KeyFile or KeyContainer was specified. - MSB3647: DelaySign parameter is true, but no KeyFile or KeyContainer was specified. - {StrBegin="MSB3647: "} - - - MSB3649: The KeyFile path '{0}' is invalid. KeyFile must point to an existing file. - MSB3649: The KeyFile path '{0}' is invalid. KeyFile must point to an existing file. - {StrBegin="MSB3649: "} - - - MSB3650: Neither SDKToolsPath '{0}' nor ToolPath '{1}' is a valid directory. One of these must be set. - MSB3650: Neither SDKToolsPath '{0}' nor ToolPath '{1}' is a valid directory. One of these must be set. - {StrBegin="MSB3650: "} - - - MSB3651: The key container '{0}' does not contain a public/private key pair. - MSB3651: The key container '{0}' does not contain a public/private key pair. - {StrBegin="MSB3651: "} - - - MSB3652: The key file '{0}' does not contain a public/private key pair. - MSB3652: The key file '{0}' does not contain a public/private key pair. - {StrBegin="MSB3652: "} - - - MSB3653: AxTlbBaseTask is not an executable task. If deriving from it, please ensure the ToolName property was set. - MSB3653: AxTlbBaseTask is not an executable task. If deriving from it, please ensure the ToolName property was set. - {StrBegin="MSB3653: "} - - - MSB3654: Delay signing requires that at least a public key be specified. Please either supply a public key using the KeyFile or KeyContainer properties, or disable delay signing. - MSB3654: Delay signing requires that at least a public key be specified. Please either supply a public key using the KeyFile or KeyContainer properties, or disable delay signing. - {StrBegin="MSB3654: "} - - - MSB3752: The "{0}" attribute of the <{1}> element has been set but is empty. If the "{0}" attribute is set it must not be empty. - MSB3752: The "{0}" attribute of the <{1}> element has been set but is empty. If the "{0}" attribute is set it must not be empty. - {StrBegin="MSB3752: "} - - - Compiling task source code - Compiling task source code - - - - MSB3756: The attribute "{0}" is not valid for the <Code> element. Valid attributes are "Language", "Source", and "Type". - MSB3756: The attribute "{0}" is not valid for the <Code> element. Valid attributes are "Language", "Source", and "Type". - {StrBegin="MSB3756: "} - - - MSB3759: The specified code language "{0}" is invalid. The supported code languages are "{1}". - MSB3759: The specified code language "{0}" is invalid. The supported code languages are "{1}". - {StrBegin="MSB3759: "} - - - MSB3759: The specified code type "{0}" is invalid. The supported code types are "{1}". - MSB3759: The specified code type "{0}" is invalid. The supported code types are "{1}". - {StrBegin="MSB3759: "} - - - MSB3761: The specified task XML is invalid. {0} - MSB3761: The specified task XML is invalid. {0} - {StrBegin="MSB3761: "} - - - MSB3760: You must specify source code within the Code element or a path to a file containing source code. - MSB3760: You must specify source code within the Code element or a path to a file containing source code. - {StrBegin="MSB3760: "} - - - MSB3881: Fatal Error: more than {0} command line arguments. - MSB3881: Fatal Error: more than {0} command line arguments. - {StrBegin="MSB3881: "} - - - MSB3882: Fatal Error: No response from server. - MSB3882: Fatal Error: No response from server. - {StrBegin="MSB3882: "} - - - MSB3883: Unexpected exception: - MSB3883: Unexpected exception: - {StrBegin="MSB3883: "} - - - MSB3884: Could not find rule set file "{0}". - MSB3884: Could not find rule set file "{0}". - {StrBegin="MSB3884: "} - - - Creating directory "{0}". - Creating directory "{0}". - - - - MSB3024: Could not copy the file "{0}" to the destination file "{1}", because the destination is a folder instead of a file. To copy the source file into a folder, consider using the DestinationFolder parameter instead of DestinationFiles. - MSB3024: Could not copy the file "{0}" to the destination file "{1}", because the destination is a folder instead of a file. To copy the source file into a folder, consider using the DestinationFolder parameter instead of DestinationFiles. - {StrBegin="MSB3024: "} - - - Did not copy from file "{0}" to file "{1}" because the "{2}" parameter was set to "{3}" in the project and the files' sizes and timestamps match. - Did not copy from file "{0}" to file "{1}" because the "{2}" parameter was set to "{3}" in the project and the files' sizes and timestamps match. - - - - MSB3021: Unable to copy file "{0}" to "{1}". {2} - MSB3021: Unable to copy file "{0}" to "{1}". {2} - {StrBegin="MSB3021: "} - - - MSB3892: ErrorIfLinkFails requires UseHardlinksIfPossible or UseSymbolicLinksIfPossible to be set. - MSB3892: ErrorIfLinkFails requires UseHardlinksIfPossible or UseSymbolicLinksIfPossible to be set. - {StrBegin="MSB3892: "} LOCALIZATION: Do not localize "ErrorIfLinkFails", "UseHardLinksIfPossible", or "UseSymbolicLinksIfPossible". - - - MSB3022: Both "{0}" and "{1}" were specified as input parameters in the project file. Please choose one or the other. - MSB3022: Both "{0}" and "{1}" were specified as input parameters in the project file. Please choose one or the other. - {StrBegin="MSB3022: "} - - - Copying file from "{0}" to "{1}". - Copying file from "{0}" to "{1}". - LOCALIZATION: {0} and {1} are paths. - - - Creating hard link to copy "{0}" to "{1}". - Creating hard link to copy "{0}" to "{1}". - LOCALIZATION: {0} and {1} are paths. - - - MSB3893: Could not use a link to copy "{0}" to "{1}". - MSB3893: Could not use a link to copy "{0}" to "{1}". - {StrBegin="MSB3893: "} LOCALIZATION: {0} and {1} are paths. - - - Could not use a link to copy "{0}" to "{1}". Copying the file instead. {2} - Could not use a link to copy "{0}" to "{1}". Copying the file instead. {2} - LOCALIZATION: {0} and {1} are paths. {2} is an optional localized message. - - - MSB3023: No destination specified for Copy. Please supply either "{0}" or "{1}". - MSB3023: No destination specified for Copy. Please supply either "{0}" or "{1}". - {StrBegin="MSB3023: "} - - - Removing read-only attribute from "{0}". - Removing read-only attribute from "{0}". - - - - MSB3025: The source file "{0}" is actually a directory. The "Copy" task does not support copying directories. - MSB3025: The source file "{0}" is actually a directory. The "Copy" task does not support copying directories. - {StrBegin="MSB3025: "} - - - Creating symbolic link to copy "{0}" to "{1}". - Creating symbolic link to copy "{0}" to "{1}". - LOCALIZATION: {0} and {1} are paths. - - - MSB3026: Could not copy "{0}" to "{1}". Beginning retry {2} in {3}ms. {4} {5} - MSB3026: Could not copy "{0}" to "{1}". Beginning retry {2} in {3}ms. {4} {5} - {StrBegin="MSB3026: "} LOCALIZATION: {0} and {1} are paths. {2} and {3} are numbers. {4} is an optional localized message. {5} is either empty or a string from Copy.FileLocked ("The file is locked by: "{0}"") - - - MSB3027: Could not copy "{0}" to "{1}". Exceeded retry count of {2}. Failed. {3} - MSB3027: Could not copy "{0}" to "{1}". Exceeded retry count of {2}. Failed. {3} - {StrBegin="MSB3027: "} LOCALIZATION: {0} and {1} are paths. {2} is a number. {3} is either empty or a string from Copy.FileLocked ("The file is locked by: "{0}"") - - - MSB3028: {0} is an invalid retry count. Value must not be negative. - MSB3028: {0} is an invalid retry count. Value must not be negative. - {StrBegin="MSB3028: "} LOCALIZATION: {0} is a number. - - - MSB3029: {0} is an invalid retry delay. Value must not be negative. - MSB3029: {0} is an invalid retry delay. Value must not be negative. - {StrBegin="MSB3029: "} LOCALIZATION: {0} is a number. - - - MSB3030: Could not copy the file "{0}" because it was not found. - MSB3030: Could not copy the file "{0}" because it was not found. - {StrBegin="MSB3030: "} LOCALIZATION: {0} is a number. - - - The file is locked by: "{0}" - The file is locked by: "{0}" - - - - MSB3031: Could not set additional metadata. "{0}" is a reserved metadata name and cannot be modified. - MSB3031: Could not set additional metadata. "{0}" is a reserved metadata name and cannot be modified. - {StrBegin="MSB3031: "} UE: Tasks and OM users are not allowed to remove or change the value of the built-in meta-data on items e.g. the meta-data "FullPath", "RelativeDir", etc. are reserved. - - - Resource file '{0}' gets manifest resource name '{1}'. - Resource file '{0}' gets manifest resource name '{1}'. - - - - MSB3042: A namespace or class definition was found within a conditional compilation directive in the file "{0}". This may lead to an incorrect choice for the manifest resource name for resource "{1}". - MSB3042: A namespace or class definition was found within a conditional compilation directive in the file "{0}". This may lead to an incorrect choice for the manifest resource name for resource "{1}". - {StrBegin="MSB3042: "} - - - Resource file '{0}' depends on '{1}'. - Resource file '{0}' depends on '{1}'. - - - - Resource file '{0}' doesn't depend on any other file. - Resource file '{0}' doesn't depend on any other file. - - - - MSB3041: Unable to create a manifest resource name for "{0}". {1} - MSB3041: Unable to create a manifest resource name for "{0}". {1} - {StrBegin="MSB3041: "} - - - Root namespace is empty. - Root namespace is empty. - - - - Root namespace is '{0}'. - Root namespace is '{0}'. - - - - MSB3053: The assembly alias "{1}" on reference "{0}" contains illegal characters. - MSB3053: The assembly alias "{1}" on reference "{0}" contains illegal characters. - {StrBegin="MSB3053: "} - - - MSB3051: The parameter to the compiler is invalid. {0} - MSB3051: The parameter to the compiler is invalid. {0} - {StrBegin="MSB3051: "} - - - MSB3052: The parameter to the compiler is invalid, '{0}{1}' will be ignored. - MSB3052: The parameter to the compiler is invalid, '{0}{1}' will be ignored. - {StrBegin="MSB3052: "} - - - Deleting file "{0}". - Deleting file "{0}". - - - - MSB3061: Unable to delete file "{0}". {1} - MSB3061: Unable to delete file "{0}". {1} - {StrBegin="MSB3061: "} - - - File "{0}" doesn't exist. Skipping. - File "{0}" doesn't exist. Skipping. - - - - Did not download file from "{0}" to "{1}" because the "{2}" parameter was set to "{3}" in the project and the files' sizes match. - Did not download file from "{0}" to "{1}" because the "{2}" parameter was set to "{3}" in the project and the files' sizes match. - - - - Downloading from "{0}" to "{1}" ({2:N0} bytes). - Downloading from "{0}" to "{1}" ({2:N0} bytes). - - - - MSB3923: Failed to download file "{0}". {1} - MSB3923: Failed to download file "{0}". {1} - {StrBegin="MSB3923: "} - - - MSB3921: The specified URL "{0}" is not valid. - MSB3921: The specified URL "{0}" is not valid. - {StrBegin="MSB3921: "} - - - MSB3922: Failed to determine a file name from the URL "{0}". Please specify a file name with the "{1}" parameter. - MSB3922: Failed to determine a file name from the URL "{0}". Please specify a file name with the "{1}" parameter. - {StrBegin="MSB3922: "} - - - MSB3924: Failed to download file "{0}". Beginning retry {1} in {2}ms. {3} - MSB3924: Failed to download file "{0}". Beginning retry {1} in {2}ms. {3} - {StrBegin="MSB3924: "} - - - MSB3071: All drive letters from A: through Z: are currently in use. Since the working directory "{0}" is a UNC path, the "Exec" task needs a free drive letter to map the UNC path to. Disconnect from one or more shared resources to free up drive letters, or specify a local working directory before attempting this command again. - MSB3071: All drive letters from A: through Z: are currently in use. Since the working directory "{0}" is a UNC path, the "Exec" task needs a free drive letter to map the UNC path to. Disconnect from one or more shared resources to free up drive letters, or specify a local working directory before attempting this command again. - {StrBegin="MSB3071: "}LOCALIZATION: "Exec", "A:", and "Z:" should not be localized. - - - MSB3073: The command "{0}" exited with code {1}. - MSB3073: The command "{0}" exited with code {1}. - {StrBegin="MSB3073: "} - - - MSB3075: The command "{0}" exited with code {1}. Please verify that you have sufficient rights to run this command. - MSB3075: The command "{0}" exited with code {1}. Please verify that you have sufficient rights to run this command. - {StrBegin="MSB3075: "} - - - The command "{0}" exited with code {1}. - The command "{0}" exited with code {1}. - - - - MSB3076: The regular expression "{0}" that was supplied is invalid. {1} - MSB3076: The regular expression "{0}" that was supplied is invalid. {1} - {StrBegin="MSB3076: "} - - - MSB3072: The "Exec" task needs a command to execute. - MSB3072: The "Exec" task needs a command to execute. - {StrBegin="MSB3072: "}LOCALIZATION: "Exec" should not be localized. - - - The working directory "{0}" does not exist. - The working directory "{0}" does not exist. - No error code because an error will be prefixed. - - - MSB3954: Failed to compute hash for file '{0}' because it does not exist or is inaccessible. - MSB3954: Failed to compute hash for file '{0}' because it does not exist or is inaccessible. - {StrBegin="MSB3954: "} - - - MSB3953: Unrecognized hash algorithm name '{0}'. Allowed algorithms are 'SHA256', 'SHA384', and 'SHA512'. - MSB3953: Unrecognized hash algorithm name '{0}'. Allowed algorithms are 'SHA256', 'SHA384', and 'SHA512'. - {StrBegin="MSB3953: "} - - - MSB3951: Unrecognized hash encoding '{0}'. Allowed encodings are 'hex' and 'base64'. - MSB3951: Unrecognized hash encoding '{0}'. Allowed encodings are 'hex' and 'base64'. - {StrBegin="MSB3951: "} - - - Found "{0}". - Found "{0}". - - - - "{0}" is not a valid file name. {1} - "{0}" is not a valid file name. {1} - - - - Comparison path is "{0}". - Comparison path is "{0}". - - - - MSB3541: {0} has invalid value "{1}". {2} - MSB3541: {0} has invalid value "{1}". {2} - {StrBegin="MSB3541: "} - - - MSB3102: Could not delete state file "{0}". {1} - MSB3102: Could not delete state file "{0}". {1} - {StrBegin="MSB3102: "} - - - Could not locate the assembly "{0}". Check to make sure the assembly exists on disk. - Could not locate the assembly "{0}". Check to make sure the assembly exists on disk. - - - - MSB3088: Could not read state file "{0}". {1} - MSB3088: Could not read state file "{0}". {1} - {StrBegin="MSB3088: "} - - - Could not read state file "{0}". {1} - Could not read state file "{0}". {1} - - - - MSB3081: A problem occurred while trying to set the "{0}" parameter for the IDE's in-process compiler. {1} - MSB3081: A problem occurred while trying to set the "{0}" parameter for the IDE's in-process compiler. {1} - {StrBegin="MSB3081: "} - - - MSB3101: Could not write state file "{0}". {1} - MSB3101: Could not write state file "{0}". {1} - {StrBegin="MSB3101: "} - - - MSB3105: The item "{0}" was specified more than once in the "{1}" parameter. Duplicate items are not supported by the "{1}" parameter. - MSB3105: The item "{0}" was specified more than once in the "{1}" parameter. Duplicate items are not supported by the "{1}" parameter. - {StrBegin="MSB3105: "} - - - MSB3083: The item "{0}" was specified more than once in the "{1}" parameter and both items had the same value "{2}" for the "{3}" metadata. Duplicate items are not supported by the "{1}" parameter unless they have different values for the "{3}" metadata. - MSB3083: The item "{0}" was specified more than once in the "{1}" parameter and both items had the same value "{2}" for the "{3}" metadata. Duplicate items are not supported by the "{1}" parameter unless they have different values for the "{3}" metadata. - {StrBegin="MSB3083: "} - - - MSB3108: Error executing the {0} task. {1} - MSB3108: Error executing the {0} task. {1} - {StrBegin="MSB3108: "} - - - Expected a file but got directory "{0}". - Expected a file but got directory "{0}". - - - - Expected file "{0}" does not exist. - Expected file "{0}" does not exist. - - - - MSB3082: Task failed because "{0}" was not found, or the .NET Framework {1} is not installed. Please install the .NET Framework {1}. - MSB3082: Task failed because "{0}" was not found, or the .NET Framework {1} is not installed. Please install the .NET Framework {1}. - {StrBegin="MSB3082: "} - - - MSB3087: An incompatible host object was passed into the "{0}" task. The host object for this task must implement the "{1}" interface. - MSB3087: An incompatible host object was passed into the "{0}" task. The host object for this task must implement the "{1}" interface. - {StrBegin="MSB3087: "} - - - The format of this state file is not valid. - The format of this state file is not valid. - - - - Item "{0}" has attribute "{1}" with value "{2}" that could not be converted to "{3}". - Item "{0}" has attribute "{1}" with value "{2}" that could not be converted to "{3}". - - - - MSB3095: Invalid argument. {0} - MSB3095: Invalid argument. {0} - {StrBegin="MSB3095: "} - - - MSB3097: File "{0}" is not a valid assembly. - MSB3097: File "{0}" is not a valid assembly. - {StrBegin="MSB3097: "} - - - MSB3098: "{1}" task received an invalid value for the "{0}" parameter. - MSB3098: "{1}" task received an invalid value for the "{0}" parameter. - {StrBegin="MSB3098: "} - - - MSB3099: Invalid assembly name "{0}". {1} - MSB3099: Invalid assembly name "{0}". {1} - {StrBegin="MSB3099: "}UE: This message is shown when RegisterAssembly or UnregisterAssembly is passed an assembly with an invalid filename. "{0}" is the name of the file, and "{1}" is a message explaining the problem. LOCALIZATION: "{1}" is a localized message. - - - MSB3100: Syntax for "{0}" parameter is not valid ({1}). Correct syntax is {0}="<name>=<value>". - MSB3100: Syntax for "{0}" parameter is not valid ({1}). Correct syntax is {0}="<name>=<value>". - {StrBegin="MSB3100: "}This error is shown if the user does any of the following: - Properties="foo" (missing property value) - Properties="=4" (missing property name) - The user must pass in an actual property name and value, as in Properties="Configuration=Debug". - - - Global Properties: - Global Properties: - - - - MSB3667: There is already a file at "{0}". If you are trying to create a precomputed cache, ensure that you are building a single project that depends on your assemblies rather than building your assemblies themselves. If you are running the ResolveAssemblyReference task normally, do not set the "AssemblyInformationCacheOutputPath" parameter of the ResolveAssemblyReference task. - MSB3667: There is already a file at "{0}". If you are trying to create a precomputed cache, ensure that you are building a single project that depends on your assemblies rather than building your assemblies themselves. If you are running the ResolveAssemblyReference task normally, do not set the "AssemblyInformationCacheOutputPath" parameter of the ResolveAssemblyReference task. - {StrBegin="MSB3667: "} - - - Removing Properties: - Removing Properties: - - - - Overriding Global Properties for project "{0}" with: - Overriding Global Properties for project "{0}" with: - - - - Additional Properties for project "{0}": - Additional Properties for project "{0}": - - - - Removing Properties for project "{0}": - Removing Properties for project "{0}": - - - - MSB3103: Invalid Resx file. {0} - MSB3103: Invalid Resx file. {0} - {StrBegin="MSB3103: "} - - - MSB3106: Assembly strong name "{0}" is either a path which could not be found or it is a full assembly name which is badly formed. If it is a full assembly name it may contain characters that need to be escaped with backslash(\). Those characters are Equals(=), Comma(,), Quote("), Apostrophe('), Backslash(\). - MSB3106: Assembly strong name "{0}" is either a path which could not be found or it is a full assembly name which is badly formed. If it is a full assembly name it may contain characters that need to be escaped with backslash(\). Those characters are Equals(=), Comma(,), Quote("), Apostrophe('), Backslash(\). - {StrBegin="MSB3106: "} - - - MSB3107: The specified project reference metadata for the reference "{0}" is missing or has an invalid value: {1} - MSB3107: The specified project reference metadata for the reference "{0}" is missing or has an invalid value: {1} - {StrBegin="MSB3107: "} - - - The IDE's in-process compiler does not support the specified values for the "{0}" parameter. Therefore, this task will fallback to using the command-line compiler. - The IDE's in-process compiler does not support the specified values for the "{0}" parameter. Therefore, this task will fallback to using the command-line compiler. - - - - MSB3091: Task failed because "{0}" was not found, or the correct Microsoft Windows SDK is not installed. The task is looking for "{0}" in the "bin" subdirectory beneath the location specified in the {1} value of the registry key {2}. You may be able to solve the problem by doing one of the following: 1) Install the Microsoft Windows SDK. 2) Install Visual Studio 2010. 3) Manually set the above registry key to the correct location. 4) Pass the correct location into the "ToolPath" parameter of the task. - MSB3091: Task failed because "{0}" was not found, or the correct Microsoft Windows SDK is not installed. The task is looking for "{0}" in the "bin" subdirectory beneath the location specified in the {1} value of the registry key {2}. You may be able to solve the problem by doing one of the following: 1) Install the Microsoft Windows SDK. 2) Install Visual Studio 2010. 3) Manually set the above registry key to the correct location. 4) Pass the correct location into the "ToolPath" parameter of the task. - {StrBegin="MSB3091: "} - - - MSB3084: Task attempted to find "{0}" in two locations. 1) Under the "{1}" processor specific directory which is generated based on SdkToolsPath 2) The x86 specific directory under "{2}" which is specified by the SDKToolsPath property. You may be able to solve the problem by doing one of the following: 1) Set the "SDKToolsPath" property to the location of the Microsoft Windows SDK. - MSB3084: Task attempted to find "{0}" in two locations. 1) Under the "{1}" processor specific directory which is generated based on SdkToolsPath 2) The x86 specific directory under "{2}" which is specified by the SDKToolsPath property. You may be able to solve the problem by doing one of the following: 1) Set the "SDKToolsPath" property to the location of the Microsoft Windows SDK. - {StrBegin="MSB3084: "} - - - Task attempted to find "{0}" using the SdkToolsPath value "{1}". Make sure the SdkToolsPath is set to the correct value and the tool exists in the correct processor specific location below it. - Task attempted to find "{0}" using the SdkToolsPath value "{1}". Make sure the SdkToolsPath is set to the correct value and the tool exists in the correct processor specific location below it. - - - - MSB3086: Task could not find "{0}" using the SdkToolsPath "{1}" or the registry key "{2}". Make sure the SdkToolsPath is set and the tool exists in the correct processor specific location under the SdkToolsPath and that the Microsoft Windows SDK is installed - MSB3086: Task could not find "{0}" using the SdkToolsPath "{1}" or the registry key "{2}". Make sure the SdkToolsPath is set and the tool exists in the correct processor specific location under the SdkToolsPath and that the Microsoft Windows SDK is installed - {StrBegin="MSB3086: "} - - - MSB3666: The SDK tool "{0}" could not be found. {1} - MSB3666: The SDK tool "{0}" could not be found. {1} - {StrBegin="MSB3666: "} The {1} will be the exception message - - - MSB3104: The referenced assembly "{0}" was not found. If this assembly is produced by another one of your projects, please make sure to build that project before building this one. - MSB3104: The referenced assembly "{0}" was not found. If this assembly is produced by another one of your projects, please make sure to build that project before building this one. - {StrBegin="MSB3104: "} - - - MSB3093: The command exited with code {0}. - MSB3093: The command exited with code {0}. - {StrBegin="MSB3093: "} - - - MSB3094: "{2}" refers to {0} item(s), and "{3}" refers to {1} item(s). They must have the same number of items. - MSB3094: "{2}" refers to {0} item(s), and "{3}" refers to {1} item(s). They must have the same number of items. - {StrBegin="MSB3094: "} - - - MSB3831: The application configuration file must have root configuration element. - MSB3831: The application configuration file must have root configuration element. - {StrBegin="MSB3831: "} - - - MSB3832: The version number "{0}" is invalid. - MSB3832: The version number "{0}" is invalid. - {StrBegin="MSB3832: "} - - - MSB3833: The assembly name "{0}" contained in the suggested binding redirect is invalid. - MSB3833: The assembly name "{0}" contained in the suggested binding redirect is invalid. - {StrBegin="MSB3833: "} - - - No suggested binding redirects from ResolveAssemblyReferences. - No suggested binding redirects from ResolveAssemblyReferences. - - - - MSB3835: The "{0}" node is missing from the "{1}" node. Skipping. - MSB3835: The "{0}" node is missing from the "{1}" node. Skipping. - {StrBegin="MSB3835: "} - - - MSB3836: The explicit binding redirect on "{0}" conflicts with an autogenerated binding redirect. Consider removing it from the application configuration file or disabling autogenerated binding redirects. The build will replace it with: "{1}". - MSB3836: The explicit binding redirect on "{0}" conflicts with an autogenerated binding redirect. Consider removing it from the application configuration file or disabling autogenerated binding redirects. The build will replace it with: "{1}". - {StrBegin="MSB3836: "} - - - Processing suggested binding redirect on "{0}" with MaxVersion "{1}". - Processing suggested binding redirect on "{0}" with MaxVersion "{1}". - - - - MSB3161: A circular dependency was detected between the following built packages: {0}. - MSB3161: A circular dependency was detected between the following built packages: {0}. - {StrBegin="MSB3161: "} - - - MSB3142: An error occurred trying to copy '{0}' to '{1}': {2} - MSB3142: An error occurred trying to copy '{0}' to '{1}': {2} - {StrBegin="MSB3142: "} - - - MSB3143: An error occurred trying to copy '{0}' for item '{1}': {2} - MSB3143: An error occurred trying to copy '{0}' for item '{1}': {2} - {StrBegin="MSB3143: "} - - - MSB3162: The '{0}' item selected requires '{1}'. Select the missing prerequisite in the Prerequisites Dialog Box or create a bootstrapper package for the missing prerequisite. - MSB3162: The '{0}' item selected requires '{1}'. Select the missing prerequisite in the Prerequisites Dialog Box or create a bootstrapper package for the missing prerequisite. - {StrBegin="MSB3162: "} - - - MSB3165: The value of the '{0}' attribute in '{1}' does not match that of file '{2}'. - MSB3165: The value of the '{0}' attribute in '{1}' does not match that of file '{2}'. - {StrBegin="MSB3165: "} - - - MSB3168: Duplicate item '{0}' will be ignored. - MSB3168: Duplicate item '{0}' will be ignored. - {StrBegin="MSB3168: "} - - - MSB3169: An error occurred generating a bootstrapper: {0} - MSB3169: An error occurred generating a bootstrapper: {0} - {StrBegin="MSB3169: "} - - - MSB3151: Item '{0}' already includes '{1}'. - MSB3151: Item '{0}' already includes '{1}'. - {StrBegin="MSB3151: "} - - - MSB3163: Build input parameter 'ComponentsLocation={0}' is not valid. The value must be one of 'HomeSite', 'Relative', or 'Absolute'. Defaulting to 'HomeSite'. - MSB3163: Build input parameter 'ComponentsLocation={0}' is not valid. The value must be one of 'HomeSite', 'Relative', or 'Absolute'. Defaulting to 'HomeSite'. - {StrBegin="MSB3163: "} - - - MSB3144: Not enough data was provided to generate a bootstrapper. Please provide a value for at least one of the parameters: 'ApplicationFile' or 'BootstrapperItems'. - MSB3144: Not enough data was provided to generate a bootstrapper. Please provide a value for at least one of the parameters: 'ApplicationFile' or 'BootstrapperItems'. - {StrBegin="MSB3144: "} - - - MSB3145: Build input parameter '{0}={1}' is not a web url or UNC share. - MSB3145: Build input parameter '{0}={1}' is not a web url or UNC share. - {StrBegin="MSB3145: "} - - - MSB3146: Item '{0}' is required by '{1}', but was not included. - MSB3146: Item '{0}' is required by '{1}', but was not included. - {StrBegin="MSB3146: "} - - - MSB3696: One of the following items '{0}' is required by '{1}', but none were included. - MSB3696: One of the following items '{0}' is required by '{1}', but none were included. - {StrBegin="MSB3696: "} - - - MSB3147: Could not find required file '{0}' in '{1}'. - MSB3147: Could not find required file '{0}' in '{1}'. - {StrBegin="MSB3147: "} - - - MSB3141: No 'PublicKey' or 'Hash' attribute specified for file '{0}' in item '{1}'. - MSB3141: No 'PublicKey' or 'Hash' attribute specified for file '{0}' in item '{1}'. - {StrBegin="MSB3141: "} - - - MSB3170: Item '{0}' could not find any of dependent items '{1}'. - MSB3170: Item '{0}' could not find any of dependent items '{1}'. - {StrBegin="MSB3170: "} - - - MSB3148: No output path specified in build settings. - MSB3148: No output path specified in build settings. - {StrBegin="MSB3148: "} - - - MSB3149: No resources available for building a bootstrapper. - MSB3149: No resources available for building a bootstrapper. - {StrBegin="MSB3149: "} - - - MSB3150: No string resources available for building a bootstrapper with culture '{0}'. - MSB3150: No string resources available for building a bootstrapper with culture '{0}'. - {StrBegin="MSB3150: "} - - - MSB3152: To enable 'Download prerequisites from the same location as my application' in the Prerequisites dialog box, you must download file '{0}' for item '{1}' to your local machine. For more information, see http://go.microsoft.com/fwlink/?LinkId=616018. - MSB3152: To enable 'Download prerequisites from the same location as my application' in the Prerequisites dialog box, you must download file '{0}' for item '{1}' to your local machine. For more information, see http://go.microsoft.com/fwlink/?LinkId=616018. - {StrBegin="MSB3152: "} - - - MSB3166: Could not find required file '{0}' for item '{1}'. - MSB3166: Could not find required file '{0}' for item '{1}'. - {StrBegin="MSB3166: "} - - - MSB3164: No 'HomeSite' attribute has been provided for '{0}', so the package will be published to the same location as the bootstrapper. - MSB3164: No 'HomeSite' attribute has been provided for '{0}', so the package will be published to the same location as the bootstrapper. - {StrBegin="MSB3164: "} - - - MSB3153: Xml validation did not pass for item '{0}' located at '{1}'. - MSB3153: Xml validation did not pass for item '{0}' located at '{1}'. - {StrBegin="MSB3153: "} - - - MSB3154: Could not find string resources for item '{0}'. - MSB3154: Could not find string resources for item '{0}'. - {StrBegin="MSB3154: "} - - - MSB3155: Item '{0}' could not be located in '{1}'. - MSB3155: Item '{0}' could not be located in '{1}'. - {StrBegin="MSB3155: "} - - - MSB3156: Xml validation did not pass for item '{0}' located at '{1}'. - MSB3156: Xml validation did not pass for item '{0}' located at '{1}'. - {StrBegin="MSB3156: "} - - - MSB3157: Could not match culture '{0}' for item '{1}'. Using culture '{2}' instead. - MSB3157: Could not match culture '{0}' for item '{1}'. Using culture '{2}' instead. - {StrBegin="MSB3157: "} - - - MSB3158: Could not find resources for culture '{0}'. Using culture '{1}' instead. - MSB3158: Could not find resources for culture '{0}'. Using culture '{1}' instead. - {StrBegin="MSB3158: "} - - - MSB3159: Xml Validation error in file '{0}': {1} - MSB3159: Xml Validation error in file '{0}': {1} - {StrBegin="MSB3159: "} - - - MSB3160: Xml Validation warning in file '{0}': {1} - MSB3160: Xml Validation warning in file '{0}': {1} - {StrBegin="MSB3160: "} - - - MSB3961: An error occurred trying to copy '{0}' to '{1}': {2} - MSB3961: An error occurred trying to copy '{0}' to '{1}': {2} - {StrBegin="MSB3961: "} - - - MSB3962: An error occurred generating a launcher: {0} - MSB3962: An error occurred generating a launcher: {0} - {StrBegin="MSB3962: "} - - - MSB3963: Not enough data was provided to generate a launcher. Please provide a value for: 'EntryPoint'. - MSB3963: Not enough data was provided to generate a launcher. Please provide a value for: 'EntryPoint'. - {StrBegin="MSB3963: "} - - - MSB3964: Could not find required file '{0}'. - MSB3964: Could not find required file '{0}'. - {StrBegin="MSB3964: "} - - - MSB3965: No output path specified in build settings. - MSB3965: No output path specified in build settings. - {StrBegin="MSB3965: "} - - - MSB3177: Reference '{0}' does not allow partially trusted callers. - MSB3177: Reference '{0}' does not allow partially trusted callers. - {StrBegin="MSB3177: "} - - - MSB3178: Assembly '{0}' is incorrectly specified as a file. - MSB3178: Assembly '{0}' is incorrectly specified as a file. - {StrBegin="MSB3178: "} - - - MSB3179: Problem isolating COM reference '{0}': {1} - MSB3179: Problem isolating COM reference '{0}': {1} - {StrBegin="MSB3179: "} - - - MSB3111: Use of app.config binding redirects requires full trust. - MSB3111: Use of app.config binding redirects requires full trust. - {StrBegin="MSB3111: "} - - - MSB3112: Two or more assemblies have the same identity '{0}'. - MSB3112: Two or more assemblies have the same identity '{0}'. - {StrBegin="MSB3112: "} - - - MSB3180: COM component '{1}' is defined in both '{3}' and '{4}', {0}="{2}". - MSB3180: COM component '{1}' is defined in both '{3}' and '{4}', {0}="{2}". - {StrBegin="MSB3180: "} - - - MSB3181: Two or more files have the same target path '{0}'. - MSB3181: Two or more files have the same target path '{0}'. - {StrBegin="MSB3181: "} - - - MSB3127: The default icon {0} could not be found in the current file references or is not part of the required download group. The default icon file name is case sensitive so the file name referenced in the application manifest must exactly match the icon's file name. - MSB3127: The default icon {0} could not be found in the current file references or is not part of the required download group. The default icon file name is case sensitive so the file name referenced in the application manifest must exactly match the icon's file name. - {StrBegin="MSB3127: "} - - - MSB3119: File association extensions must start with a period character (.). - MSB3119: File association extensions must start with a period character (.). - {StrBegin="MSB3119: "} - - - MSB3120: File association extension '{0}' exceeds the maximum allowed length of {1}. - MSB3120: File association extension '{0}' exceeds the maximum allowed length of {1}. - {StrBegin="MSB3120: "} - - - MSB3121: The file association element in the application manifest is missing one or more of the following required attributes: extension, description, progid, or default icon. - MSB3121: The file association element in the application manifest is missing one or more of the following required attributes: extension, description, progid, or default icon. - {StrBegin="MSB3121: "} - - - MSB3122: Use of file associations requires full trust. - MSB3122: Use of file associations requires full trust. - {StrBegin="MSB3122: "} - - - MSB3123: The number of file associations exceeds the limit of {0}. - MSB3123: The number of file associations exceeds the limit of {0}. - {StrBegin="MSB3123: "} - - - MSB3124: A file association has already been created for extension '{0}'. - MSB3124: A file association has already been created for extension '{0}'. - {StrBegin="MSB3124: "} - - - MSB3125: The application is using file associations but has no EntryPoint build parameter. - MSB3125: The application is using file associations but has no EntryPoint build parameter. - {StrBegin="MSB3125: "} - - - MSB3126: The application is using file associations but is not marked for installation. File associations cannot be used for applications that are not installed such as applications hosted in a web browser. - MSB3126: The application is using file associations but is not marked for installation. File associations cannot be used for applications that are not installed such as applications hosted in a web browser. - {StrBegin="MSB3126: "} - - - MSB3171: Problem generating manifest. {0} - MSB3171: Problem generating manifest. {0} - {StrBegin="MSB3171: "} - - - MSB3176: Specified minimum required version is greater than the current publish version. Please specify a version less than or equal to the current publish version. - MSB3176: Specified minimum required version is greater than the current publish version. Please specify a version less than or equal to the current publish version. - {StrBegin="MSB3176: "} - - - MSB3117: Application is set to host in browser but the TargetFrameworkVersion is set to v2.0. - MSB3117: Application is set to host in browser but the TargetFrameworkVersion is set to v2.0. - - - - MSB3116: Application is marked to host in browser but is also marked for online and offline use. Please change your application to online only. - MSB3116: Application is marked to host in browser but is also marked for online and offline use. Please change your application to online only. - - - - MSB3110: Assembly '{0}' has mismatched identity '{1}', expected file name: '{2}'. - MSB3110: Assembly '{0}' has mismatched identity '{1}', expected file name: '{2}'. - {StrBegin="MSB3110: "} - - - MSB3115: File '{0}' is not a valid entry point. - MSB3115: File '{0}' is not a valid entry point. - {StrBegin="MSB3115: "} - - - MSB3184: Input manifest is invalid. - MSB3184: Input manifest is invalid. - {StrBegin="MSB3184: "} - - - MSB3133: The ExcludePermissions property is deprecated. The permission set requested by the application has been set to the permissions defined in Internet or Local Intranet zone. To continue using a custom Permission Set, define your custom permission set in the Security Page of the Project Designer. - MSB3133: The ExcludePermissions property is deprecated. The permission set requested by the application has been set to the permissions defined in Internet or Local Intranet zone. To continue using a custom Permission Set, define your custom permission set in the Security Page of the Project Designer. - {StrBegin="MSB3133: "} - - - MSB3134: The permission set requested by the application exceeded the permissions allowed by the Internet or Intranet zones. Select Full Trust or to continue using partial trust, define your custom permission set in the Security Page of the Project Designer. - MSB3134: The permission set requested by the application exceeded the permissions allowed by the Internet or Intranet zones. Select Full Trust or to continue using partial trust, define your custom permission set in the Security Page of the Project Designer. - {StrBegin="MSB3134: "} - - - MSB3135: The PermissionSet for the target zone has not been defined for the following version of the .NET Framework: {0}. - MSB3135: The PermissionSet for the target zone has not been defined for the following version of the .NET Framework: {0}. - {StrBegin="MSB3135: "} - - - MSB3175: Invalid value for '{0}' of item '{1}'. - MSB3175: Invalid value for '{0}' of item '{1}'. - {StrBegin="MSB3175: "} - - - MSB3174: Invalid value for '{0}'. - MSB3174: Invalid value for '{0}'. - {StrBegin="MSB3174: "} - - - MSB3189: The update location for this application is a local path. - MSB3189: The update location for this application is a local path. - {StrBegin="MSB3189: "} - - - MSB3185: EntryPoint not specified for manifest. - MSB3185: EntryPoint not specified for manifest. - {StrBegin="MSB3185: "} - - - MSB3186: Unable to infer an assembly identity for generated manifest from task input parameters. - MSB3186: Unable to infer an assembly identity for generated manifest from task input parameters. - {StrBegin="MSB3186: "} - - - MSB3187: Referenced assembly '{0}' targets a different processor than the application. - MSB3187: Referenced assembly '{0}' targets a different processor than the application. - {StrBegin="MSB3187: "} - - - MSB3188: Assembly '{0}' must be strong signed in order to be marked as a prerequisite. - MSB3188: Assembly '{0}' must be strong signed in order to be marked as a prerequisite. - {StrBegin="MSB3188: "} - - - MSB3172: Unable to read manifest '{0}'. {1} - MSB3172: Unable to read manifest '{0}'. {1} - {StrBegin="MSB3172: "} - - - MSB3114: Could not find file '{0}' referenced by assembly '{1}'. - MSB3114: Could not find file '{0}' referenced by assembly '{1}'. - {StrBegin="MSB3114: "} - - - MSB3113: Could not find file '{0}'. - MSB3113: Could not find file '{0}'. - {StrBegin="MSB3113: "} - - - MSB3128: The ClickOnce manifests cannot be signed because they contain one or more references that are not hashed. - MSB3128: The ClickOnce manifests cannot be signed because they contain one or more references that are not hashed. - {StrBegin="MSB3128: "} - - - MSB3182: File name '{0}' exceeds {1} characters. - MSB3182: File name '{0}' exceeds {1} characters. - {StrBegin="MSB3182: "} - - - MSB3183: Reference '{0}' is an interop assembly requiring full trust. - MSB3183: Reference '{0}' is an interop assembly requiring full trust. - {StrBegin="MSB3183: "} - - - MSB3173: Unable to write manifest '{0}'. {1} - MSB3173: Unable to write manifest '{0}'. {1} - {StrBegin="MSB3173: "} - - - MSB3190: ClickOnce does not support the request execution level '{0}'. - MSB3190: ClickOnce does not support the request execution level '{0}'. - {StrBegin="MSB3190: "} - - - MSB3824: In order to build with .NET Core, resource inputs must be in .txt or .resx format. - MSB3824: In order to build with .NET Core, resource inputs must be in .txt or .resx format. - {StrBegin="MSB3824: "} - - - Input file "{0}" does not exist. - Input file "{0}" does not exist. - {0} is a filename on disk. - - - Input file "{0}" is newer than output file "{1}". - Input file "{0}" is newer than output file "{1}". - {0} and {1} are filenames on disk. - - - Linked input file "{0}" does not exist. - Linked input file "{0}" does not exist. - {0} is a filename on disk. - - - Linked input file "{0}" is newer than output file "{1}". - Linked input file "{0}" is newer than output file "{1}". - {0} and {1} are filenames on disk. - - - MSB3821: Couldn't process file {0} due to its being in the Internet or Restricted zone or having the mark of the web on the file. Remove the mark of the web if you want to process these files. - MSB3821: Couldn't process file {0} due to its being in the Internet or Restricted zone or having the mark of the web on the file. Remove the mark of the web if you want to process these files. - {StrBegin="MSB3821: "} "Internet zone", "Restricted zone", and "mark of the web" are Windows concepts that may have a specific translation. - - - Output file "{0}" does not exist. - Output file "{0}" does not exist. - {0} is a filename on disk. - - - MSB3822: Non-string resources require the System.Resources.Extensions assembly at runtime, but it was not found in this project's references. - MSB3822: Non-string resources require the System.Resources.Extensions assembly at runtime, but it was not found in this project's references. - {StrBegin="MSB3822: "} - - - MSB3823: Non-string resources require the property GenerateResourceUsePreserializedResources to be set to true. - MSB3823: Non-string resources require the property GenerateResourceUsePreserializedResources to be set to true. - {StrBegin="MSB3823: "} - - - MSB3552: Resource file "{0}" cannot be found. - MSB3552: Resource file "{0}" cannot be found. - {StrBegin="MSB3552: "} - - - MSB3553: Resource file "{0}" has an invalid name. {1} - MSB3553: Resource file "{0}" has an invalid name. {1} - {StrBegin="MSB3553: "}Appears if the input file name is so invalid we can't change the file extension on it. - - - MSB3554: Cannot write to the output file "{0}". {1} - MSB3554: Cannot write to the output file "{0}". {1} - {StrBegin="MSB3554: "} - - - Output file "{0}" is possibly corrupt and will be deleted and recreated. - Output file "{0}" is possibly corrupt and will be deleted and recreated. - - - - MSB3556: Only strings can be written to a .txt file, resource "{0}" is type {1}. - MSB3556: Only strings can be written to a .txt file, resource "{0}" is type {1}. - {StrBegin="MSB3556: "} - - - MSB3557: Error(s) generating strongly typed resources for file "{0}". - MSB3557: Error(s) generating strongly typed resources for file "{0}". - {StrBegin="MSB3557: "} - - - MSB3558: Unsupported file extension "{0}" on file "{1}". - MSB3558: Unsupported file extension "{0}" on file "{1}". - {StrBegin="MSB3558: "} - - - MSB3559: The code DOM provider for the "{0}" language failed. {1} - MSB3559: The code DOM provider for the "{0}" language failed. {1} - {StrBegin="MSB3559: "} - - - MSB3560: Could not delete the possibly corrupt output file "{0}". {1} - MSB3560: Could not delete the possibly corrupt output file "{0}". {1} - {StrBegin="MSB3560: "} - - - MSB3562: The "[strings]" tag is no longer necessary in text resources; please remove it. - MSB3562: The "[strings]" tag is no longer necessary in text resources; please remove it. - {StrBegin="MSB3562: "} - - - MSB3563: Unsupported square bracket keyword, "{0}". - MSB3563: Unsupported square bracket keyword, "{0}". - {StrBegin="MSB3563: "} - - - MSB3564: Resource line without an equals sign, "{0}". - MSB3564: Resource line without an equals sign, "{0}". - {StrBegin="MSB3564: "} - - - MSB3565: Resource line without a name. - MSB3565: Resource line without a name. - {StrBegin="MSB3565: "} - - - MSB3566: Unsupported or invalid escape character in resource "{0}", char '{1}'. - MSB3566: Unsupported or invalid escape character in resource "{0}", char '{1}'. - {StrBegin="MSB3566: "} - - - MSB3567: Could not generate property on class "{0}". - MSB3567: Could not generate property on class "{0}". - {StrBegin="MSB3567: "} - - - Could not load type {0} which is used in the .RESX file. Ensure that the necessary references have been added to your project. - Could not load type {0} which is used in the .RESX file. Ensure that the necessary references have been added to your project. - - - - MSB3568: Duplicate resource name "{0}" is not allowed, ignored. - MSB3568: Duplicate resource name "{0}" is not allowed, ignored. - {StrBegin="MSB3568: "} - - - MSB3569: Invalid hex value after '\u' in resource "{0}", value '{1}'. - MSB3569: Invalid hex value after '\u' in resource "{0}", value '{1}'. - {StrBegin="MSB3569: "} - - - MSB3570: Cannot write to the Strongly Typed Resource class file "{0}". {1} - MSB3570: Cannot write to the Strongly Typed Resource class file "{0}". {1} - {StrBegin="MSB3570: "} - - - MSB3572: StronglyTypedClassName, StronglyTypedNamespace, and/or StronglyTypedFileName parameters were passed in, but no StronglyTypedLanguage. If you want to create a strongly typed resource class, please specify a language. Otherwise remove all class, file name, and namespace parameters. - MSB3572: StronglyTypedClassName, StronglyTypedNamespace, and/or StronglyTypedFileName parameters were passed in, but no StronglyTypedLanguage. If you want to create a strongly typed resource class, please specify a language. Otherwise remove all class, file name, and namespace parameters. - {StrBegin="MSB3572: "} - - - MSB3573: The language for a strongly typed resource class was specified, but more than one source file was passed in. Please pass in only one source file at a time if you want to generate strongly typed resource classes. - MSB3573: The language for a strongly typed resource class was specified, but more than one source file was passed in. Please pass in only one source file at a time if you want to generate strongly typed resource classes. - {StrBegin="MSB3573: "} - - - {0} - {0} - - - - Processing resource file "{0}" into "{1}". - Processing resource file "{0}" into "{1}". - - - - Extracting .ResW files from assembly "{0}" into "{1}". - Extracting .ResW files from assembly "{0}" into "{1}". - - - - Skipping extracting .ResW files from assembly "{0}" because it declares non-supported framework "{1}". - Skipping extracting .ResW files from assembly "{0}" because it declares non-supported framework "{1}". - - - - Processing {0} resources from file "{1}". - Processing {0} resources from file "{1}". - - - - Creating strongly typed resources class "{0}". - Creating strongly typed resources class "{0}". - - - - No resources specified in "Sources". Skipping resource generation. - No resources specified in "Sources". Skipping resource generation. - - LOCALIZATION: Please don't localize "Sources" this is an item meta-data name. - - - - No resources are out of date with respect to their source files. Skipping resource generation. - No resources are out of date with respect to their source files. Skipping resource generation. - - - - Additional input "{0}" has been updated since the last build. Forcing regeneration of all resources. - Additional input "{0}" has been updated since the last build. Forcing regeneration of all resources. - - - - Creating a separate AppDomain because "NeverLockTypeAssemblies" evaluated to 'true'. - Creating a separate AppDomain because "NeverLockTypeAssemblies" evaluated to 'true'. - - - - Creating a separate AppDomain because while parsing "{0}" the serialized type "{1}" on line {2} could not be loaded. {3} - Creating a separate AppDomain because while parsing "{0}" the serialized type "{1}" on line {2} could not be loaded. {3} - - - - Creating a separate AppDomain because of error parsing "{0}". {1} - Creating a separate AppDomain because of error parsing "{0}". {1} - - - - Creating a separate AppDomain because of error parsing "{0}" on line {1}. {2} - Creating a separate AppDomain because of error parsing "{0}" on line {1}. {2} - - - - Creating a separate AppDomain because of resource "{0}" representing a serialized type "{1}" in "{2}" on line {3}. - Creating a separate AppDomain because of resource "{0}" representing a serialized type "{1}" in "{2}" on line {3}. - - - - Creating a separate AppDomain because of resource "{0}" of type "{1}" in "{2}" on line {3}. - Creating a separate AppDomain because of resource "{0}" of type "{1}" in "{2}" on line {3}. - - - - MSB3574: Did not recognize "{0}" as a managed assembly. - MSB3574: Did not recognize "{0}" as a managed assembly. - {StrBegin="MSB3574: "} - - - MSB3575: GenerateResource cannot write assemblies, only read from them. Cannot create assembly "{0}". - MSB3575: GenerateResource cannot write assemblies, only read from them. Cannot create assembly "{0}". - {StrBegin="MSB3575: "} - - - MSB3576: Creating the CultureInfo failed for assembly "{2}". Note the set of cultures supported is Operating System-dependent, and the Operating System has removed some cultures from time to time (ie, some Serbian cultures are split up in Windows 7). The culture may be a user-defined custom culture that we can't currently load on this machine. Exception info: {0}: {1} - MSB3576: Creating the CultureInfo failed for assembly "{2}". Note the set of cultures supported is Operating System-dependent, and the Operating System has removed some cultures from time to time (ie, some Serbian cultures are split up in Windows 7). The culture may be a user-defined custom culture that we can't currently load on this machine. Exception info: {0}: {1} - {StrBegin="MSB3576: "} - - - MSB3577: Two output file names resolved to the same output path: "{0}" - MSB3577: Two output file names resolved to the same output path: "{0}" - {StrBegin="MSB3577: "} - - - MSB3578: This assembly contains neutral resources corresponding to the culture "{0}". These resources will not be considered neutral in the output format as we are unable to preserve this information. The resources will continue to correspond to "{0}" in the output format. - MSB3578: This assembly contains neutral resources corresponding to the culture "{0}". These resources will not be considered neutral in the output format as we are unable to preserve this information. The resources will continue to correspond to "{0}" in the output format. - {StrBegin="MSB3578: "} - - - MSB3579: Couldn't find the linked resources file "{0}" listed in the assembly manifest. - MSB3579: Couldn't find the linked resources file "{0}" listed in the assembly manifest. - {StrBegin="MSB3579: "} - - - MSB3580: The assembly in file "{0}" has an assembly culture, indicating it is a satellite assembly for culture "{1}". But satellite assembly simple names must end in ".resources", while this one's simple name is "{2}". This is either a main assembly with the culture incorrectly set, or a satellite assembly with an incorrect simple name. - MSB3580: The assembly in file "{0}" has an assembly culture, indicating it is a satellite assembly for culture "{1}". But satellite assembly simple names must end in ".resources", while this one's simple name is "{2}". This is either a main assembly with the culture incorrectly set, or a satellite assembly with an incorrect simple name. - {StrBegin="MSB3580: "} - - - MSB3811: The assembly "{0}" says it is a satellite assembly, but it contains code. Main assemblies shouldn't specify the assembly culture in their manifest, and satellites should not contain code. This is almost certainly an error in your build process. - MSB3811: The assembly "{0}" says it is a satellite assembly, but it contains code. Main assemblies shouldn't specify the assembly culture in their manifest, and satellites should not contain code. This is almost certainly an error in your build process. - {StrBegin="MSB3811: "} - - - MSB3812: This assembly claims to be a satellite assembly, but doesn't contain any properly named .resources files as manifest resources. The name of the files should end in {0}.resources. There is probably a build-related problem with this assembly. - MSB3812: This assembly claims to be a satellite assembly, but doesn't contain any properly named .resources files as manifest resources. The name of the files should end in {0}.resources. There is probably a build-related problem with this assembly. - {StrBegin="MSB3812: "} - - - MSB3813: Invalid or unrecognized UltimateResourceFallbackLocation value in the NeutralResourcesLanguageAttribute for assembly "{1}". Location: "{0}" - MSB3813: Invalid or unrecognized UltimateResourceFallbackLocation value in the NeutralResourcesLanguageAttribute for assembly "{1}". Location: "{0}" - {StrBegin="MSB3813: "} - - - MSB3814: Main assembly "{1}" was built improperly. The manifest resource "{0}" ends in .en-US.resources, when it should end in .resources. Either rename it to something like foo.resources (and consider using the NeutralResourcesLanguageAttribute on the main assembly), or move it to a US English satellite assembly. - MSB3814: Main assembly "{1}" was built improperly. The manifest resource "{0}" ends in .en-US.resources, when it should end in .resources. Either rename it to something like foo.resources (and consider using the NeutralResourcesLanguageAttribute on the main assembly), or move it to a US English satellite assembly. - {StrBegin="MSB3814: "} - - - MSB3815: Satellite assembly "{2}" was built improperly. The manifest resource "{0}" will not be found by the ResourceManager. It must end in "{1}". - MSB3815: Satellite assembly "{2}" was built improperly. The manifest resource "{0}" will not be found by the ResourceManager. It must end in "{1}". - {StrBegin="MSB3815: "} - - - MSB3816: Loading assembly "{0}" failed. {1} - MSB3816: Loading assembly "{0}" failed. {1} - {StrBegin="MSB3816: "} - - - MSB3817: The assembly "{0}" does not have a NeutralResourcesLanguageAttribute on it. To be used in an app package, portable libraries must define a NeutralResourcesLanguageAttribute on their main assembly (ie, the one containing code, not a satellite assembly). - MSB3817: The assembly "{0}" does not have a NeutralResourcesLanguageAttribute on it. To be used in an app package, portable libraries must define a NeutralResourcesLanguageAttribute on their main assembly (ie, the one containing code, not a satellite assembly). - {StrBegin="MSB3817: "} - - - MSB3818: The GenerateResource task doesn't currently support simultaneously running as an external tool and extracting ResW files from assemblies. - MSB3818: The GenerateResource task doesn't currently support simultaneously running as an external tool and extracting ResW files from assemblies. - {StrBegin="MSB3818: "} - - - MSB3819: Cannot find assembly "{0}", which may contain managed resources that need to be included in this app package. Please ensure that this assembly exists. - MSB3819: Cannot find assembly "{0}", which may contain managed resources that need to be included in this app package. Please ensure that this assembly exists. - {StrBegin="MSB3819: "} - - - MSB3820: The path needed to store build-related temporary files is too long. Try your project in a shorter directory, or rename some of your resources. The full path was "{0}". - MSB3820: The path needed to store build-related temporary files is too long. Try your project in a shorter directory, or rename some of your resources. The full path was "{0}". - {StrBegin="MSB3820: "} - - - MSB3441: Cannot get assembly name for "{0}". {1} - MSB3441: Cannot get assembly name for "{0}". {1} - {StrBegin="MSB3441: "} - - - Choosing AnyCPU by default. - Choosing AnyCPU by default. - - - - Project '{0}' will build with platform: '{1}'. - Project '{0}' will build with platform: '{1}'. - - - - Found mapping '{0}'='{1}' in given lookup table: '{2}'. - Found mapping '{0}'='{1}' in given lookup table: '{2}'. - - - - MSB3983: The PlatformLookupTable '{0}' is in an invalid format and won't be used. The format should be 'A=B;C=D'. - MSB3983: The PlatformLookupTable '{0}' is in an invalid format and won't be used. The format should be 'A=B;C=D'. - {StrBegin="MSB3983: "} - - - Parsed lookup table:'{0}'. - Parsed lookup table:'{0}'. - - - - MSB3981: Could not determine what '{0}' should be built as. The project will be built without the Platform property set. - MSB3981: Could not determine what '{0}' should be built as. The project will be built without the Platform property set. - {StrBegin="MSB3981: "} - - - MSB3982: EnableDynamicPlatformResolution is true but referenced project '{0}' has no 'Platforms' metadata set. It will be built without a specified platform. - MSB3982: EnableDynamicPlatformResolution is true but referenced project '{0}' has no 'Platforms' metadata set. It will be built without a specified platform. - {StrBegin="MSB3982: "} - - - ProjectReference and current project have the same platform. - ProjectReference and current project have the same platform. - - - - Could not locate the expected version of the Microsoft Windows SDK. Looked for a location specified in the "{0}" value of the registry key "{1}". If your build process does not need the SDK then this can be ignored. Otherwise you can solve the problem by doing one of the following: 1) Install the Microsoft Windows SDK. 2) Install Visual Studio 2010. 3) Manually set the above registry key to the correct location. - Could not locate the expected version of the Microsoft Windows SDK. Looked for a location specified in the "{0}" value of the registry key "{1}". If your build process does not need the SDK then this can be ignored. Otherwise you can solve the problem by doing one of the following: 1) Install the Microsoft Windows SDK. 2) Install Visual Studio 2010. 3) Manually set the above registry key to the correct location. - - - - Found the Microsoft Windows SDK installed at "{0}". - Found the Microsoft Windows SDK installed at "{0}". - - - - MSB3971: The reference assemblies for "{0}" were not found. You might be using an older .NET SDK to target .NET 5.0 or higher. Update Visual Studio and/or your .NET SDK. - MSB3971: The reference assemblies for "{0}" were not found. You might be using an older .NET SDK to target .NET 5.0 or higher. Update Visual Studio and/or your .NET SDK. - {StrBegin="MSB3971: "} - - - Creating directory "{0}". - Creating directory "{0}". - - - - MSB3191: Unable to create directory "{0}". {1} - MSB3191: Unable to create directory "{0}". {1} - {StrBegin="MSB3191: "} - - - MSB3511: "{0}" is an invalid value for the "Importance" parameter. Valid values are: High, Normal and Low. - MSB3511: "{0}" is an invalid value for the "Importance" parameter. Valid values are: High, Normal and Low. - {StrBegin="MSB3511: "}UE: This message is shown when a user specifies a value for the importance attribute of Message which is not valid. - The importance enumeration is: High, Normal and Low. Specifying any other importance will result in this message being shown - LOCALIZATION: "Importance" should not be localized. - High should not be localized. - Normal should not be localized. - Low should not be localized. - - - Creating directory "{0}". - Creating directory "{0}". - - - - MSB3676: Could not move the file "{0}" to the destination file "{1}", because the destination is a folder instead of a file. To move the source file into a folder, consider using the DestinationFolder parameter instead of DestinationFiles. - MSB3676: Could not move the file "{0}" to the destination file "{1}", because the destination is a folder instead of a file. To move the source file into a folder, consider using the DestinationFolder parameter instead of DestinationFiles. - {StrBegin="MSB3676: "} - - - MSB3677: Unable to move file "{0}" to "{1}". {2} - MSB3677: Unable to move file "{0}" to "{1}". {2} - {StrBegin="MSB3677: "} - - - MSB3678: Both "{0}" and "{1}" were specified as input parameters in the project file. Only one must be provided. - MSB3678: Both "{0}" and "{1}" were specified as input parameters in the project file. Only one must be provided. - {StrBegin="MSB3678: "} - - - Moving file from "{0}" to "{1}". - Moving file from "{0}" to "{1}". - - - - MSB3679: No destination specified for Move. Please supply either "{0}" or "{1}". - MSB3679: No destination specified for Move. Please supply either "{0}" or "{1}". - {StrBegin="MSB3679: "} - - - MSB3680: The source file "{0}" does not exist. - MSB3680: The source file "{0}" does not exist. - {StrBegin="MSB3680: "} - - - MSB3681: The source file "{0}" is a directory. The "Move" task does not support moving directories. - MSB3681: The source file "{0}" is a directory. The "Move" task does not support moving directories. - {StrBegin="MSB3681: "} - - - MSB3203: The output path "{0}" cannot be rebased. {1} - MSB3203: The output path "{0}" cannot be rebased. {1} - {StrBegin="MSB3203: "}UE: This message is shown when the user asks the "MSBuild" task to rebase the paths of its output items relative to the project from where the "MSBuild" task is called (as opposed to the project(s) on which the "MSBuild" task is called), and one of the output item paths is invalid. LOCALIZATION: "{1}" is a localized message from a CLR/FX exception explaining the problem. - - - MSB3202: The project file "{0}" was not found. - MSB3202: The project file "{0}" was not found. - {StrBegin="MSB3202: "}UE: This message is shown when the user passes a non-existent project file to the MSBuild task, in the "Projects" parameter. - and they have not specified the SkipNonexistentProjects parameter, or it is set to false. - - - Skipping project "{0}" because it was not found. - Skipping project "{0}" because it was not found. - UE: This message is shown when the user passes a non-existent project file to the MSBuild task, in the "Projects" parameter, and they have specified the SkipNonexistentProjects parameter. - - - MSB3204: The project file "{0}" is in the ".vcproj" file format, which MSBuild no longer supports. Please convert the project by opening it in the Visual Studio IDE or running the conversion tool, or use MSBuild 3.5 or earlier to build it. - MSB3204: The project file "{0}" is in the ".vcproj" file format, which MSBuild no longer supports. Please convert the project by opening it in the Visual Studio IDE or running the conversion tool, or use MSBuild 3.5 or earlier to build it. - {StrBegin="MSB3204: "} LOC: ".vcproj" should not be localized - - - MSB3205: SkipNonexistentProject can only accept values of "True", "False" and "Build". - MSB3205: SkipNonexistentProject can only accept values of "True", "False" and "Build". - {StrBegin="MSB3205: "} LOC: "SkipNonexistentProject", "True", "False" and "Build" should not be localized - - - The MSBuild task is skipping the remaining projects because the StopOnFirstFailure parameter was set to true. - The MSBuild task is skipping the remaining projects because the StopOnFirstFailure parameter was set to true. - LOCALIZATION: Do not localize the words "MSBuild" or "StopOnFirstFailure". - - - The MSBuild task is skipping the remaining targets because the StopOnFirstFailure parameter was set to true. - The MSBuild task is skipping the remaining targets because the StopOnFirstFailure parameter was set to true. - LOCALIZATION: Do not localize the words "MSBuild" or "StopOnFirstFailure". - - - Overriding the BuildingInParallel property by setting it to false. This is due to the system being run in single process mode with StopOnFirstFailure set to true. - Overriding the BuildingInParallel property by setting it to false. This is due to the system being run in single process mode with StopOnFirstFailure set to true. - LOCALIZATION: Do not localize the words "MSBuild", "BuildingInParallel", or "StopOnFirstFailure". - - - StopOnFirstFailure will have no effect when the following conditions are all present: 1) The system is running in multiple process mode 2) The BuildInParallel property is true. 3) The RunEachTargetSeparately property is false. - StopOnFirstFailure will have no effect when the following conditions are all present: 1) The system is running in multiple process mode 2) The BuildInParallel property is true. 3) The RunEachTargetSeparately property is false. - LOCALIZATION: Do not localize the words "RunEachTargetSeparately", "BuildingInParallel", or "StopOnFirstFailure". - - - MSB3501: Could not read lines from file "{0}". {1} - MSB3501: Could not read lines from file "{0}". {1} - {StrBegin="MSB3501: "} - - - MSB3211: The assembly '{0}' is not registered for COM Interop. Please register it with regasm.exe /tlb. - MSB3211: The assembly '{0}' is not registered for COM Interop. Please register it with regasm.exe /tlb. - {StrBegin="MSB3211: "} - - - MSB3212: The assembly "{0}" could not be converted to a type library. {1} - MSB3212: The assembly "{0}" could not be converted to a type library. {1} - {StrBegin="MSB3212: "} - - - MSB3217: Cannot register assembly "{0}". {1} - MSB3217: Cannot register assembly "{0}". {1} - {StrBegin="MSB3217: "} - - - MSB3213: Cannot register type library "{0}". {1} - MSB3213: Cannot register type library "{0}". {1} - {StrBegin="MSB3213: "} - - - MSB3214: "{0}" does not contain any types that can be registered for COM Interop. - MSB3214: "{0}" does not contain any types that can be registered for COM Interop. - {StrBegin="MSB3214: "} - - - MSB3215: Cannot register assembly "{0}" - file doesn't exist. - MSB3215: Cannot register assembly "{0}" - file doesn't exist. - {StrBegin="MSB3215: "} - - - Registering assembly "{0}" for COM Interop. - Registering assembly "{0}" for COM Interop. - - - - Exporting and registering type library "{0}". - Exporting and registering type library "{0}". - - - - Type library "{0}" is up to date, skipping regeneration. - Type library "{0}" is up to date, skipping regeneration. - - - - MSB3216: Cannot register assembly "{0}" - access denied. Please make sure you're running the application as administrator. {1} - MSB3216: Cannot register assembly "{0}" - access denied. Please make sure you're running the application as administrator. {1} - {StrBegin="MSB3216: "} - - - MSB3231: Unable to remove directory "{0}". {1} - MSB3231: Unable to remove directory "{0}". {1} - {StrBegin="MSB3231: "} - - - Removing directory "{0}". - Removing directory "{0}". - - - - Directory "{0}" doesn't exist. Skipping. - Directory "{0}" doesn't exist. Skipping. - - - - No resources specified in "InputFiles". Skipping resource generation. - No resources specified in "InputFiles". Skipping resource generation. - - - - MSB3451: Neither SDKToolsPath '{0}' nor ToolPath '{1}' is a valid directory. One of these must be set. - MSB3451: Neither SDKToolsPath '{0}' nor ToolPath '{1}' is a valid directory. One of these must be set. - {StrBegin="MSB3451: "} - - - MSB3452: StronglyTypedClassName, StronglyTypedNamespace, and/or StronglyTypedFileName parameters were passed in, but no StronglyTypedLanguage. If you want to create a strongly typed resource class, please specify a language. Otherwise remove all class, file name, and namespace parameters. - MSB3452: StronglyTypedClassName, StronglyTypedNamespace, and/or StronglyTypedFileName parameters were passed in, but no StronglyTypedLanguage. If you want to create a strongly typed resource class, please specify a language. Otherwise remove all class, file name, and namespace parameters. - {StrBegin="MSB3452: "} - - - MSB3453: The language for a strongly typed resource class was specified, but more than one source file was passed in. Please pass in only one source file at a time if you want to generate strongly typed resource classes. - MSB3453: The language for a strongly typed resource class was specified, but more than one source file was passed in. Please pass in only one source file at a time if you want to generate strongly typed resource classes. - {StrBegin="MSB3453: "} - - - MSB3454: Tracker.exe is required to correctly incrementally generate resources in some circumstances, such as when building on a 64-bit OS using 32-bit MSBuild. This build requires Tracker.exe, but it could not be found. The task is looking for Tracker.exe beneath the {0} value of the registry key {1}. To solve the problem, either: 1) Install the Microsoft Windows SDK v7.0A or later. 2) Install Microsoft Visual Studio 2010. 3) Manually set the above registry key to the correct location. Alternatively, you can turn off incremental resource generation by setting the "TrackFileAccess" property to "false". - MSB3454: Tracker.exe is required to correctly incrementally generate resources in some circumstances, such as when building on a 64-bit OS using 32-bit MSBuild. This build requires Tracker.exe, but it could not be found. The task is looking for Tracker.exe beneath the {0} value of the registry key {1}. To solve the problem, either: 1) Install the Microsoft Windows SDK v7.0A or later. 2) Install Microsoft Visual Studio 2010. 3) Manually set the above registry key to the correct location. Alternatively, you can turn off incremental resource generation by setting the "TrackFileAccess" property to "false". - {StrBegin="MSB3454: "} - - - MSB3455: ResGen.exe may not run because the command line is {0} characters long, which exceeds the maximum length of the command. To fix this problem, please either (1) remove unnecessary assembly references, or (2) make the paths to those references shorter. - MSB3455: ResGen.exe may not run because the command line is {0} characters long, which exceeds the maximum length of the command. To fix this problem, please either (1) remove unnecessary assembly references, or (2) make the paths to those references shorter. - {StrBegin="MSB3455: "} - - - Assembly file '{0}' could not be opened -- PE image doesn't contain managed metadata. - Assembly file '{0}' could not be opened -- PE image doesn't contain managed metadata. - - - - AssemblyFoldersEx location: "{0}" - AssemblyFoldersEx location: "{0}" - - - - Considered AssemblyFoldersEx locations. - Considered AssemblyFoldersEx locations. - - - - There was a conflict between "{0}" and "{1}". - There was a conflict between "{0}" and "{1}". - - - - "{0}" was chosen because it had a higher version. - "{0}" was chosen because it had a higher version. - - - - "{0}" was chosen because it was primary and "{1}" was not. - "{0}" was chosen because it was primary and "{1}" was not. - - - - Consider app.config remapping of assembly "{0}" from Version "{1}" [{2}] to Version "{3}" [{4}] to solve conflict and get rid of warning. - Consider app.config remapping of assembly "{0}" from Version "{1}" [{2}] to Version "{3}" [{4}] to solve conflict and get rid of warning. - - UE and LOCALIZATION: - {1} and {3} are version numbers like 1.0.0.0 - {2} and {4} are file names correspending to {1} and {3} respectively - {0} is an assembly name with no version number like 'D, Culture=neutral, PublicKeyToken=aaaaaaaaaaaaaaaa' - - - - Considered "{0}", - but its name "{1}" - didn't match the expected name "{2}". - Considered "{0}", - but its name "{1}" - didn't match the expected name "{2}". - - - - Considered "{0}", but it didn't exist. - Considered "{0}", but it didn't exist. - - - - Considered treating "{0}" as a file name, but it didn't exist. - Considered treating "{0}" as a file name, but it didn't exist. - - - - Considered "{0}", which was not found in the GAC. - Considered "{0}", which was not found in the GAC. - - - - Considered "{0}", which existed but didn't have a valid identity. This may not be an assembly. - Considered "{0}", which existed but didn't have a valid identity. This may not be an assembly. - - - - Considered "{0}", which existed but had a processor architecture "{1}" which does not match the targeted processor architecture "{2}". - Considered "{0}", which existed but had a processor architecture "{1}" which does not match the targeted processor architecture "{2}". - - - - Dependency "{0}". - Dependency "{0}". - - - - {0} - {0} - - - - {0} - {0} - - - - {0} - {0} - - - - Found related file "{0}". - Found related file "{0}". - - - - Found satellite file "{0}". - Found satellite file "{0}". - - - - Found embedded scatter file "{0}". - Found embedded scatter file "{0}". - - - - {0} - {0} - - - - Ignoring "{0}" because it has a non-empty subtype "{1}". - Ignoring "{0}" because it has a non-empty subtype "{1}". - - - - Ignoring invalid Target Framework value "{0}". - Ignoring invalid Target Framework value "{0}". - - - - MSB3242: Conflict between mutually exclusive parameters. AutoUnify was 'true' and AppConfigFile was set. - MSB3242: Conflict between mutually exclusive parameters. AutoUnify was 'true' and AppConfigFile was set. - {StrBegin="MSB3242: "} - - - MSB3243: No way to resolve conflict between "{0}" and "{1}". Choosing "{0}" arbitrarily. - MSB3243: No way to resolve conflict between "{0}" and "{1}". Choosing "{0}" arbitrarily. - {StrBegin="MSB3243: "} - - - MSB3244: Could not find dependent files. {0} - MSB3244: Could not find dependent files. {0} - {StrBegin="MSB3244: "} - - - MSB3245: Could not resolve this reference. {0} If this reference is required by your code, you may get compilation errors. - MSB3245: Could not resolve this reference. {0} If this reference is required by your code, you may get compilation errors. - {StrBegin="MSB3245: "} - - - MSB3246: Resolved file has a bad image, no metadata, or is otherwise inaccessible. {0} - MSB3246: Resolved file has a bad image, no metadata, or is otherwise inaccessible. {0} - {StrBegin="MSB3246: "} - - - MSB3247: Found conflicts between different versions of the same dependent assembly. In Visual Studio, double-click this warning (or select it and press Enter) to fix the conflicts; otherwise, add the following binding redirects to the "runtime" node in the application configuration file: {0} - MSB3247: Found conflicts between different versions of the same dependent assembly. In Visual Studio, double-click this warning (or select it and press Enter) to fix the conflicts; otherwise, add the following binding redirects to the "runtime" node in the application configuration file: {0} - {StrBegin="MSB3247: "} - - - MSB3248: Parameter "{0}" has invalid value "{1}". {2} - MSB3248: Parameter "{0}" has invalid value "{1}". {2} - {StrBegin="MSB3248: "} - - - MSB3249: Application Configuration file "{0}" is invalid. {1} - MSB3249: Application Configuration file "{0}" is invalid. {1} - {StrBegin="MSB3249: "} - - - MSB3250: The file "{0}" will be ignored because it cannot be read. This file was either passed in to InstalledAssemblyTables or was found by searching the {1} folder in the TargetFrameworkDirectories. {2} - MSB3250: The file "{0}" will be ignored because it cannot be read. This file was either passed in to InstalledAssemblyTables or was found by searching the {1} folder in the TargetFrameworkDirectories. {2} - {StrBegin="MSB3250: "} - - - MSB3251: Could not resolve assembly {0}. The target framework required by this assembly ({1}) is higher than the project target framework. If this reference is required by your code, you may get compilation errors. - MSB3251: Could not resolve assembly {0}. The target framework required by this assembly ({1}) is higher than the project target framework. If this reference is required by your code, you may get compilation errors. - - - - MSB3252: The currently targeted framework "{1}" does not include the referenced assembly "{0}". To fix this, either (1) change the targeted framework for this project or (2) remove the referenced assembly from the project. - MSB3252: The currently targeted framework "{1}" does not include the referenced assembly "{0}". To fix this, either (1) change the targeted framework for this project or (2) remove the referenced assembly from the project. - {StrBegin="MSB3252: "} - - - MSB3253: The currently targeted framework "{2}" does not include "{1}" which the referenced assembly "{0}" depends on. This caused the referenced assembly to not resolve. To fix this, either (1) change the targeted framework for this project, or (2) remove the referenced assembly from the project. - MSB3253: The currently targeted framework "{2}" does not include "{1}" which the referenced assembly "{0}" depends on. This caused the referenced assembly to not resolve. To fix this, either (1) change the targeted framework for this project, or (2) remove the referenced assembly from the project. - {StrBegin="MSB3253: "} - - - MSB3254: The file "{0}" will be ignored because it cannot be read. This file was either passed in to InstalledAssemblySubsetTables or was found by searching the {1} folder in the TargetFrameworkDirectories. {2} - MSB3254: The file "{0}" will be ignored because it cannot be read. This file was either passed in to InstalledAssemblySubsetTables or was found by searching the {1} folder in the TargetFrameworkDirectories. {2} - {StrBegin="MSB3254: "} - - - MSB3255: Could not find any Target Framework Subset files in the Target Framework Directories or at the locations specified in the InstalledAssemblySubsetTables. - MSB3255: Could not find any Target Framework Subset files in the Target Framework Directories or at the locations specified in the InstalledAssemblySubsetTables. - {StrBegin="MSB3255: "} - - - MSB3256: No assemblies were read in from the redist lists. A TargetFramework profile exclusion list could not be generated. - MSB3256: No assemblies were read in from the redist lists. A TargetFramework profile exclusion list could not be generated. - {StrBegin="MSB3256: "} - - - MSB3257: The primary reference "{0}" could not be resolved because it has a higher version "{1}" than exists in the current target framework. The version found in the current target framework is "{2}". - MSB3257: The primary reference "{0}" could not be resolved because it has a higher version "{1}" than exists in the current target framework. The version found in the current target framework is "{2}". - {StrBegin="MSB3257: "} - - - MSB3258: The primary reference "{0}" could not be resolved because it has an indirect dependency on the .NET Framework assembly "{1}" which has a higher version "{2}" than the version "{3}" in the current target framework. - MSB3258: The primary reference "{0}" could not be resolved because it has an indirect dependency on the .NET Framework assembly "{1}" which has a higher version "{2}" than the version "{3}" in the current target framework. - {StrBegin="MSB3258: "} - - - MSB3259: Invalid parameter combination. Can only set either subset or profile parameters. Cannot set one or more subset parameters ("TargetFrameworkSubsets", "InstalledAssemblySubsetTables") and one or more profile parameters ("ProfileName", "FullFrameworkFolders", "FullFrameworkAssemblyTables") at the same time. - MSB3259: Invalid parameter combination. Can only set either subset or profile parameters. Cannot set one or more subset parameters ("TargetFrameworkSubsets", "InstalledAssemblySubsetTables") and one or more profile parameters ("ProfileName", "FullFrameworkFolders", "FullFrameworkAssemblyTables") at the same time. - {StrBegin="MSB3259: "} - - - MSB3260: Could not find any target framework profile redist files in the FullFrameworkFolders locations. - MSB3260: Could not find any target framework profile redist files in the FullFrameworkFolders locations. - {StrBegin="MSB3260: "} - - - MSB3261: The FrameworkDirectory metadata must be set on all items passed to the FullFrameworkAssemblyTables parameter. The item "{0}" did not have the metadata set. - MSB3261: The FrameworkDirectory metadata must be set on all items passed to the FullFrameworkAssemblyTables parameter. The item "{0}" did not have the metadata set. - {StrBegin="MSB3261: "} - - - MSB3262: When targeting a profile the ProfileName parameter and one of FullFrameworkFolders or FullFrameworkAssemblyTables must be set. - MSB3262: When targeting a profile the ProfileName parameter and one of FullFrameworkFolders or FullFrameworkAssemblyTables must be set. - {StrBegin="MSB3262: "} - - - MSB3263: The file "{0}" will be ignored because it cannot be read. This file was either passed in to FullFrameworkAssemblyTables or was found by searching the "{1}" folder in the FullFrameworkFolders. {2} - MSB3263: The file "{0}" will be ignored because it cannot be read. This file was either passed in to FullFrameworkAssemblyTables or was found by searching the "{1}" folder in the FullFrameworkFolders. {2} - {StrBegin="MSB3263: "} - - - MSB3267: The primary reference "{0}", which is a framework assembly, could not be resolved in the currently targeted framework. "{1}". To resolve this problem, either remove the reference "{0}" or retarget your application to a framework version which contains "{0}". - MSB3267: The primary reference "{0}", which is a framework assembly, could not be resolved in the currently targeted framework. "{1}". To resolve this problem, either remove the reference "{0}" or retarget your application to a framework version which contains "{0}". - {StrBegin="MSB3267: "} - - - MSB3268: The primary reference "{0}" could not be resolved because it has an indirect dependency on the framework assembly "{1}" which could not be resolved in the currently targeted framework. "{2}". To resolve this problem, either remove the reference "{0}" or retarget your application to a framework version which contains "{1}". - MSB3268: The primary reference "{0}" could not be resolved because it has an indirect dependency on the framework assembly "{1}" which could not be resolved in the currently targeted framework. "{2}". To resolve this problem, either remove the reference "{0}" or retarget your application to a framework version which contains "{1}". - {StrBegin="MSB3268: "} - - - MSB3269: Could not determine if resolved references are part of the targeted framework because of an error. "{0}" - MSB3269: Could not determine if resolved references are part of the targeted framework because of an error. "{0}" - {StrBegin="MSB3269: "} - - - MSB3270: There was a mismatch between the processor architecture of the project being built "{0}" and the processor architecture of the reference "{1}", "{2}". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project. - MSB3270: There was a mismatch between the processor architecture of the project being built "{0}" and the processor architecture of the reference "{1}", "{2}". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project. - {StrBegin="MSB3270: "} - - - MSB3271: There was a mismatch between the processor architecture of the project being built "{0}" and the processor architecture, "{1}", of the implementation file "{2}" for "{3}". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and implementation file, or choose a winmd file with an implementation file that has a processor architecture which matches the targeted processor architecture of your project. - MSB3271: There was a mismatch between the processor architecture of the project being built "{0}" and the processor architecture, "{1}", of the implementation file "{2}" for "{3}". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and implementation file, or choose a winmd file with an implementation file that has a processor architecture which matches the targeted processor architecture of your project. - {StrBegin="MSB3271: "} - - - MSB3272: There was a problem reading the implementation file "{0}". "{1}" - MSB3272: There was a problem reading the implementation file "{0}". "{1}" - {StrBegin="MSB3272: "} - - - Invalid PE header found. The implementation file will not used. - Invalid PE header found. The implementation file will not used. - This message can be used as the {1} in MSB3272 - - - MSB3273: Unknown processor architecture. The implementation file "{0}" for "{1}" had an ImageFileMachine value of "0x{2}". If you wish to use this implementation file make sure the "ResolveAssemblyWarnOrErrorOnTargetArchitectureMismatch" property in your project is set to "Warning" or "None". - MSB3273: Unknown processor architecture. The implementation file "{0}" for "{1}" had an ImageFileMachine value of "0x{2}". If you wish to use this implementation file make sure the "ResolveAssemblyWarnOrErrorOnTargetArchitectureMismatch" property in your project is set to "Warning" or "None". - {StrBegin="MSB3273: "} - - - MSB3274: The primary reference "{0}" could not be resolved because it was built against the "{1}" framework. This is a higher version than the currently targeted framework "{2}". - MSB3274: The primary reference "{0}" could not be resolved because it was built against the "{1}" framework. This is a higher version than the currently targeted framework "{2}". - {StrBegin="MSB3274: "} - - - MSB3275: The primary reference "{0}" could not be resolved because it has an indirect dependency on the assembly "{1}" which was built against the "{2}" framework. This is a higher version than the currently targeted framework "{3}". - MSB3275: The primary reference "{0}" could not be resolved because it has an indirect dependency on the assembly "{1}" which was built against the "{2}" framework. This is a higher version than the currently targeted framework "{3}". - {StrBegin="MSB3275: "} - - - MSB3276: Found conflicts between different versions of the same dependent assembly. Please set the "AutoGenerateBindingRedirects" property to true in the project file. For more information, see http://go.microsoft.com/fwlink/?LinkId=294190. - MSB3276: Found conflicts between different versions of the same dependent assembly. Please set the "AutoGenerateBindingRedirects" property to true in the project file. For more information, see http://go.microsoft.com/fwlink/?LinkId=294190. - {StrBegin="MSB3276: "} - - - MSB3277: Found conflicts between different versions of "{0}" that could not be resolved. -{1} - MSB3277: Found conflicts between different versions of "{0}" that could not be resolved. -{1} - {StrBegin="MSB3277: "} - - - {0} = '{1}' - {0} = '{1}' - - - - {0}: - {0}: - - - - This reference is not "CopyLocal" because it conflicted with another reference with the same name and lost the conflict. - This reference is not "CopyLocal" because it conflicted with another reference with the same name and lost the conflict. - - LOCALIZATION: Please don't localize "CopyLocal" this is an item meta-data name. - - - - The ImageRuntimeVersion for this reference is "{0}". - The ImageRuntimeVersion for this reference is "{0}". - - LOCALIZATION: Please don't localize "ImageRuntimeVersion" this is an item meta-data name. - - - - This reference is a WinMDFile. - This reference is a WinMDFile. - - LOCALIZATION: Please don't localize "WinMDFile" this is an item meta-data name. - - - - This reference is not "CopyLocal" because the CopyLocalDependenciesWhenParentReferenceInGac property is set to false and all the parent references for this reference are found in the GAC. - This reference is not "CopyLocal" because the CopyLocalDependenciesWhenParentReferenceInGac property is set to false and all the parent references for this reference are found in the GAC. - - LOCALIZATION: Please don't localize "CopyLocal" this is an item meta-data name. "CopyLocalDependenciesWhenParentReferenceInGac" is a property name. - - - - This reference is not "CopyLocal" because its types will be embedded into the target assembly. - This reference is not "CopyLocal" because its types will be embedded into the target assembly. - - LOCALIZATION: Please don't localize "CopyLocal" this is an item meta-data name. - - - - This reference is not "CopyLocal" because it's in a Frameworks directory. - This reference is not "CopyLocal" because it's in a Frameworks directory. - - LOCALIZATION: Please don't localize "CopyLocal" this is an item meta-data name. - - - - This reference is not "CopyLocal" because at least one source item had "Private" set to "false" and no source items had "Private" set to "true". - This reference is not "CopyLocal" because at least one source item had "Private" set to "false" and no source items had "Private" set to "true". - - LOCALIZATION: Please don't localize "CopyLocal", "Private", "false", "true". - - - - This reference is not "CopyLocal" because it's a prerequisite file. - This reference is not "CopyLocal" because it's a prerequisite file. - - LOCALIZATION: Please don't localize "CopyLocal" this is an item meta-data name. - - - - This reference is not "CopyLocal" because it's registered in the GAC. - This reference is not "CopyLocal" because it's registered in the GAC. - - LOCALIZATION: Please don't localize "CopyLocal" this is an item meta-data name. - - - - Primary reference "{0}". - Primary reference "{0}". - - - - Required by "{0}". - Required by "{0}". - - - - References which depend on "{0}" [{1}]. - References which depend on "{0}" [{1}]. - This will look like references which depend on "A, Version=2.0.0.0 PublicKey=4a4fded9gisujf" [a.dll]. - - - Unresolved primary reference with an item include of "{0}". - Unresolved primary reference with an item include of "{0}". - This messages is for a reference which could not be resolved, however we have its item spec and will display that. {0} will be somethign like System or A, Version=xxx - - - Project file item includes which caused reference "{0}". - Project file item includes which caused reference "{0}". - This will look like, Project file item includes which caused reference "a.dll". - - - Resolved file path is "{0}". - Resolved file path is "{0}". - - - - Reference found at search path location "{0}". - Reference found at search path location "{0}". - - - - For SearchPath "{0}". - For SearchPath "{0}". - - - - Using this version instead of original version "{0}" in "{2}" because of a binding redirect entry in the file "{1}". - Using this version instead of original version "{0}" in "{2}" because of a binding redirect entry in the file "{1}". - - - - Using this version instead of original version "{0}" in "{1}" because AutoUnify is 'true'. - Using this version instead of original version "{0}" in "{1}" because AutoUnify is 'true'. - - - - Due to a remapping entry in the currently targeted framework redist list, reference "{0}" was remapped to "{1}". - Due to a remapping entry in the currently targeted framework redist list, reference "{0}" was remapped to "{1}". - - - - Using this version instead of original version "{0}" in "{1}" because there is a more recent version of this framework file. - Using this version instead of original version "{0}" in "{1}" because there is a more recent version of this framework file. - - - - Unified Dependency "{0}". - Unified Dependency "{0}". - - - - Unified primary reference "{0}". - Unified primary reference "{0}". - - - - Could not find satellite assemblies for reference "{0}". {1} - Could not find satellite assemblies for reference "{0}". {1} - - - - A TargetFramework profile exclusion list will be generated. The exclusion list is a list of assemblies not in the profile. - A TargetFramework profile exclusion list will be generated. The exclusion list is a list of assemblies not in the profile. - - - - A TargetFramework profile exclusion list will not be generated. A full client name "{0}" was found in the TargetFrameworkSubsetNames list. - A TargetFramework profile exclusion list will not be generated. A full client name "{0}" was found in the TargetFrameworkSubsetNames list. - - - - No TargetFramework subset exclusion list will be generated. IgnoreDefaultInstalledAssemblySubsetTables is true and no additional profile files were passed in to InstalledAssemblySubsetTables. - No TargetFramework subset exclusion list will be generated. IgnoreDefaultInstalledAssemblySubsetTables is true and no additional profile files were passed in to InstalledAssemblySubsetTables. - - - - A TargetFramework profile exclusion list will be generated. - A TargetFramework profile exclusion list will be generated. - - - - No TargetFramework profile exclusion list will be generated. No TargetFrameworkSubsets were provided and no additional profile files were passed in to InstalledAssemblySubsetTables. - No TargetFramework profile exclusion list will be generated. No TargetFrameworkSubsets were provided and no additional profile files were passed in to InstalledAssemblySubsetTables. - - - - TargetFramework Profile List Information: - TargetFramework Profile List Information: - - - - TargetFramework Profile List Paths: - TargetFramework Profile List Paths: - - - - Redist List File Paths: - Redist List File Paths: - - - - Computed TargetFramework profile exclusion list assembly full names: - Computed TargetFramework profile exclusion list assembly full names: - - - - Path: "{0}" - Path: "{0}" - - - - The redist list file "{0}" has a null or empty Redist name in the FileList element. Make sure the Redist Name is not null or empty. - The redist list file "{0}" has a null or empty Redist name in the FileList element. Make sure the Redist Name is not null or empty. - - - - The AssemblyFolder config file ('{0}') specified in Microsoft.Common.CurrentVersion.targets was invalid. The error was: {1} - The AssemblyFolder config file ('{0}') specified in Microsoft.Common.CurrentVersion.targets was invalid. The error was: {1} - - - - COM Reference '{0}' is the interop assembly for ActiveX control '{1}' but was marked to be linked by the compiler with the /link flag. This COM reference will be treated as a reference and will not be linked. - COM Reference '{0}' is the interop assembly for ActiveX control '{1}' but was marked to be linked by the compiler with the /link flag. This COM reference will be treated as a reference and will not be linked. - - - - Adding a matching tlbimp reference for the aximp reference "{0}". - Adding a matching tlbimp reference for the aximp reference "{0}". - - - - Using cache file at "{0}". - Using cache file at "{0}". - - - - Creating new cache file at "{0}". - Creating new cache file at "{0}". - - - - MSB3281: The assembly "{0}" is not a valid assembly file. - MSB3281: The assembly "{0}" is not a valid assembly file. - {StrBegin="MSB3281: "} - - - MSB3282: Cannot access type library name for library "{0}". {1} - MSB3282: Cannot access type library name for library "{0}". {1} - {StrBegin="MSB3282: "} - - - MSB3283: Cannot find wrapper assembly for type library "{0}". Verify that (1) the COM component is registered correctly and (2) your target platform is the same as the bitness of the COM component. For example, if the COM component is 32-bit, your target platform must not be 64-bit. - MSB3283: Cannot find wrapper assembly for type library "{0}". Verify that (1) the COM component is registered correctly and (2) your target platform is the same as the bitness of the COM component. For example, if the COM component is 32-bit, your target platform must not be 64-bit. - {StrBegin="MSB3283: "} - - - MSB3284: Cannot get the file path for type library "{0}" version {1}.{2}. {3} - MSB3284: Cannot get the file path for type library "{0}" version {1}.{2}. {3} - {StrBegin="MSB3284: "} - - - MSB3285: Cannot get type library attributes for a dependent type library! - MSB3285: Cannot get type library attributes for a dependent type library! - {StrBegin="MSB3285: "} - - - MSB3286: Cannot load type library "{0}" version {1}.{2}. {3} - MSB3286: Cannot load type library "{0}" version {1}.{2}. {3} - {StrBegin="MSB3286: "} - - - MSB3287: Cannot load type library for reference "{0}". {1} - MSB3287: Cannot load type library for reference "{0}". {1} - {StrBegin="MSB3287: "} - - - MSB3302: Cannot retrieve information about a dependent type. - MSB3302: Cannot retrieve information about a dependent type. - {StrBegin="MSB3302: "} - - - MSB3300: Cannot specify values for both KeyFile and KeyContainer. - MSB3300: Cannot specify values for both KeyFile and KeyContainer. - {StrBegin="MSB3300: "} - - - MSB3301: DelaySign parameter is true, but no KeyFile or KeyContainer was specified. - MSB3301: DelaySign parameter is true, but no KeyFile or KeyContainer was specified. - {StrBegin="MSB3301: "} - - - MSB3288: COM reference "{0}" conflicts with reference "{1}" - the project references different type libraries with the same type library names. Ignoring reference "{0}". - MSB3288: COM reference "{0}" conflicts with reference "{1}" - the project references different type libraries with the same type library names. Ignoring reference "{0}". - {StrBegin="MSB3288: "} - - - MSB3290: Failed to create the wrapper assembly for type library "{0}". {1} - MSB3290: Failed to create the wrapper assembly for type library "{0}". {1} - {StrBegin="MSB3290: "} - - - MSB3291: Could not resolve dependent .NET assembly "{0}". Please make sure this assembly is included in the references section of the project file. - MSB3291: Could not resolve dependent .NET assembly "{0}". Please make sure this assembly is included in the references section of the project file. - {StrBegin="MSB3291: "} - - - MSB3292: Failed to remap ADO reference version {0}.{1} to version 2.7 - "{2}". - MSB3292: Failed to remap ADO reference version {0}.{1} to version 2.7 - "{2}". - {StrBegin="MSB3292: "} - - - MSB3303: Could not resolve COM reference "{0}" version {1}.{2}. {3} - MSB3303: Could not resolve COM reference "{0}" version {1}.{2}. {3} - {StrBegin="MSB3303: "} - - - MSB3293: Could not resolve dependent COM reference "{0}" version {1}.{2}. - MSB3293: Could not resolve dependent COM reference "{0}" version {1}.{2}. - {StrBegin="MSB3293: "} - - - MSB3294: Could not resolve dependent COM reference "{0}". - MSB3294: Could not resolve dependent COM reference "{0}". - {StrBegin="MSB3294: "} - - - MSB3304: Could not determine the dependencies of the COM reference "{0}". {1} - MSB3304: Could not determine the dependencies of the COM reference "{0}". {1} - {StrBegin="MSB3304: "} - - - MSB3305: Processing COM reference "{0}" from path "{1}". {2} - MSB3305: Processing COM reference "{0}" from path "{1}". {2} - {StrBegin="MSB3305: "} - - - Processing COM reference "{0}" from path "{1}". {2} - Processing COM reference "{0}" from path "{1}". {2} - - - - MSB3295: Failed to load an assembly. Please make sure you have disabled strong name verification for your public key if you want to generate delay signed wrappers. {0} - MSB3295: Failed to load an assembly. Please make sure you have disabled strong name verification for your public key if you want to generate delay signed wrappers. {0} - {StrBegin="MSB3295: "} - - - MSB3296: The specified COM reference meta-data for the reference "{1}" is missing or has an invalid value: "{0}". - MSB3296: The specified COM reference meta-data for the reference "{1}" is missing or has an invalid value: "{0}". - {StrBegin="MSB3296: "} - - - MSB3297: No COM references have been passed into the task, exiting. - MSB3297: No COM references have been passed into the task, exiting. - {StrBegin="MSB3297: "} - - - Remapping ADO reference version {0}.{1} to version 2.7. - Remapping ADO reference version {0}.{1} to version 2.7. - - - - Resolved COM reference dependency "{0}" version {1}.{2}: "{3}" - Resolved COM reference dependency "{0}" version {1}.{2}: "{3}" - - - - Resolved COM reference dependency "{0}": "{1}" - Resolved COM reference dependency "{0}": "{1}" - - - - Resolved COM reference for item "{0}": "{1}". - Resolved COM reference for item "{0}": "{1}". - - - - Resolving COM reference for item "{0}" with a wrapper "{1}". - Resolving COM reference for item "{0}" with a wrapper "{1}". - - - - Resolving COM reference dependency "{0}" version {1}.{2}. - Resolving COM reference dependency "{0}" version {1}.{2}. - - - - Determining dependencies of the COM reference "{0}". - Determining dependencies of the COM reference "{0}". - - - - MSB3298: The key container '{0}' does not contain a public/private key pair. - MSB3298: The key container '{0}' does not contain a public/private key pair. - {StrBegin="MSB3298: "} - - - MSB3299: The key file '{0}' does not contain a public/private key pair. - MSB3299: The key file '{0}' does not contain a public/private key pair. - {StrBegin="MSB3299: "} - - - {0} {1}.{2} - {0} {1}.{2} - - - - MSB3321: Importing key file "{0}" was canceled. - MSB3321: Importing key file "{0}" was canceled. - {StrBegin="MSB3321: "} - - - MSB3322: Unable to get MD5 checksum for the key file "{0}". {1} - MSB3322: Unable to get MD5 checksum for the key file "{0}". {1} - {StrBegin="MSB3322: "} - - - Error importing key - Error importing key - - - - MSB3323: Unable to find manifest signing certificate in the certificate store. - MSB3323: Unable to find manifest signing certificate in the certificate store. - {StrBegin="MSB3323: "} - - - MSB3324: Invalid key file name "{0}". {1} - MSB3324: Invalid key file name "{0}". {1} - {StrBegin="MSB3324: "} - - - MSB3325: Cannot import the following key file: {0}. The key file may be password protected. To correct this, try to import the certificate again or manually install the certificate to the Strong Name CSP with the following key container name: {1} - MSB3325: Cannot import the following key file: {0}. The key file may be password protected. To correct this, try to import the certificate again or manually install the certificate to the Strong Name CSP with the following key container name: {1} - {StrBegin="MSB3325: "} - - - MSB3326: Cannot import the following key file: {0}. The key file may be password protected. To correct this, try to import the certificate again or import the certificate manually into the current user’s personal certificate store. - MSB3326: Cannot import the following key file: {0}. The key file may be password protected. To correct this, try to import the certificate again or import the certificate manually into the current user’s personal certificate store. - {StrBegin="MSB3326: "} - - - MSB3327: Unable to find code signing certificate in the current user’s Windows certificate store. To correct this, either disable signing of the ClickOnce manifest or install the certificate into the certificate store. - MSB3327: Unable to find code signing certificate in the current user’s Windows certificate store. To correct this, either disable signing of the ClickOnce manifest or install the certificate into the certificate store. - {StrBegin="MSB3327: "} - - - MSB3331: Unable to apply publish properties for item "{0}". - MSB3331: Unable to apply publish properties for item "{0}". - {StrBegin="MSB3331: "} - - - Processing manifest file "{0}". - Processing manifest file "{0}". - - - - Attempting to resolve reference "{0}" on path(s): - Attempting to resolve reference "{0}" on path(s): - - - - MSB3341: Could not resolve reference "{0}". If this reference is required by your code, you may get compilation errors. - MSB3341: Could not resolve reference "{0}". If this reference is required by your code, you may get compilation errors. - {StrBegin="MSB3341: "} - - - MSB3582: Could not resolve project reference "{0}". - MSB3582: Could not resolve project reference "{0}". - {StrBegin="MSB3582: "} - - - Project reference "{0}" has not been resolved. - Project reference "{0}" has not been resolved. - - UE and LOCALIZATION: - This is not an error - we pass unresolved references to UnresolvedProjectReferences for further - processing in the .targets file. - - - - Resolving project reference "{0}". - Resolving project reference "{0}". - - - - Project reference "{0}" resolved as "{1}". - Project reference "{0}" resolved as "{1}". - - - - MSB3471: Non-existent reference "{0}" passed to the SGen task. - MSB3471: Non-existent reference "{0}" passed to the SGen task. - {StrBegin="MSB3471: "} - - - MSB3472: We were unable to delete the existing serializer "{0}" before creating a new one: {1} - MSB3472: We were unable to delete the existing serializer "{0}" before creating a new one: {1} - {StrBegin="MSB3472: "} - - - MSB3473: Path for "{0}" is invalid. {1} - MSB3473: Path for "{0}" is invalid. {1} - {StrBegin="MSB3473: "} - - - MSB3474: The task "{0}" is not supported on the .NET Core version of MSBuild. Use the Microsoft XML Serializer Generator package instead. See https://go.microsoft.com/fwlink/?linkid=858594 for more information. - MSB3474: The task "{0}" is not supported on the .NET Core version of MSBuild. Use the Microsoft XML Serializer Generator package instead. See https://go.microsoft.com/fwlink/?linkid=858594 for more information. - {StrBegin="MSB3474: "} - - - MSB3481: The signing certificate could not be located. Ensure that it is in the current user's personal store. - MSB3481: The signing certificate could not be located. Ensure that it is in the current user's personal store. - {StrBegin="MSB3481: "} - - - MSB3482: An error occurred while signing: {0} - MSB3482: An error occurred while signing: {0} - {StrBegin="MSB3482: "} - - - MSB3483: A warning occurred while signing: {0} - MSB3483: A warning occurred while signing: {0} - {StrBegin="MSB3483: "} - - - MSB3484: Signing target '{0}' could not be found. - MSB3484: Signing target '{0}' could not be found. - {StrBegin="MSB3484: "} - - - MSB3487: The signing certificate does not include private key information. - MSB3487: The signing certificate does not include private key information. - {StrBegin="MSB3487: "} - - - MSB3351: Unable to create a strong name key pair from key container '{0}'. - MSB3351: Unable to create a strong name key pair from key container '{0}'. - {StrBegin="MSB3351: "} - - - MSB3352: The specified key file '{0}' could not be read. - MSB3352: The specified key file '{0}' could not be read. - {StrBegin="MSB3352: "} - - - MSB3353: Public key necessary for delay signing was not specified. - MSB3353: Public key necessary for delay signing was not specified. - {StrBegin="MSB3353: "} - - - MSB4803: The task "{0}" is not supported on the .NET Core version of MSBuild. Please use the .NET Framework version of MSBuild. See https://aka.ms/msbuild/MSB4803 for further details. - MSB4803: The task "{0}" is not supported on the .NET Core version of MSBuild. Please use the .NET Framework version of MSBuild. See https://aka.ms/msbuild/MSB4803 for further details. - {StrBegin="MSB4803: "} - - - MSB3661: Invalid value '{0}' passed to the Transform property. - MSB3661: Invalid value '{0}' passed to the Transform property. - {StrBegin="MSB3661: "} - - - MSB3662: No input file has been passed to the task, exiting. - MSB3662: No input file has been passed to the task, exiting. - {StrBegin="MSB3662: "} - - - MSB3371: The file "{0}" cannot be created. {1} - MSB3371: The file "{0}" cannot be created. {1} - {StrBegin="MSB3371: "} - - - MSB3372: The file "{0}" cannot be made writable. {1} - MSB3372: The file "{0}" cannot be made writable. {1} - {StrBegin="MSB3372: "} - - - MSB3373: The attributes on file "{0}" cannot be restored to their original value. {1} - MSB3373: The attributes on file "{0}" cannot be restored to their original value. {1} - {StrBegin="MSB3373: "} - - - MSB3374: The last access/last write time on file "{0}" cannot be set. {1} - MSB3374: The last access/last write time on file "{0}" cannot be set. {1} - {StrBegin="MSB3374: "} - - - Creating "{0}" because "{1}" was specified. - Creating "{0}" because "{1}" was specified. - - - - MSB3375: The file "{0}" does not exist. - MSB3375: The file "{0}" does not exist. - {StrBegin="MSB3375: "} - - - MSB3376: The syntax of the Time parameter is incorrect. {0} - MSB3376: The syntax of the Time parameter is incorrect. {0} - {StrBegin="MSB3376: "} - - - Touching "{0}". - Touching "{0}". - - - - MSB3396: The "{0}" task needs either an assembly path or state file path. - MSB3396: The "{0}" task needs either an assembly path or state file path. - {StrBegin="MSB3396: "} - - - MSB3395: Cannot unregister assembly "{0}". {1} - MSB3395: Cannot unregister assembly "{0}". {1} - {StrBegin="MSB3395: "} - - - MSB3391: "{0}" does not contain any types that can be unregistered for COM Interop. - MSB3391: "{0}" does not contain any types that can be unregistered for COM Interop. - {StrBegin="MSB3391: "} - - - MSB3392: Cannot unregister assembly "{0}" - access denied. Please make sure you're running the application as administrator. {1} - MSB3392: Cannot unregister assembly "{0}" - access denied. Please make sure you're running the application as administrator. {1} - {StrBegin="MSB3392: "} - - - MSB3393: Cannot unregister assembly "{0}" - file doesn't exist. - MSB3393: Cannot unregister assembly "{0}" - file doesn't exist. - {StrBegin="MSB3393: "} - - - Unregistering assembly "{0}" for COM Interop. - Unregistering assembly "{0}" for COM Interop. - - - - Unregistering type library "{0}". - Unregistering type library "{0}". - - - - MSB3397: Cannot unregister type library "{0}" - cannot load file, check to make sure it's a valid type library. - MSB3397: Cannot unregister type library "{0}" - cannot load file, check to make sure it's a valid type library. - {StrBegin="MSB3397: "} - - - Cannot unregister type library "{0}" - file doesn't exist. - Cannot unregister type library "{0}" - file doesn't exist. - - - - MSB3394: Type library "{0}" is not registered, cannot unregister. - MSB3394: Type library "{0}" is not registered, cannot unregister. - {StrBegin="MSB3394: "} - - - Did not unzip from file "{0}" to file "{1}" because the "{2}" parameter was set to "{3}" in the project and the files' sizes and timestamps match. - Did not unzip from file "{0}" to file "{1}" because the "{2}" parameter was set to "{3}" in the project and the files' sizes and timestamps match. - - - - Did not unzip file "{0}" because it didn't match the include filter or because it matched the exclude filter. - Did not unzip file "{0}" because it didn't match the include filter or because it matched the exclude filter. - - - - MSB3931: Failed to unzip to directory "{0}" because it could not be created. {1} - MSB3931: Failed to unzip to directory "{0}" because it could not be created. {1} - {StrBegin="MSB3931: "} - - - MSB3936: Failed to open unzip file "{0}" to "{1}". {2} - MSB3936: Failed to open unzip file "{0}" to "{1}". {2} - {StrBegin="MSB3936: "} - - - MSB3935: Failed to unzip file "{0}" because destination file "{1}" is read-only and could not be made writable. {2} - MSB3935: Failed to unzip file "{0}" because destination file "{1}" is read-only and could not be made writable. {2} - {StrBegin="MSB3935: "} - - - MSB3933: Failed to open zip file "{0}". {1} - MSB3933: Failed to open zip file "{0}". {1} - {StrBegin="MSB3933: "} - - - MSB3934: Failed to open unzip file "{0}" to "{1}" because it is outside the destination directory. - MSB3934: Failed to open unzip file "{0}" to "{1}" because it is outside the destination directory. - {StrBegin="MSB3934: "} - - - MSB3932: Failed to unzip file "{0}" because the file does not exist or is inaccessible. - MSB3932: Failed to unzip file "{0}" because the file does not exist or is inaccessible. - {StrBegin="MSB3932: "} - - - MSB3937: Failed to parse pattern "{0}" because it contains an invalid path character. - MSB3937: Failed to parse pattern "{0}" because it contains an invalid path character. - {StrBegin="MSB3937: "} - - - MSB3938: Failed to parse pattern "{0}" because it contains a property reference which isn't supported. - MSB3938: Failed to parse pattern "{0}" because it contains a property reference which isn't supported. - {StrBegin="MSB3938: "} - - - Unzipping file "{0}" to "{1}". - Unzipping file "{0}" to "{1}". - - - - MSB3401: "{1}" is an invalid value for the "{0}" parameter. The valid values are: {2} - MSB3401: "{1}" is an invalid value for the "{0}" parameter. The valid values are: {2} - {StrBegin="MSB3401: "} - - - MSB3402: There was an error creating the pdb file "{0}". {1} - MSB3402: There was an error creating the pdb file "{0}". {1} - {StrBegin="MSB3402: "} - - - "{1}" is an invalid value for the "{0}" parameter. - "{1}" is an invalid value for the "{0}" parameter. - - - - MSB3952: File hash mismatch. Expected {0} to have a {1} file hash of {2}, but it was {3}. - MSB3952: File hash mismatch. Expected {0} to have a {1} file hash of {2}, but it was {3}. - {StrBegin="MSB3952: "} - - - Could not convert the value for parameter "{0}" to the inferred type "{1}". The value will be treated as a string. {2} - Could not convert the value for parameter "{0}" to the inferred type "{1}". The value will be treated as a string. {2} - - - - MSB3716: The parameter value "{0}" could not be converted to "{1}". {2} - MSB3716: The parameter value "{0}" could not be converted to "{1}". {2} - {StrBegin="MSB3716: "} - - - Could not infer the type of parameter "{0}" because the attribute type is unknown. The value will be treated as a string. - Could not infer the type of parameter "{0}" because the attribute type is unknown. The value will be treated as a string. - - - - Multiple attribute constructors were found for type inferencing. - Multiple attribute constructors were found for type inferencing. - - - - MSB3715: The type "{0}" was not found. - MSB3715: The type "{0}" was not found. - {StrBegin="MSB3715: "} - - - MSB3491: Could not write lines to file "{0}". {1} - MSB3491: Could not write lines to file "{0}". {1} - {StrBegin="MSB3491: "} - - - MSB3492: Could not read existing file "{0}" to determine whether its contents are up to date. Overwriting it. - MSB3492: Could not read existing file "{0}" to determine whether its contents are up to date. Overwriting it. - {StrBegin="MSB3492: "} - - - Skipping write to file "{0}" because content would not change. - Skipping write to file "{0}" because content would not change. - - - - MSB3642: The Target Framework Moniker "{0}" is invalid. "{1}" - MSB3642: The Target Framework Moniker "{0}" is invalid. "{1}" - {StrBegin="MSB3642: "} - - - MSB3643: There was an error generating reference assembly paths based on the TargetFrameworkMoniker "{0}". {1} - MSB3643: There was an error generating reference assembly paths based on the TargetFrameworkMoniker "{0}". {1} - {StrBegin="MSB3643: "} - - - MSB3644: The reference assemblies for {0} were not found. To resolve this, install the Developer Pack (SDK/Targeting Pack) for this framework version or retarget your application. You can download .NET Framework Developer Packs at https://aka.ms/msbuild/developerpacks - MSB3644: The reference assemblies for {0} were not found. To resolve this, install the Developer Pack (SDK/Targeting Pack) for this framework version or retarget your application. You can download .NET Framework Developer Packs at https://aka.ms/msbuild/developerpacks - {StrBegin="MSB3644: "} - - - MSB3645: .NET Framework v3.5 Service Pack 1 was not found. In order to target "{0}", .NET Framework v3.5 Service Pack 1 or later must be installed. - MSB3645: .NET Framework v3.5 Service Pack 1 was not found. In order to target "{0}", .NET Framework v3.5 Service Pack 1 or later must be installed. - {StrBegin="MSB3645: "} - - - MSB3762: No references were passed to the task. References to at least mscorlib and Windows.Foundation are required. - MSB3762: No references were passed to the task. References to at least mscorlib and Windows.Foundation are required. - {StrBegin="MSB3762: "} - - - MSB3724: Unable to create Xaml task. Duplicate property name '{0}'. - MSB3724: Unable to create Xaml task. Duplicate property name '{0}'. - {StrBegin="MSB3724: "} - - - MSB3686: Unable to create Xaml task. Compilation failed. {0} - MSB3686: Unable to create Xaml task. Compilation failed. {0} - {StrBegin="MSB3686: "} - - - MSB3687: Unable to parse Xaml rule. {0} - MSB3687: Unable to parse Xaml rule. {0} - {StrBegin="MSB3687: "} - - - MSB3688: Unable to create Xaml task. File not found: {0}. - MSB3688: Unable to create Xaml task. File not found: {0}. - {StrBegin="MSB3688: "} - - - MSB3689: Unable to execute Xaml task. If the CommandLineTemplate task parameter is not specified, then the ToolName attribute must be specified in the Rule or the ToolExe task parameter must be set. - MSB3689: Unable to execute Xaml task. If the CommandLineTemplate task parameter is not specified, then the ToolName attribute must be specified in the Rule or the ToolExe task parameter must be set. - {StrBegin="MSB3689: "} - - - MSB3690: Unable to create Xaml task. The Rule "{0}" was not found. - MSB3690: Unable to create Xaml task. The Rule "{0}" was not found. - {StrBegin="MSB3690: "} - - - MSB3691: Unable to create Xaml task. The root object was not of type ProjectSchemaDefinitions. - MSB3691: Unable to create Xaml task. The root object was not of type ProjectSchemaDefinitions. - {StrBegin="MSB3691: "} - - - MSB3692: Unable to create Xaml task. The <UsingTask> does not contain a <Task> definition. - MSB3692: Unable to create Xaml task. The <UsingTask> does not contain a <Task> definition. - {StrBegin="MSB3692: "} - - - MSB3693: Unable to execute Xaml task. The value "{1}" specified for task parameter "{0}" is not valid. - MSB3693: Unable to execute Xaml task. The value "{1}" specified for task parameter "{0}" is not valid. - {StrBegin="MSB3693: "} - - - MSB3694: Unable to create Xaml task. The EnumValue "{1}" on EnumProperty "{0}" is missing the SwitchValue attribute. - MSB3694: Unable to create Xaml task. The EnumValue "{1}" on EnumProperty "{0}" is missing the SwitchValue attribute. - {StrBegin="MSB3694: "} - - - MSB3721: The command "{0}" exited with code {1}. - MSB3721: The command "{0}" exited with code {1}. - {StrBegin="MSB3721: "} - - - MSB3722: The command "{0}" exited with code {1}. Please verify that you have sufficient rights to run this command. - MSB3722: The command "{0}" exited with code {1}. Please verify that you have sufficient rights to run this command. - {StrBegin="MSB3722: "} - - - MSB3723: The parameter "{0}" requires missing parameter "{1}" to be set. - MSB3723: The parameter "{0}" requires missing parameter "{1}" to be set. - {StrBegin="MSB3723: "} - - - MSB3701: Unable to load arguments for the XslTransformation task. {0} - MSB3701: Unable to load arguments for the XslTransformation task. {0} - {StrBegin="MSB3701: "} - - - MSB3705: XslCompiledDllPath is not supported when building with .NET Core. - MSB3705: XslCompiledDllPath is not supported when building with .NET Core. - {StrBegin="MSB3705: "} - - - MSB3702: Unable to process the XsltParameters argument for the XslTransformation task. {0} - MSB3702: Unable to process the XsltParameters argument for the XslTransformation task. {0} - {StrBegin="MSB3702: "} - - - MSB3703: Unable to execute transformation. {0} - MSB3703: Unable to execute transformation. {0} - {StrBegin="MSB3703: "} - - - Only one of XmlContent or XmlInputPaths arguments can be set. - Only one of XmlContent or XmlInputPaths arguments can be set. - - - - One of XmlContent or XmlInputPaths arguments must be set. - One of XmlContent or XmlInputPaths arguments must be set. - - - - Only one of XslContent, XslInputPath or XslCompiledDllPath arguments can be set. - Only one of XslContent, XslInputPath or XslCompiledDllPath arguments can be set. - - - - One of XslContent, XslInputPath and XslCompiledDllPath arguments must be set. - One of XslContent, XslInputPath and XslCompiledDllPath arguments must be set. - - - - MSB3704: Unable to load the specified Xslt. {0} - MSB3704: Unable to load the specified Xslt. {0} - {StrBegin="MSB3704: "} - - - When specifying assembly "{0}", you must specify the type as well. - When specifying assembly "{0}", you must specify the type as well. - - - - The specified Xslt Parameter doesn't have attribute "{0}". - The specified Xslt Parameter doesn't have attribute "{0}". - - - - The specified Xslt Parameter attribute is not a well-formed XML fragment. - The specified Xslt Parameter attribute is not a well-formed XML fragment. - - - - The usage of the document() method and embedded scripts is prohibited by default, due to risks of foreign code execution. If "{0}" is a trusted source that requires those constructs, please set the "UseTrustedSettings" parameter to "true" to allow their execution. - The usage of the document() method and embedded scripts is prohibited by default, due to risks of foreign code execution. If "{0}" is a trusted source that requires those constructs, please set the "UseTrustedSettings" parameter to "true" to allow their execution. - - - - MSB3731: Unable to process the Namespaces argument for the XmlPoke task. {0} - MSB3731: Unable to process the Namespaces argument for the XmlPoke task. {0} - {StrBegin="MSB3731: "} - - - The specified Namespaces attribute doesn't have attribute "{0}". - The specified Namespaces attribute doesn't have attribute "{0}". - - - - The specified Namespaces attribute is not a well-formed XML fragment. - The specified Namespaces attribute is not a well-formed XML fragment. - - - - Replaced "{0}" with "{1}". - Replaced "{0}" with "{1}". - - - - Made {0} replacement(s). - Made {0} replacement(s). - - - - MSB3732: Unable to set XPath expression's Context. {0} - MSB3732: Unable to set XPath expression's Context. {0} - {StrBegin="MSB3732: "} - - - MSB3733: Input file "{0}" cannot be opened. {1} - MSB3733: Input file "{0}" cannot be opened. {1} - {StrBegin="MSB3733: "} - - - MSB3734: XPath Query "{0}" cannot be loaded. {1} - MSB3734: XPath Query "{0}" cannot be loaded. {1} - {StrBegin="MSB3734: "} - - - MSB3735: Error while executing poke operation with the Value parameter "{0}". {1} - MSB3735: Error while executing poke operation with the Value parameter "{0}". {1} - {StrBegin="MSB3735: "} - - - MSB3741: Unable to load arguments for the XmlPeek task. {0} - MSB3741: Unable to load arguments for the XmlPeek task. {0} - {StrBegin="MSB3741: "} - - - MSB3742: Unable to process the Namespaces argument for the XmlPeek task. {0} - MSB3742: Unable to process the Namespaces argument for the XmlPeek task. {0} - {StrBegin="MSB3742: "} - - - MSB3743: Unable to set XPath expression's Context. {0} - MSB3743: Unable to set XPath expression's Context. {0} - {StrBegin="MSB3743: "} - - - Only one of XmlContent or XmlInputPath arguments can be set. - Only one of XmlContent or XmlInputPath arguments can be set. - - - - One of XmlContent or XmlInputPath arguments must be set. - One of XmlContent or XmlInputPath arguments must be set. - - - - The specified Namespaces attribute does not have attribute "{0}". - The specified Namespaces attribute does not have attribute "{0}". - - - - The specified Namespaces attribute is not a well-formed XML fragment. - The specified Namespaces attribute is not a well-formed XML fragment. - - - - Found "{0}". - Found "{0}". - - - - The specified XPath query did not capture any nodes. - The specified XPath query did not capture any nodes. - - - - MSB3711: At least one of OutputFile or OutputDirectory must be provided. - MSB3711: At least one of OutputFile or OutputDirectory must be provided. - {StrBegin="MSB3711: "} - - - MSB3712: Code for the language "{0}" could not be generated. {1} - MSB3712: Code for the language "{0}" could not be generated. {1} - {StrBegin="MSB3712: "} - - - MSB3713: The file "{0}" could not be created. {1} - MSB3713: The file "{0}" could not be created. {1} - {StrBegin="MSB3713: "} - - - MSB3714: The parameter "{0}" was supplied, but not all previously numbered parameters. - MSB3714: The parameter "{0}" was supplied, but not all previously numbered parameters. - {StrBegin="MSB3714: "} - - - No output file was written because no code was specified to create. - No output file was written because no code was specified to create. - - - - Emitted specified code into "{0}". - Emitted specified code into "{0}". - - - - Generated by the MSBuild WriteCodeFragment class. - Generated by the MSBuild WriteCodeFragment class. - - - - MSB3751: The <Code> element is missing for the "{0}" task. This element is required. - MSB3751: The <Code> element is missing for the "{0}" task. This element is required. - {StrBegin="MSB3751: "} <Code> should not be localized it is the name of an xml element - - - MSB3752: The "{0}" attribute has been set but is empty. If the "{0}" attribute is set it must not be empty. - MSB3752: The "{0}" attribute has been set but is empty. If the "{0}" attribute is set it must not be empty. - {StrBegin="MSB3752: "} - - - MSB3753: The task could not be instantiated because it does not implement the ITask interface. Make sure the task implements the Microsoft.Build.Framework.ITask interface. - MSB3753: The task could not be instantiated because it does not implement the ITask interface. Make sure the task implements the Microsoft.Build.Framework.ITask interface. - {StrBegin="MSB3753: "} - - - MSB3754: The reference assembly "{0}" is invalid. "{1}" - MSB3754: The reference assembly "{0}" is invalid. "{1}" - {StrBegin="MSB3754: "} - - - MSB3755: Could not find reference "{0}". If this reference is required by your code, you may get compilation errors. - MSB3755: Could not find reference "{0}". If this reference is required by your code, you may get compilation errors. - {StrBegin="MSB3755: "} - - - MSB3756: The element <{0}> is not a valid child of the <{1}> element. Valid child elements are <Code>, <Reference>, and <Using>. - MSB3756: The element <{0}> is not a valid child of the <{1}> element. Valid child elements are <Code>, <Reference>, and <Using>. - {StrBegin="MSB3756: "} - - - MSB3757: Only one <Code> element can be specified. - MSB3757: Only one <Code> element can be specified. - {StrBegin="MSB3757: "} - - - MSB3758: An error has occurred during compilation. {0} - MSB3758: An error has occurred during compilation. {0} - {StrBegin="MSB3758: "} - - - The task name "{0}" could not be found. - The task name "{0}" could not be found. - - - - The source file for this compilation can be found at: "{0}" - The source file for this compilation can be found at: "{0}" - - - - The reference assembly "{0}" is a metadata only assembly. - The reference assembly "{0}" is a metadata only assembly. - - - - Searching for SDK "{0}": - Searching for SDK "{0}": - - - - Found at search location "{0}". - Found at search location "{0}". - - - - There was a problem reading the SDK manifest file "{0}". {1} - There was a problem reading the SDK manifest file "{0}". {1} - - - - Reading SDK manifest file "{0}". - Reading SDK manifest file "{0}". - - - - Targeted configuration and architecture "{0}|{1}" - Targeted configuration and architecture "{0}|{1}" - - - - Has a platform identity of "{0}". - Has a platform identity of "{0}". - - - - Could not find "FrameworkIdentity" attribute "{0}" in the SDK manifest. - Could not find "FrameworkIdentity" attribute "{0}" in the SDK manifest. - - - - No FrameworkIdentity attributes were found in the SDK manifest, treating this SDK as a non-framework SDK. - No FrameworkIdentity attributes were found in the SDK manifest, treating this SDK as a non-framework SDK. - - - - No "APPX" attributes indicating app package locations were found in the SDK manifest. If an app package is required at runtime the project may not run. - No "APPX" attributes indicating app package locations were found in the SDK manifest. If an app package is required at runtime the project may not run. - - - - Found "FrameworkIdentity" attribute "{0}" in the SDK manifest. - Found "FrameworkIdentity" attribute "{0}" in the SDK manifest. - - - - Found "APPX" location attribute "{0}" in the SDK manifest. - Found "APPX" location attribute "{0}" in the SDK manifest. - - - - Updating the "{0}" architecture "APPX" location from "{1}" to "{2}". - Updating the "{0}" architecture "APPX" location from "{1}" to "{2}". - - - - Cannot resolve "SDKReference" items because no installed SDK locations were passed into the property "InstalledSdks". - Cannot resolve "SDKReference" items because no installed SDK locations were passed into the property "InstalledSdks". - "SDKReference" and "InstalledSDKs" are property names on the task and should not be localized - - - MSB3773: The SDK "{0}" cannot be referenced alongside SDK(s) {1}, as they all belong to the same SDK product Family "{2}". Please consider removing references to other SDKs of the same product family. - MSB3773: The SDK "{0}" cannot be referenced alongside SDK(s) {1}, as they all belong to the same SDK product Family "{2}". Please consider removing references to other SDKs of the same product family. - {StrBegin="MSB3773: "} - - - MSB3774: Could not find SDK "{0}". - MSB3774: Could not find SDK "{0}". - {StrBegin="MSB3774: "} - - - MSB3775: There was an error resolving the SDK "{0}". {1} - MSB3775: There was an error resolving the SDK "{0}". {1} - {StrBegin="MSB3775: "} "{0}" will be the root location which could not be searched. Ie (c:\program files\sdks\..) - - - MSB3776: The SDK Reference "{0}" is incorrectly formatted. It must be in the following format "<SDKName>, Version=<SDKVersion>. For example: "MySDK, Version=2.0" - MSB3776: The SDK Reference "{0}" is incorrectly formatted. It must be in the following format "<SDKName>, Version=<SDKVersion>. For example: "MySDK, Version=2.0" - {StrBegin="MSB3776: "} - - - MSB3777: "FrameworkIdentity" attributes were found in the SDK manifest file "{0}", however none of the attributes matched the targeted configuration and architecture "{1} | {2}" and no "FrameworkIdentity" attribute without configuration and architecture could be found. If this project is to be packaged, packaging will fail. - MSB3777: "FrameworkIdentity" attributes were found in the SDK manifest file "{0}", however none of the attributes matched the targeted configuration and architecture "{1} | {2}" and no "FrameworkIdentity" attribute without configuration and architecture could be found. If this project is to be packaged, packaging will fail. - {StrBegin="MSB3777: "} - - - MSB3778: "APPX" attributes were found in the SDK manifest file "{0}" however none of the attributes matched the targeted configuration and architecture "{1} | {2}" and no "APPX" attribute without configuration and architecture could be found. If an app package is required then the project will fail at runtime. - MSB3778: "APPX" attributes were found in the SDK manifest file "{0}" however none of the attributes matched the targeted configuration and architecture "{1} | {2}" and no "APPX" attribute without configuration and architecture could be found. If an app package is required then the project will fail at runtime. - {StrBegin="MSB3778: "} - - - MSB3779: The processor architecture of the project being built "{0}" is not supported by the referenced SDK "{1}". Please consider changing the targeted processor architecture of your project (in Visual Studio this can be done through the Configuration Manager) to one of the architectures supported by the SDK: "{2}". - MSB3779: The processor architecture of the project being built "{0}" is not supported by the referenced SDK "{1}". Please consider changing the targeted processor architecture of your project (in Visual Studio this can be done through the Configuration Manager) to one of the architectures supported by the SDK: "{2}". - {StrBegin="MSB3779: "} - - - MSB3780: The SDK "{0}" cannot be referenced alongside SDK(s) {1}, because only one version of the SDK can be referenced from a project. Please consider removing references to the other SDKs. - MSB3780: The SDK "{0}" cannot be referenced alongside SDK(s) {1}, because only one version of the SDK can be referenced from a project. Please consider removing references to the other SDKs. - {StrBegin="MSB3780: "} - - - MSB3781: The SDK "{0}" depends on the following SDK(s) {1}, which have not been added to the project or were not found. Please ensure that you add these dependencies to your project or you may experience runtime issues. You can add dependencies to your project through the Reference Manager. - MSB3781: The SDK "{0}" depends on the following SDK(s) {1}, which have not been added to the project or were not found. Please ensure that you add these dependencies to your project or you may experience runtime issues. You can add dependencies to your project through the Reference Manager. - {StrBegin="MSB3781: "} - - - MSB3782: The "{0}" SDK does not support targeting a neutral architecture with "Prefer 32-Bit" enabled for the project. Please go to the project properties (Build tab for C# and Compile tab for VB) and disable the "Prefer 32-bit" option, or change your project to target a non-neutral architecture. - MSB3782: The "{0}" SDK does not support targeting a neutral architecture with "Prefer 32-Bit" enabled for the project. Please go to the project properties (Build tab for C# and Compile tab for VB) and disable the "Prefer 32-bit" option, or change your project to target a non-neutral architecture. - {StrBegin="MSB3782: "} Also, please localize "Prefer 32-Bit" in the same way that it is localized in wizard\vbdesigner\designer\proppages\buildproppage.resx - - - MSB3783: Project "{0}" depends upon SDK "{1} v{2}" which was released originally for apps targeting "{3} {4}". To verify whether "{1} v{2}" is compatible with "{5} {6}", contact the SDK author or see http://go.microsoft.com/fwlink/?LinkID=309181. - MSB3783: Project "{0}" depends upon SDK "{1} v{2}" which was released originally for apps targeting "{3} {4}". To verify whether "{1} v{2}" is compatible with "{5} {6}", contact the SDK author or see http://go.microsoft.com/fwlink/?LinkID=309181. - {StrBegin="MSB3783: "} - - - MSB3841: The SDK "{0}" depends on the SDK "{1}", which is not compatible with "{2} {3}". Please reference a version of SDK "{0}" which supports "{2} {3}". - MSB3841: The SDK "{0}" depends on the SDK "{1}", which is not compatible with "{2} {3}". Please reference a version of SDK "{0}" which supports "{2} {3}". - {StrBegin="MSB3841: "} - - - MSB3842: Project "{0}" depends upon SDK "{1} v{2}" which supports apps targeting "{3} {4}". To verify whether "{1} v{2}" is compatible with "{5} {6}", contact the SDK author or see http://go.microsoft.com/fwlink/?LinkID=309181. - MSB3842: Project "{0}" depends upon SDK "{1} v{2}" which supports apps targeting "{3} {4}". To verify whether "{1} v{2}" is compatible with "{5} {6}", contact the SDK author or see http://go.microsoft.com/fwlink/?LinkID=309181. - {StrBegin="MSB3842: "} - - - MSB3843: Project "{0}" targets platform "{3}", but references SDK "{1} v{2}" which targets platform "{4}". - MSB3843: Project "{0}" targets platform "{3}", but references SDK "{1} v{2}" which targets platform "{4}". - {StrBegin="MSB3843: "} - - - MSB3844: Project "{0}" targets platform version "{3}", but references SDK "{1} v{2}" which requires platform version "{4}" or higher. - MSB3844: Project "{0}" targets platform version "{3}", but references SDK "{1} v{2}" which requires platform version "{4}" or higher. - {StrBegin="MSB3844: "} - - - Installed SDKs: - Installed SDKs: - - - - SDK "{0}" is installed at "{1}" - SDK "{0}" is installed at "{1}" - - - - Found "{0}" SDKs. - Found "{0}" SDKs. - - - - Searching for SDKs targeting "{0}, {1}". - Searching for SDKs targeting "{0}, {1}". - {0} will be the platform identifier, "Windows" and {1} will be a version number - - - MSB3784: "TargetPlatformVersion" and "TargetPlatformIdentifier" cannot be empty. - MSB3784: "TargetPlatformVersion" and "TargetPlatformIdentifier" cannot be empty. - {StrBegin="MSB3784: "} TargetPlatformVersion and TargetPlatformIdentifier root are property names and should not be localized - - - MSB3785: No SDKs were found for TargetPlatform = {0} v{1}. SDKReference items will not be resolved. If your application requires these references there may be compilation errors. - MSB3785: No SDKs were found for TargetPlatform = {0} v{1}. SDKReference items will not be resolved. If your application requires these references there may be compilation errors. - {StrBegin="MSB3785: "} "SDKReference" refers to SDKReference items in the project file and should not be localized. - - - MSB3786: There was a problem retrieving the installed SDKs on the machine. {0} - MSB3786: There was a problem retrieving the installed SDKs on the machine. {0} - {StrBegin="MSB3786: "} - - - Enumerating SDK Reference "{0}" from "{1}". - Enumerating SDK Reference "{0}" from "{1}". - - - - Looking for references under "{0}". - Looking for references under "{0}". - - - - Looking for redist files under "{0}". - Looking for redist files under "{0}". - - - - Not enumerating SDK Reference "{0}" because the "ExpandReferences" metadata is not true on the reference. - Not enumerating SDK Reference "{0}" because the "ExpandReferences" metadata is not true on the reference. - - - - Adding reference "{0}". - Adding reference "{0}". - - - - Adding file "{0}" from redist folder with target path "{1}". - Adding file "{0}" from redist folder with target path "{1}". - - - - There was a conflict between two redist files going to the same target path "{0}" within the "{1}" SDK. Choosing "{2}" over "{3}" because it was resolved first. - There was a conflict between two redist files going to the same target path "{0}" within the "{1}" SDK. Choosing "{2}" over "{3}" because it was resolved first. - - - - There was a conflict between two files from the redist folder files going to the same target path "{0}" between the "{1}" and "{2}" SDKs. Choosing "{3}" over "{4}" because it was resolved first. - There was a conflict between two files from the redist folder files going to the same target path "{0}" between the "{1}" and "{2}" SDKs. Choosing "{3}" over "{4}" because it was resolved first. - - - - There was a conflict between two references with the same file name resolved within the "{0}" SDK. Choosing "{1}" over "{2}" because it was resolved first. - There was a conflict between two references with the same file name resolved within the "{0}" SDK. Choosing "{1}" over "{2}" because it was resolved first. - - - - There was a conflict between two references with the same file name between the "{0}" and "{1}" SDKs. Choosing "{2}" over "{3}" because it was resolved first. - There was a conflict between two references with the same file name between the "{0}" and "{1}" SDKs. Choosing "{2}" over "{3}" because it was resolved first. - - - - There was a problem reading the cache file "{0}". "{1}" - There was a problem reading the cache file "{0}". "{1}" - - - - There was a problem deleting the cache file "{0}". "{1}" - There was a problem deleting the cache file "{0}". "{1}" - - - - There was a problem getting the time stamp of the current assembly "{0}". "{1}" - There was a problem getting the time stamp of the current assembly "{0}". "{1}" - - - - There was a problem getting the assembly metadata for "{0}". "{1}" - There was a problem getting the assembly metadata for "{0}". "{1}" - - - - There was a problem writing the cache file "{0}". "{1}" - There was a problem writing the cache file "{0}". "{1}" - - - - The "OriginalItemSpec" metadata for the resolved SDK with path "{0}" was empty. The "OriginalItemSpec" metadata must be set." - The "OriginalItemSpec" metadata for the resolved SDK with path "{0}" was empty. The "OriginalItemSpec" metadata must be set." - - - - MSB3795: There was a problem in the GetSDKReferenceFiles task. {0} - MSB3795: There was a problem in the GetSDKReferenceFiles task. {0} - {StrBegin="MSB3795: "} - - - MSB3796: There was a conflict between two files. {0} - MSB3796: There was a conflict between two files. {0} - {StrBegin="MSB3796: "} - - - MSB3797: The targeted configuration for the resolved sdk reference "{0}" was empty. Cannot find reference or redist files without a targeted configuration. - MSB3797: The targeted configuration for the resolved sdk reference "{0}" was empty. Cannot find reference or redist files without a targeted configuration. - {StrBegin="MSB3797: "} - - - MSB3798: The targeted architecture for the resolved sdk reference "{0}" was empty. Cannot find reference or redist files without a targeted architecture. - MSB3798: The targeted architecture for the resolved sdk reference "{0}" was empty. Cannot find reference or redist files without a targeted architecture. - {StrBegin="MSB3798: "} - - - MSB3851: This project targets "{0}, Version={1}", but it is attempting to reference "{2}" targeting "{3}", which is invalid. - MSB3851: This project targets "{0}, Version={1}", but it is attempting to reference "{2}" targeting "{3}", which is invalid. - {StrBegin="MSB3851: "} - - - MSB3861: Failed to log an error using resource string "{0}". {1} - MSB3861: Failed to log an error using resource string "{0}". {1} - {StrBegin="MSB3861: "} - - - MSB3871: Shared projects cannot be built on their own. Please either build a project that references this project, or build the entire solution. - MSB3871: Shared projects cannot be built on their own. Please either build a project that references this project, or build the entire solution. - {StrBegin="MSB3871: "} - - - MSB3891: Both "{0}" and "{1}" were specified in the project file. Please choose one or the other. - MSB3891: Both "{0}" and "{1}" were specified in the project file. Please choose one or the other. - - - - The property "{0}" in the telemetry event data property list "{1}" is malformed. Please only pass in a semicolon-delimited list of constant string values separated by "=", e.g., "Property1=Value1;Property2=Value2". - The property "{0}" in the telemetry event data property list "{1}" is malformed. Please only pass in a semicolon-delimited list of constant string values separated by "=", e.g., "Property1=Value1;Property2=Value2". - - - - (No message specified) - (No message specified) - - - - MSB4801: The task factory "{0}" is not supported on the .NET Core version of MSBuild. - MSB4801: The task factory "{0}" is not supported on the .NET Core version of MSBuild. - {StrBegin="MSB4801: "} - - - Zipping directory "{0}" to "{1}". - Zipping directory "{0}" to "{1}". - - - - MSB3941: Failed to zip directory "{0}" because it does not exist or is inaccessible. - MSB3941: Failed to zip directory "{0}" because it does not exist or is inaccessible. - {StrBegin="MSB3941: "} - - - MSB3943: Failed to zip directory "{0}" to file "{1}". {2} - MSB3943: Failed to zip directory "{0}" to file "{1}". {2} - {StrBegin="MSB3943: "} - - - MSB3942: Failed to create zip file "{0}" because it already exists. Please delete or rename the file and try again. - MSB3942: Failed to create zip file "{0}" because it already exists. Please delete or rename the file and try again. - {StrBegin="MSB3942: "} - - - - \ No newline at end of file diff --git a/src/Utilities/Resources/xlf/Strings.en.xlf b/src/Utilities/Resources/xlf/Strings.en.xlf deleted file mode 100644 index c5ca7ab2572..00000000000 --- a/src/Utilities/Resources/xlf/Strings.en.xlf +++ /dev/null @@ -1,282 +0,0 @@ - - - - - - MSB6001: Invalid command line switch for "{0}". {1} - MSB6001: Invalid command line switch for "{0}". {1} - {StrBegin="MSB6001: "}UE: This message is shown when a tool-based task (i.e. the task is a wrapper for an .exe) is given a parameter value that converts into an invalid command line switch for the tool. "{0}" is the name of the tool e.g. "csc.exe", and "{1}" is a message explaining the problem. LOCALIZATION: "{1}" is a localized message. - - - Illegal quote passed to the command line switch named "{0}". The value was [{1}]. - Illegal quote passed to the command line switch named "{0}". The value was [{1}]. - - - - Illegal quote in the command line value [{0}]. - Illegal quote in the command line value [{0}]. - - - - The command exited with code {0}. - The command exited with code {0}. - - - - MSB6005: Task attempted to log before it was initialized. Message was: {0} - MSB6005: Task attempted to log before it was initialized. Message was: {0} - {StrBegin="MSB6005: "}UE: This occurs if the task attempts to log something in its own constructor. - - - MSB6010: Could not find platform manifest file at "{0}". - MSB6010: Could not find platform manifest file at "{0}". - {StrBegin="MSB6010: "} - - - .NET Framework version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. - .NET Framework version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion. - - - - .NET Framework version "{0}" is not supported when explicitly targeting the Windows SDK, which is only supported on .NET 4.5 and later. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion that is Version45 or above. - .NET Framework version "{0}" is not supported when explicitly targeting the Windows SDK, which is only supported on .NET 4.5 and later. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion that is Version45 or above. - - - - Visual Studio version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.VisualStudioVersion. - Visual Studio version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.VisualStudioVersion. - - - - MSB6002: The command-line for the "{0}" task is too long. Command-lines longer than 32000 characters are likely to fail. Try reducing the length of the command-line by breaking down the call to "{0}" into multiple calls with fewer parameters per call. - MSB6002: The command-line for the "{0}" task is too long. Command-lines longer than 32000 characters are likely to fail. Try reducing the length of the command-line by breaking down the call to "{0}" into multiple calls with fewer parameters per call. - {StrBegin="MSB6002: "} - - - MSB6003: The specified task executable "{0}" could not be run. {1} - MSB6003: The specified task executable "{0}" could not be run. {1} - {StrBegin="MSB6003: "} - - - MSB6006: "{0}" exited with code {1}. - MSB6006: "{0}" exited with code {1}. - {StrBegin="MSB6006: "} - - - MSB6004: The specified task executable location "{0}" is invalid. - MSB6004: The specified task executable location "{0}" is invalid. - {StrBegin="MSB6004: "} - - - MSB6011: Invalid parameters passed to the {0} task. - MSB6011: Invalid parameters passed to the {0} task. - {StrBegin="MSB6011: "} - - - There was an error reading the redist list file "{0}". {1} - There was an error reading the redist list file "{0}". {1} - No Error code because this resource will be used in an exception. The error code is discarded if it is included - - - The Framework at path "{0}" tried to include the framework at path "{1}" as part of its reference assembly paths but there was an error. {2} - The Framework at path "{0}" tried to include the framework at path "{1}" as part of its reference assembly paths but there was an error. {2} - No Error code because this resource will be used in an exception. The error code is discarded if it is included - - - When attempting to generate a reference assembly path from the path "{0}" and the framework moniker "{1}" there was an error. {2} - When attempting to generate a reference assembly path from the path "{0}" and the framework moniker "{1}" there was an error. {2} - No Error code because this resource will be used in an exception. The error code is discarded if it is included - - - MSB6007: The "{0}" value passed to the Environment property is not in the format "name=value", where the value part may be empty. - MSB6007: The "{0}" value passed to the Environment property is not in the format "name=value", where the value part may be empty. - {StrBegin="MSB6007: "} - - - Environment Variables passed to tool: - Environment Variables passed to tool: - - - - Tracking logs are not available, minimal rebuild will be disabled. - Tracking logs are not available, minimal rebuild will be disabled. - - - - Missing input files detected, minimal rebuild will be disabled. - Missing input files detected, minimal rebuild will be disabled. - - - - Missing output files detected, minimal rebuild will be disabled. - Missing output files detected, minimal rebuild will be disabled. - - - - Skipping task because it is up-to-date. - Skipping task because it is up-to-date. - - - - Write Tracking log not available, minimal rebuild will be disabled. - Write Tracking log not available, minimal rebuild will be disabled. - - - - Write Tracking Logs: - Write Tracking Logs: - - - - Using cached output dependency table built from: - Using cached output dependency table built from: - - - - Tracking Logs: - Tracking Logs: - - - - Using cached dependency table built from: - Using cached dependency table built from: - - - - Outputs for {0}: - Outputs for {0}: - - - - Inputs for {0}: - Inputs for {0}: - - - - Output details ({0} of them) were not logged for performance reasons. - Output details ({0} of them) were not logged for performance reasons. - - - - Input details ({0} of them) were not logged for performance reasons. - Input details ({0} of them) were not logged for performance reasons. - - - - Tracking log {0} is not available. - Tracking log {0} is not available. - - - - {0} will be compiled because the tracking log is not available. - {0} will be compiled because the tracking log is not available. - - - - {0} will be compiled because it was not found in the tracking log. - {0} will be compiled because it was not found in the tracking log. - - - - {0} will be compiled because not all outputs are available. - {0} will be compiled because not all outputs are available. - - - - {0} will be compiled because dependency {1} was missing. - {0} will be compiled because dependency {1} was missing. - - - - {0} will be compiled because {1} was modified at {2}. - {0} will be compiled because {1} was modified at {2}. - - - - {0} will be compiled. - {0} will be compiled. - - - - All outputs are up-to-date. - All outputs are up-to-date. - - - - File {0} was modified at {1} which is newer than {2} modified at {3}. - File {0} was modified at {1} which is newer than {2} modified at {3}. - - - - {0} does not exist; source compilation required. - {0} does not exist; source compilation required. - - - - {0} will be compiled because output {1} does not exist. - {0} will be compiled because output {1} does not exist. - - - - Read Tracking Logs: - Read Tracking Logs: - - - - Using cached input dependency table built from: - Using cached input dependency table built from: - - - - No output for {0} was found in the tracking log; source compilation required. - No output for {0} was found in the tracking log; source compilation required. - - - - No dependencies for output {0} were found in the tracking log; source compilation required. - No dependencies for output {0} were found in the tracking log; source compilation required. - - - - Could not find {0} in the write tracking log. - Could not find {0} in the write tracking log. - - - - Could not find {0} in the read tracking log. - Could not find {0} in the read tracking log. - - - - The number of source files and corresponding outputs must match. - The number of source files and corresponding outputs must match. - - - - Source compilation required: input {0} is newer than output {1}. - Source compilation required: input {0} is newer than output {1}. - - - - MSB6008: Forcing a rebuild of all sources due to an error with the tracking logs. {0} - MSB6008: Forcing a rebuild of all sources due to an error with the tracking logs. {0} - {StrBegin="MSB6008: "} - - - MSB6009: Forcing a rebuild of all source files due to the contents of "{0}" being invalid. - MSB6009: Forcing a rebuild of all source files due to the contents of "{0}" being invalid. - {StrBegin="MSB6009: "} - - - Build FAILED. - Build FAILED. - - - - Build succeeded. - Build succeeded. - - - - - \ No newline at end of file