PowerBuild.xml
|
<?xml version="1.0"?>
<doc> <assembly> <name>PowerBuild</name> </assembly> <members> <member name="T:Microsoft.Build.CommandLine.InitializationException"> <summary> This exception is used to flag failures in application initialization, either due to invalid parameters on the command line, or because the application was invoked in an invalid context. </summary> <remarks> Unlike the CommandLineSwitchException, this exception is NOT thrown for syntax errors in switches. </remarks> </member> <member name="M:Microsoft.Build.CommandLine.InitializationException.#ctor"> <summary> Private default constructor prevents parameterless instantiation. </summary> </member> <member name="M:Microsoft.Build.CommandLine.InitializationException.#ctor(System.String)"> <summary> This constructor initializes the exception message. </summary> <param name="message"></param> </member> <member name="M:Microsoft.Build.CommandLine.InitializationException.#ctor(System.String,System.String)"> <summary> This constructor initializes the exception message and saves the switch that caused the initialization failure. </summary> <param name="message"></param> <param name="invalidSwitch">Can be null.</param> </member> <member name="P:Microsoft.Build.CommandLine.InitializationException.Message"> <summary> Gets the error message and the invalid switch, or only the error message if no invalid switch is set. </summary> </member> <member name="M:Microsoft.Build.CommandLine.InitializationException.VerifyThrow(System.Boolean,System.String)"> <summary> Throws the exception if the specified condition is not met. </summary> <param name="condition"></param> <param name="messageResourceName"></param> </member> <member name="M:Microsoft.Build.CommandLine.InitializationException.VerifyThrow(System.Boolean,System.String,System.String)"> <summary> Throws the exception if the specified condition is not met. </summary> <param name="condition"></param> <param name="messageResourceName"></param> <param name="invalidSwitch"></param> </member> <member name="M:Microsoft.Build.CommandLine.InitializationException.Throw(System.String,System.String,System.Exception,System.Boolean)"> <summary> Throws the exception using the given exception context. </summary> <param name="messageResourceName"></param> <param name="invalidSwitch"></param> <param name="e"></param> <param name="showStackTrace"></param> </member> <member name="M:Microsoft.Build.CommandLine.InitializationException.VerifyThrow(System.Boolean,System.String,System.String,System.Object[])"> <summary> Throws the exception if the specified condition is not met. </summary> </member> <member name="M:Microsoft.Build.CommandLine.InitializationException.Throw(System.String,System.String)"> <summary> Throws the exception using the given exception context. </summary> <param name="message"></param> <param name="invalidSwitch"></param> </member> <member name="T:Microsoft.Build.CommandLine.MSBuildApp"> <summary> This class implements the MSBuild.exe command-line application. It processes command-line arguments and invokes the build engine. </summary> </member> <member name="M:Microsoft.Build.CommandLine.MSBuildApp.ValidateExtensions(System.String[])"> <summary> This method takes in a list of file name extensions to ignore. It will then validate the extensions to make sure they start with a period, have atleast one character after the period and do not contain any invalid path chars or wild cards </summary> <param name="projectsExtensionsToIgnore"></param> <returns></returns> </member> <member name="M:Microsoft.Build.CommandLine.MSBuildApp.RemoveFilesWithExtensionsToIgnore(System.String[],System.Collections.Generic.Dictionary{System.String,System.Object})"> <summary> Removes filenames from the given list whose extensions are on the list of extensions to ignore </summary> <param name="potentialProjectOrSolutionFiles">A list of project or solution file names</param> <param name="extensionsToIgnoreDictionary">A list of extensions to ignore</param> <returns>Array of project or solution files names which do not have an extension to be ignored </returns> </member> <member name="F:Microsoft.Build.CommandLine.MSBuildApp.s_wildcards"> <summary> This is a set of wildcard chars which can cause a file extension to be invalid </summary> </member> <member name="T:Microsoft.Build.Shared.ErrorUtilities"> <summary> This class contains methods that are useful for error checking and validation. </summary> </member> <member name="F:Microsoft.Build.Shared.ErrorUtilities.s_throwExceptions"> <summary> Emergency escape hatch. If a customer hits a bug in the shipped product causing an internal exception, and fortuitously it happens that ignoring the VerifyThrow allows execution to continue in a reasonable way, then we can give them this undocumented environment variable as an immediate workaround. </summary> </member> <member name="M:Microsoft.Build.Shared.ErrorUtilities.ThrowInternalError(System.String,System.Object[])"> <summary> Throws InternalErrorException. This is only for situations that would mean that there is a bug in MSBuild itself. </summary> </member> <member name="M:Microsoft.Build.Shared.ErrorUtilities.ThrowInternalError(System.String,System.Exception,System.Object[])"> <summary> Throws InternalErrorException. This is only for situations that would mean that there is a bug in MSBuild itself. </summary> </member> <member name="M:Microsoft.Build.Shared.ErrorUtilities.ThrowInternalErrorUnreachable"> <summary> Throws InternalErrorException. Indicates the code path followed should not have been possible. This is only for situations that would mean that there is a bug in MSBuild itself. </summary> </member> <member name="M:Microsoft.Build.Shared.ErrorUtilities.ThrowIfTypeDoesNotImplementToString(System.Object)"> <summary> Throws InternalErrorException. Indicates the code path followed should not have been possible. This is only for situations that would mean that there is a bug in MSBuild itself. </summary> </member> <member name="M:Microsoft.Build.Shared.ErrorUtilities.VerifyThrowInternalNull(System.Object,System.String)"> <summary> Helper to throw an InternalErrorException when the specified parameter is null. This should be used ONLY if this would indicate a bug in MSBuild rather than anything caused by user action. </summary> <param name="parameter">The value of the argument.</param> <param name="parameterName">Parameter that should not be null</param> </member> <member name="M:Microsoft.Build.Shared.ErrorUtilities.VerifyThrowInternalLockHeld(System.Object)"> <summary> Helper to throw an InternalErrorException when a lock on the specified object is not already held. This should be used ONLY if this would indicate a bug in MSBuild rather than anything caused by user action. </summary> <param name="locker">The object that should already have been used as a lock.</param> </member> <member name="M:Microsoft.Build.Shared.ErrorUtilities.VerifyThrowInternalLength(System.String,System.String)"> <summary> Helper to throw an InternalErrorException when the specified parameter is null or zero length. This should be used ONLY if this would indicate a bug in MSBuild rather than anything caused by user action. </summary> <param name="parameterValue">The value of the argument.</param> <param name="parameterName">Parameter that should not be null or zero length</param> </member> <member name="M:Microsoft.Build.Shared.ErrorUtilities.VerifyThrowInternalRooted(System.String)"> <summary> Helper to throw an InternalErrorException when the specified parameter is not a rooted path. This should be used ONLY if this would indicate a bug in MSBuild rather than anything caused by user action. </summary> <param name="value">Parameter that should be a rooted path</param> </member> <member name="M:Microsoft.Build.Shared.ErrorUtilities.VerifyThrow(System.Boolean,System.String)"> <summary> This method should be used in places where one would normally put an "assert". It should be used to validate that our assumptions are true, where false would indicate that there must be a bug in our code somewhere. This should not be used to throw errors based on bad user input or anything that the user did wrong. </summary> <param name="condition"></param> <param name="unformattedMessage"></param> </member> <member name="M:Microsoft.Build.Shared.ErrorUtilities.VerifyThrow(System.Boolean,System.String,System.Object)"> <summary> Overload for one string format argument. </summary> <param name="condition"></param> <param name="unformattedMessage"></param> <param name="arg0"></param> </member> <member name="M:Microsoft.Build.Shared.ErrorUtilities.VerifyThrow(System.Boolean,System.String,System.Object,System.Object)"> <summary> Overload for two string format arguments. </summary> <param name="condition"></param> <param name="unformattedMessage"></param> <param name="arg0"></param> <param name="arg1"></param> </member> <member name="M:Microsoft.Build.Shared.ErrorUtilities.VerifyThrow(System.Boolean,System.String,System.Object,System.Object,System.Object)"> <summary> Overload for three string format arguments. </summary> <param name="condition"></param> <param name="unformattedMessage"></param> <param name="arg0"></param> <param name="arg1"></param> <param name="arg2"></param> </member> <member name="M:Microsoft.Build.Shared.ErrorUtilities.VerifyThrow(System.Boolean,System.String,System.Object,System.Object,System.Object,System.Object)"> <summary> Overload for four string format arguments. </summary> <param name="condition"></param> <param name="unformattedMessage"></param> <param name="arg0"></param> <param name="arg1"></param> <param name="arg2"></param> <param name="arg3"></param> </member> <member name="M:Microsoft.Build.Shared.ErrorUtilities.ThrowInvalidOperation(System.String,System.Object[])"> <summary> Throws an InvalidOperationException with the specified resource string </summary> <param name="resourceName">Resource to use in the exception</param> <param name="args">Formatting args.</param> </member> <member name="M:Microsoft.Build.Shared.ErrorUtilities.VerifyThrowInvalidOperation(System.Boolean,System.String)"> <summary> Throws an InvalidOperationException if the given condition is false. </summary> <param name="condition"></param> <param name="resourceName"></param> </member> <member name="M:Microsoft.Build.Shared.ErrorUtilities.VerifyThrowInvalidOperation(System.Boolean,System.String,System.Object)"> <summary> Overload for one string format argument. </summary> <param name="condition"></param> <param name="resourceName"></param> <param name="arg0"></param> </member> <member name="M:Microsoft.Build.Shared.ErrorUtilities.VerifyThrowInvalidOperation(System.Boolean,System.String,System.Object,System.Object)"> <summary> Overload for two string format arguments. </summary> <param name="condition"></param> <param name="resourceName"></param> <param name="arg0"></param> <param name="arg1"></param> </member> <member name="M:Microsoft.Build.Shared.ErrorUtilities.VerifyThrowInvalidOperation(System.Boolean,System.String,System.Object,System.Object,System.Object)"> <summary> Overload for three string format arguments. </summary> <param name="condition"></param> <param name="resourceName"></param> <param name="arg0"></param> <param name="arg1"></param> <param name="arg2"></param> </member> <member name="M:Microsoft.Build.Shared.ErrorUtilities.VerifyThrowInvalidOperation(System.Boolean,System.String,System.Object,System.Object,System.Object,System.Object)"> <summary> Overload for four string format arguments. </summary> <param name="condition"></param> <param name="resourceName"></param> <param name="arg0"></param> <param name="arg1"></param> <param name="arg2"></param> <param name="arg3"></param> </member> <member name="M:Microsoft.Build.Shared.ErrorUtilities.ThrowArgument(System.String,System.Object[])"> <summary> Throws an ArgumentException that can include an inner exception. PERF WARNING: calling a method that takes a variable number of arguments is expensive, because memory is allocated for the array of arguments -- do not call this method repeatedly in performance-critical scenarios </summary> </member> <member name="M:Microsoft.Build.Shared.ErrorUtilities.ThrowArgument(System.Exception,System.String,System.Object[])"> <summary> Throws an ArgumentException that can include an inner exception. PERF WARNING: calling a method that takes a variable number of arguments is expensive, because memory is allocated for the array of arguments -- do not call this method repeatedly in performance-critical scenarios </summary> <remarks> This method is thread-safe. </remarks> <param name="innerException">Can be null.</param> <param name="resourceName"></param> <param name="args"></param> </member> <member name="M:Microsoft.Build.Shared.ErrorUtilities.VerifyThrowArgument(System.Boolean,System.String)"> <summary> Throws an ArgumentException if the given condition is false. </summary> <remarks>This method is thread-safe.</remarks> <param name="condition"></param> <param name="resourceName"></param> </member> <member name="M:Microsoft.Build.Shared.ErrorUtilities.VerifyThrowArgument(System.Boolean,System.String,System.Object)"> <summary> Overload for one string format argument. </summary> <remarks>This method is thread-safe.</remarks> <param name="condition"></param> <param name="resourceName"></param> <param name="arg0"></param> </member> <member name="M:Microsoft.Build.Shared.ErrorUtilities.VerifyThrowArgument(System.Boolean,System.String,System.Object,System.Object)"> <summary> Overload for two string format arguments. </summary> <remarks>This method is thread-safe.</remarks> <param name="condition"></param> <param name="resourceName"></param> <param name="arg0"></param> <param name="arg1"></param> </member> <member name="M:Microsoft.Build.Shared.ErrorUtilities.VerifyThrowArgument(System.Boolean,System.String,System.Object,System.Object,System.Object)"> <summary> Overload for three string format arguments. </summary> <remarks>This method is thread-safe.</remarks> </member> <member name="M:Microsoft.Build.Shared.ErrorUtilities.VerifyThrowArgument(System.Boolean,System.String,System.Object,System.Object,System.Object,System.Object)"> <summary> Overload for four string format arguments. </summary> <remarks>This method is thread-safe.</remarks> </member> <member name="M:Microsoft.Build.Shared.ErrorUtilities.VerifyThrowArgument(System.Boolean,System.Exception,System.String)"> <summary> Throws an ArgumentException that includes an inner exception, if the given condition is false. </summary> <remarks>This method is thread-safe.</remarks> <param name="condition"></param> <param name="innerException">Can be null.</param> <param name="resourceName"></param> </member> <member name="M:Microsoft.Build.Shared.ErrorUtilities.VerifyThrowArgument(System.Boolean,System.Exception,System.String,System.Object)"> <summary> Overload for one string format argument. </summary> <remarks>This method is thread-safe.</remarks> <param name="condition"></param> <param name="innerException"></param> <param name="resourceName"></param> <param name="arg0"></param> </member> <member name="M:Microsoft.Build.Shared.ErrorUtilities.VerifyThrowArgument(System.Boolean,System.Exception,System.String,System.Object,System.Object)"> <summary> Overload for two string format arguments. </summary> <remarks>This method is thread-safe.</remarks> <param name="condition"></param> <param name="innerException"></param> <param name="resourceName"></param> <param name="arg0"></param> <param name="arg1"></param> </member> <member name="M:Microsoft.Build.Shared.ErrorUtilities.VerifyThrowArgument(System.Boolean,System.Exception,System.String,System.Object,System.Object,System.Object)"> <summary> Overload for three string format arguments. </summary> <remarks>This method is thread-safe.</remarks> </member> <member name="M:Microsoft.Build.Shared.ErrorUtilities.VerifyThrowArgument(System.Boolean,System.Exception,System.String,System.Object,System.Object,System.Object,System.Object)"> <summary> Overload for four string format arguments. </summary> <remarks>This method is thread-safe.</remarks> </member> <member name="M:Microsoft.Build.Shared.ErrorUtilities.ThrowArgumentOutOfRange(System.String)"> <summary> Throws an argument out of range exception. </summary> </member> <member name="M:Microsoft.Build.Shared.ErrorUtilities.VerifyThrowArgumentOutOfRange(System.Boolean,System.String)"> <summary> Throws an ArgumentOutOfRangeException using the given parameter name if the condition is false. </summary> </member> <member name="M:Microsoft.Build.Shared.ErrorUtilities.VerifyThrowArgumentLength(System.String,System.String)"> <summary> Throws an ArgumentNullException if the given string parameter is null and ArgumentException if it has zero length. </summary> <param name="parameter"></param> <param name="parameterName"></param> </member> <member name="M:Microsoft.Build.Shared.ErrorUtilities.VerifyThrowArgumentLengthIfNotNull(System.String,System.String)"> <summary> Throws an ArgumentException if the string has zero length, unless it is null, in which case no exception is thrown. </summary> </member> <member name="M:Microsoft.Build.Shared.ErrorUtilities.VerifyThrowArgumentNull(System.Object,System.String)"> <summary> Throws an ArgumentNullException if the given parameter is null. </summary> <remarks>This method is thread-safe.</remarks> <param name="parameter"></param> <param name="parameterName"></param> </member> <member name="M:Microsoft.Build.Shared.ErrorUtilities.VerifyThrowArgumentNull(System.Object,System.String,System.String)"> <summary> Throws an ArgumentNullException if the given parameter is null. </summary> <remarks>This method is thread-safe.</remarks> </member> <member name="M:Microsoft.Build.Shared.ErrorUtilities.VerifyThrowArgumentArraysSameLength(System.Array,System.Array,System.String,System.String)"> <summary> Verifies the given arrays are not null and have the same length </summary> <param name="parameter1"></param> <param name="parameter2"></param> <param name="parameter1Name"></param> <param name="parameter2Name"></param> </member> <member name="T:Microsoft.Build.Shared.DirectoryGetFiles"> <summary> delegate for System.IO.Directory.GetFiles, used for testing </summary> <param name="path">Directory path to start search for files in</param> <param name="searchPattern">pattern of files to match</param> <returns>string array of files which match search pattern</returns> </member> <member name="T:Microsoft.Build.Shared.GetDirectories"> <summary> delegate for Directory.GetDirectories. </summary> <param name="path">The path to get directories for.</param> <param name="pattern">The pattern to search for.</param> <returns>An array of directories.</returns> </member> <member name="T:Microsoft.Build.Shared.DirectoryExists"> <summary> Delegate for System.IO.Directory.Exists </summary> <param name="path">Directory path to check if it exists</param> <returns>true if directory exists</returns> </member> <member name="T:Microsoft.Build.Shared.FileExists"> <summary> File exists delegate </summary> <param name="path">The path to check for existence.</param> <returns>'true' if the file exists.</returns> </member> <member name="T:Microsoft.Build.Shared.FileCopy"> <summary> File.Copy delegate </summary> <param name="source"></param> <param name="destination"></param> </member> <member name="T:Microsoft.Build.Shared.FileDelete"> <summary> File.Delete delegate </summary> <param name="path"></param> </member> <member name="T:Microsoft.Build.Shared.FileCreate"> <summary> File create delegate </summary> <param name="path">The path to create.</param> </member> <member name="T:Microsoft.Build.Shared.InternalErrorException"> <summary> This exception is to be thrown whenever an assumption we have made in the code turns out to be false. Thus, if this exception ever gets thrown, it is because of a bug in our own code, not because of something the user or project author did wrong. !~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~ WARNING: When this file is shared into multiple assemblies each assembly will view this as a different type. Don't throw this exception from one assembly and catch it in another. !~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~ </summary> </member> <member name="M:Microsoft.Build.Shared.InternalErrorException.#ctor"> <summary> Default constructor. SHOULD ONLY BE CALLED BY DESERIALIZER. SUPPLY A MESSAGE INSTEAD. </summary> </member> <member name="M:Microsoft.Build.Shared.InternalErrorException.#ctor(System.String)"> <summary> Creates an instance of this exception using the given message. </summary> </member> <member name="M:Microsoft.Build.Shared.InternalErrorException.#ctor(System.String,System.Exception)"> <summary> Creates an instance of this exception using the given message and inner exception. Adds the inner exception's details to the exception message because most bug reporters don't bother to provide the inner exception details which is typically what we care about. </summary> </member> <member name="M:Microsoft.Build.Shared.InternalErrorException.ConsiderDebuggerLaunch(System.String,System.Exception)"> <summary> A fatal internal error due to a bug has occurred. Give the dev a chance to debug it, if possible. Will in all cases launch the debugger, if the environment variable "MSBUILDLAUNCHDEBUGGER" is set. In DEBUG build, will always launch the debugger, unless we are in razzle (_NTROOT is set) or in NUnit, or MSBUILDDONOTLAUNCHDEBUGGER is set (that could be useful in suite runs). We don't launch in retail or LKG so builds don't jam; they get a callstack, and continue or send a mail, etc. We don't launch in NUnit as tests often intentionally cause InternalErrorExceptions. Because we only call this method from this class, just before throwing an InternalErrorException, there is no danger that this suppression will cause a bug to only manifest itself outside NUnit (which would be most unfortunate!). Do not make this non-private. Unfortunately NUnit can't handle unhandled exceptions like InternalErrorException on anything other than the main test thread. However, there's still a callstack displayed before it quits. If it is going to launch the debugger, it first does a Debug.Fail to give information about what needs to be debugged -- the exception hasn't been thrown yet. This automatically displays the current callstack. </summary> </member> <member name="T:Microsoft.Build.Shared.ResourceUtilities"> <summary> This class contains utility methods for dealing with resources. </summary> </member> <member name="M:Microsoft.Build.Shared.ResourceUtilities.ExtractMessageCode(System.Boolean,System.String,System.String@)"> <summary> Extracts the message code (if any) prefixed to the given string. <![CDATA[ MSBuild codes match "^\s*(?<CODE>MSB\d\d\d\d):\s*(?<MESSAGE>.*)$" Arbitrary codes match "^\s*(?<CODE>[A-Za-z]+\d+):\s*(?<MESSAGE>.*)$" ]]> Thread safe. </summary> <param name="msbuildCodeOnly">Whether to match only MSBuild error codes, or any error code.</param> <param name="message">The string to parse.</param> <param name="code">[out] The message code, or null if there was no code.</param> <returns>The string without its message code prefix, if any.</returns> </member> <member name="M:Microsoft.Build.Shared.ResourceUtilities.GetHelpKeyword(System.String)"> <summary> Retrieves the MSBuild F1-help keyword for the given resource string. Help keywords are used to index help topics in host IDEs. </summary> <param name="resourceName">Resource string to get the MSBuild F1-keyword for.</param> <returns>The MSBuild F1-help keyword string.</returns> </member> <member name="M:Microsoft.Build.Shared.ResourceUtilities.GetResourceString(System.String)"> <summary> Retrieves the contents of the named resource string. </summary> <param name="resourceName">Resource string name.</param> <returns>Resource string contents.</returns> </member> <member name="M:Microsoft.Build.Shared.ResourceUtilities.FormatResourceString(System.String@,System.String@,System.String,System.Object[])"> <summary> Loads the specified string resource and formats it with the arguments passed in. If the string resource has an MSBuild message code and help keyword associated with it, they too are returned. PERF WARNING: calling a method that takes a variable number of arguments is expensive, because memory is allocated for the array of arguments -- do not call this method repeatedly in performance-critical scenarios </summary> <remarks>This method is thread-safe.</remarks> <param name="code">[out] The MSBuild message code, or null.</param> <param name="helpKeyword">[out] The MSBuild F1-help keyword for the host IDE, or null.</param> <param name="resourceName">Resource string to load.</param> <param name="args">Optional arguments for formatting the resource string.</param> <returns>The formatted resource string.</returns> </member> <member name="M:Microsoft.Build.Shared.ResourceUtilities.FormatResourceString(System.String,System.Object[])"> <summary> Looks up a string in the resources, and formats it with the arguments passed in. If the string resource has an MSBuild message code and help keyword associated with it, they are discarded. PERF WARNING: calling a method that takes a variable number of arguments is expensive, because memory is allocated for the array of arguments -- do not call this method repeatedly in performance-critical scenarios </summary> <remarks>This method is thread-safe.</remarks> <param name="resourceName">Resource string to load.</param> <param name="args">Optional arguments for formatting the resource string.</param> <returns>The formatted resource string.</returns> </member> <member name="M:Microsoft.Build.Shared.ResourceUtilities.FormatString(System.String,System.Object[])"> <summary> Formats the given string using the variable arguments passed in. PERF WARNING: calling a method that takes a variable number of arguments is expensive, because memory is allocated for the array of arguments -- do not call this method repeatedly in performance-critical scenarios Thread safe. </summary> <param name="unformatted">The string to format.</param> <param name="args">Optional arguments for formatting the given string.</param> <returns>The formatted string.</returns> </member> <member name="M:Microsoft.Build.Shared.ResourceUtilities.VerifyResourceStringExists(System.String)"> <summary> Verifies that a particular resource string actually exists in the string table. This will only be called in debug builds. It helps catch situations where a dev calls VerifyThrowXXX with a new resource string, but forgets to add the resource string to the string table, or misspells it! </summary> <remarks>This method is thread-safe.</remarks> <param name="resourceName">Resource string to check.</param> </member> <member name="T:PowerBuild.MSBuild.Strings"> <summary> A strongly-typed resource class, for looking up localized strings, etc. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.ResourceManager"> <summary> Returns the cached ResourceManager instance used by this class. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.Culture"> <summary> Overrides the current thread's CurrentUICulture property for all resource lookups using this strongly typed resource class. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.AbortingBuild"> <summary> Looks up a localized string similar to Attempting to cancel the build.... </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.AmbiguousProjectDirectoryError"> <summary> Looks up a localized string similar to MSBUILD : error MSB1050: Specify which project or solution file to use because the folder "{0}" contains more than one project or solution file.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.AmbiguousProjectError"> <summary> Looks up a localized string similar to MSBUILD : error MSB1011: Specify which project or solution file to use because this folder contains more than one project or solution file.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.BuildStarted"> <summary> Looks up a localized string similar to Build started.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.CannotAutoDisableAutoResponseFile"> <summary> Looks up a localized string similar to MSBUILD : error MSB1027: The /noautoresponse switch cannot be specified in the MSBuild.rsp auto-response file, nor in any response file that is referenced by the auto-response file.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.ConfigurationFailurePrefixNoErrorCode"> <summary> Looks up a localized string similar to MSBUILD : Configuration error {0}: {1}. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.CopyrightMessage"> <summary> Looks up a localized string similar to Microsoft (R) Build Engine version {0} Copyright (C) Microsoft Corporation. All rights reserved. . </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.DebuggingSolutionFiles"> <summary> Looks up a localized string similar to MSBUILD : error MSB1048: Solution files cannot be debugged directly. Run MSBuild first with an environment variable MSBUILDEMITSOLUTION=1 to create a corresponding ".sln.metaproj" file. Then debug that.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.DuplicateProjectSwitchError"> <summary> Looks up a localized string similar to MSBUILD : error MSB1008: Only one project can be specified.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.FatalError"> <summary> Looks up a localized string similar to MSBUILD : error MSB1025: An internal failure occurred while running MSBuild.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.FileLocation"> <summary> Looks up a localized string similar to {0} ({1},{2}). </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.HelpMessage_1_Syntax"> <summary> Looks up a localized string similar to Syntax: MSBuild.exe [options] [project file | directory] . </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.HelpMessage_10_PropertySwitch"> <summary> Looks up a localized string similar to /property:<n>=<v> Set or override these project-level properties. <n> is the property name, and <v> is the property value. Use a semicolon or a comma to separate multiple properties, or specify each property separately. (Short form: /p) Example: /property:WarningLevel=2;OutDir=bin\Debug\ . </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.HelpMessage_11_LoggerSwitch"> <summary> Looks up a localized string similar to /logger:<logger> Use this logger to log events from MSBuild. To specify multiple loggers, specify each logger separately. The <logger> syntax is: [<logger class>,]<logger assembly>[;<logger parameters>] The <logger class> syntax is: [<partial or full namespace>.]<logger class name> The <logger assembly> syntax is: {<assembly name>[,<strong name>] [rest of string was truncated]";. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.HelpMessage_12_VerbositySwitch"> <summary> Looks up a localized string similar to /verbosity:<level> Display this amount of information in the event log. The available verbosity levels are: q[uiet], m[inimal], n[ormal], d[etailed], and diag[nostic]. (Short form: /v) Example: /verbosity:quiet . </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.HelpMessage_13_ConsoleLoggerParametersSwitch"> <summary> Looks up a localized string similar to /consoleloggerparameters:<parameters> Parameters to console logger. (Short form: /clp) The available parameters are: PerformanceSummary--Show time spent in tasks, targets and projects. Summary--Show error and warning summary at the end. NoSummary--Don't show error and warning summary at the end. ErrorsOnly- [rest of string was truncated]";. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.HelpMessage_14_NoConsoleLoggerSwitch"> <summary> Looks up a localized string similar to /noconsolelogger Disable the default console logger and do not log events to the console. (Short form: /noconlog) . </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.HelpMessage_15_ValidateSwitch"> <summary> Looks up a localized string similar to /validate Validate the project against the default schema. (Short form: /val) /validate:<schema> Validate the project against the specified schema. (Short form: /val) Example: /validate:MyExtendedBuildSchema.xsd . </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.HelpMessage_16_Examples"> <summary> Looks up a localized string similar to Examples: MSBuild MyApp.sln /t:Rebuild /p:Configuration=Release MSBuild MyApp.csproj /t:Clean /p:Configuration=Debug;TargetFrameworkVersion=v3.5 . </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.HelpMessage_17_MaximumCPUSwitch"> <summary> Looks up a localized string similar to /maxcpucount[:n] Specifies the maximum number of concurrent processes to build with. If the switch is not used, the default value used is 1. If the switch is used without a value MSBuild will use up to the number of processors on the computer. (Short form: /m[:n]) . </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.HelpMessage_18_DistributedLoggerSwitch"> <summary> Looks up a localized string similar to /distributedlogger:<central logger>*<forwarding logger> Use this logger to log events from MSBuild, attaching a different logger instance to each node. To specify multiple loggers, specify each logger separately. (Short form /dl) The <logger> syntax is: [<logger class>,]<logger assembly>[;<logger parameters>] The <logger class> sy [rest of string was truncated]";. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.HelpMessage_19_IgnoreProjectExtensionsSwitch"> <summary> Looks up a localized string similar to /ignoreprojectextensions:<extensions> List of extensions to ignore when determining which project file to build. Use a semicolon or a comma to separate multiple extensions. (Short form: /ignore) Example: /ignoreprojectextensions:.sln . </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.HelpMessage_2_Description"> <summary> Looks up a localized string similar to Description: Builds the specified targets in the project file. If a project file is not specified, MSBuild searches the current working directory for a file that has a file extension that ends in "proj" and uses that file. If a directory is specified, MSBuild searches that directory for a project file. . </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.HelpMessage_20_FileLoggerSwitch"> <summary> Looks up a localized string similar to /fileLogger[n] Logs the build output to a file. By default the file is in the current directory and named "msbuild[n].log". Events from all nodes are combined into a single log. The location of the file and other parameters for the fileLogger can be specified through the addition of the "/fileLoggerParameters[n]" switch. "n" if present can be a digit from 1-9, allowing [rest of string was truncated]";. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.HelpMessage_21_DistributedFileLoggerSwitch"> <summary> Looks up a localized string similar to /distributedFileLogger Logs the build output to multiple log files, one log file per MSBuild node. The initial location for these files is the current directory. By default the files are called "MSBuild<nodeid>.log". The location of the files and other parameters for the fileLogger can be specified with the addition of [rest of string was truncated]";. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.HelpMessage_22_FileLoggerParametersSwitch"> <summary> Looks up a localized string similar to /fileloggerparameters[n]:<parameters> Provides any extra parameters for file loggers. The presence of this switch implies the corresponding /filelogger[n] switch. "n" if present can be a digit from 1-9. /fileloggerparameters is also used by any distributed file logger, see description of /distributedFileLogger. (Short for [rest of string was truncated]";. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.HelpMessage_23_ToolsVersionSwitch"> <summary> Looks up a localized string similar to /toolsversion:<version> The version of the MSBuild Toolset (tasks, targets, etc.) to use during build. This version will override the versions specified by individual projects. (Short form: /tv) Example: /toolsversion:3.5 . </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.HelpMessage_24_NodeReuse"> <summary> Looks up a localized string similar to /nodeReuse:<parameters> Enables or Disables the reuse of MSBuild nodes. The parameters are: True --Nodes will remain after the build completes and will be reused by subsequent builds (default) False--Nodes will not remain after the build completes (Short form: /nr) Example: /nr:true . </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.HelpMessage_25_PreprocessSwitch"> <summary> Looks up a localized string similar to /preprocess[:file] Creates a single, aggregated project file by inlining all the files that would be imported during a build, with their boundaries marked. This can be useful for figuring out what files are being imported and from where, and what they will contribute to the build. By default the output is written to the console window. If the path to an [rest of string was truncated]";. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.HelpMessage_26_DetailedSummarySwitch"> <summary> Looks up a localized string similar to /detailedsummary Shows detailed information at the end of the build about the configurations built and how they were scheduled to nodes. (Short form: /ds) . </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.HelpMessage_27_DebuggerSwitch"> <summary> Looks up a localized string similar to /debug Causes a debugger prompt to appear immediately so that Visual Studio can be attached for you to debug the MSBuild XML and any tasks and loggers it uses. . </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.HelpMessage_28_WarnAsErrorSwitch"> <summary> Looks up a localized string similar to /warnaserror[:code[;code2]] List of warning codes to treats as errors. Use a semicolon or a comma to separate multiple warning codes. To treat all warnings as errors use the switch with no values. (Short form: /err[:c;[c2]]) Example: /warnaserror:MSB4130 When a warning is treated as an error the target will continue to execut [rest of string was truncated]";. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.HelpMessage_29_WarnAsMessageSwitch"> <summary> Looks up a localized string similar to /warnasmessage[:code[;code2]] List of warning codes to treats as low importance messages. Use a semicolon or a comma to separate multiple warning codes. (Short form: /nowarn[:c;[c2]]) Example: /warnasmessage:MSB3026 . </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.HelpMessage_3_SwitchesHeader"> <summary> Looks up a localized string similar to Switches: . </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.HelpMessage_4_HelpSwitch"> <summary> Looks up a localized string similar to /help Display this usage message. (Short form: /? or /h) . </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.HelpMessage_5_NoLogoSwitch"> <summary> Looks up a localized string similar to /nologo Do not display the startup banner and copyright message. . </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.HelpMessage_6_VersionSwitch"> <summary> Looks up a localized string similar to /version Display version information only. (Short form: /ver) . </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.HelpMessage_7_ResponseFile"> <summary> Looks up a localized string similar to @<file> Insert command-line settings from a text file. To specify multiple response files, specify each response file separately. Any response files named "msbuild.rsp" are automatically consumed from the following locations: (1) the directory of msbuild.exe (2) the directory of the first project or solution built . </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.HelpMessage_8_NoAutoResponseSwitch"> <summary> Looks up a localized string similar to /noautoresponse Do not auto-include any MSBuild.rsp files. (Short form: /noautorsp) . </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.HelpMessage_9_TargetSwitch"> <summary> Looks up a localized string similar to /target:<targets> Build these targets in this project. Use a semicolon or a comma to separate multiple targets, or specify each target separately. (Short form: /t) Example: /target:Resources;Compile . </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.HelpPrompt"> <summary> Looks up a localized string similar to For switch syntax, type "MSBuild /help". </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.InvalidConfigurationFile"> <summary> Looks up a localized string similar to MSBUILD : Configuration error MSB1043: The application could not start. {0}. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.InvalidExtensionToIgnore"> <summary> Looks up a localized string similar to MSBUILD : error MSB1036: There is an invalid extension in the /ignoreprojectextensions list. Extensions must start with a period ".", have one or more characters after the period and not contain any invalid path characters or wildcards.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.InvalidLoggerError"> <summary> Looks up a localized string similar to MSBUILD : error MSB1019: Logger switch was not correctly formed.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.InvalidMaxCPUCountValue"> <summary> Looks up a localized string similar to MSBUILD : error MSB1030: Maximum CPU count is not valid. {0}. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.InvalidMaxCPUCountValueOutsideRange"> <summary> Looks up a localized string similar to MSBUILD : error MSB1032: Maximum CPU count is not valid. Value must be an integer greater than zero and no more than 1024.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.InvalidNodeNumberValue"> <summary> Looks up a localized string similar to MSBUILD : error MSB1033: Node number is not valid. {0}.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.InvalidNodeNumberValueIsNegative"> <summary> Looks up a localized string similar to MSBUILD : error MSB1034: Node number is not valid. Value must be an integer greater than zero.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.InvalidNodeReuseValue"> <summary> Looks up a localized string similar to MSBUILD : error MSB1042: Node reuse value is not valid. {0}.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.InvalidPreprocessPath"> <summary> Looks up a localized string similar to MSBUILD : error MSB1047: File to preprocess to is not valid. {0}. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.InvalidPropertyError"> <summary> Looks up a localized string similar to MSBUILD : error MSB1006: Property is not valid.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.InvalidSchemaFile"> <summary> Looks up a localized string similar to MSBUILD : MSB1046: The schema "{0}" is not valid. {1}. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.InvalidSwitchIndicator"> <summary> Looks up a localized string similar to Switch: {0}. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.InvalidToolsVersionError"> <summary> Looks up a localized string similar to MSBUILD : error MSB1040: ToolsVersion is not valid. {0}. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.InvalidVerbosityError"> <summary> Looks up a localized string similar to MSBUILD : error MSB1018: Verbosity level is not valid.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.LoggerCreationError"> <summary> Looks up a localized string similar to MSBUILD : error MSB1021: Cannot create an instance of the logger. {0}. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.LoggerFailurePrefixNoErrorCode"> <summary> Looks up a localized string similar to MSBUILD : Logger error {0}: {1}. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.LoggerFailurePrefixWithErrorCode"> <summary> Looks up a localized string similar to MSBUILD : Logger error MSB1029: {0}. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.LoggerFatalError"> <summary> Looks up a localized string similar to MSBUILD : error MSB1028: The logger failed unexpectedly.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.LoggerNotFoundError"> <summary> Looks up a localized string similar to MSBUILD : error 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.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.MissingConsoleLoggerParameterError"> <summary> Looks up a localized string similar to MSBUILD : error MSB1037: Specify one or more parameters for the console logger if using the /consoleLoggerParameters switch. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.MissingFileLoggerParameterError"> <summary> Looks up a localized string similar to MSBUILD : error MSB1038: Specify one or more parameters for the file logger if using the /fileLoggerParameters switch. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.MissingIgnoreProjectExtensionsError"> <summary> Looks up a localized string similar to MSBUILD : error MSB1035: Specify the project extensions to ignore.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.MissingLoggerError"> <summary> Looks up a localized string similar to MSBUILD : error MSB1007: Specify a logger.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.MissingMaxCPUCountError"> <summary> Looks up a localized string similar to MSBUILD : error MSB1031: Specify the maximum number of CPUs.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.MissingNodeReuseParameterError"> <summary> Looks up a localized string similar to MSBUILD : error MSB1041: Specify one or more parameters for node reuse if using the /nodereuse switch. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.MissingProjectError"> <summary> Looks up a localized string similar to MSBUILD : error MSB1003: Specify a project or solution file. The current working directory does not contain a project or solution file.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.MissingPropertyError"> <summary> Looks up a localized string similar to MSBUILD : error MSB1005: Specify a property and its value.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.MissingResponseFileError"> <summary> Looks up a localized string similar to MSBUILD : error MSB1012: Specify a response file.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.MissingTargetError"> <summary> Looks up a localized string similar to MSBUILD : error MSB1004: Specify the name of the target.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.MissingToolsVersionError"> <summary> Looks up a localized string similar to MSBUILD : error MSB1039: Specify the version of the toolset.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.MissingVerbosityError"> <summary> Looks up a localized string similar to MSBUILD : error MSB1016: Specify the verbosity level.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.MissingWarnAsMessageParameterError"> <summary> Looks up a localized string similar to MSBUILD : error MSB1051: Specify one or more warning codes to treat as low importance messages when using the /warnasmessage switch.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.MultipleSchemasError"> <summary> Looks up a localized string similar to MSBUILD : error MSB1024: Only one schema can be specified for validation of the project.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.NeedJustMyCode"> <summary> Looks up a localized string similar to If MSBuild debugging does not work correctly, please verify that the "Just My Code" feature is enabled in Visual Studio, and that you have selected the managed debugger.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.ParameterRequiredError"> <summary> Looks up a localized string similar to MSBUILD : error MSB1049: The {0} parameter must be specified. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.PickedUpSwitchesFromAutoResponse"> <summary> Looks up a localized string similar to Some command line switches were read from the auto-response file "{0}". To disable this file, use the "/noautoresponse" switch.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.PossiblyOmittedMaxCPUSwitch"> <summary> Looks up a localized string similar to Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.ProjectNotFoundError"> <summary> Looks up a localized string similar to MSBUILD : error MSB1009: Project file does not exist.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.ProjectSchemaErrorHalt"> <summary> Looks up a localized string similar to MSBUILD : MSB1045: Stopping because of syntax errors in project file.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.ProjectUpgradeNeededToVcxProj"> <summary> Looks up a localized string similar to MSBUILD : error MSB4192: The project file "{0}" is in the ".vcproj" or ".dsp" file format, which MSBuild cannot build directly. Please convert the project by opening it in the Visual Studio IDE or running the conversion tool, or, for ".vcproj", use MSBuild to build the solution file containing the project instead.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.ReadResponseFileError"> <summary> Looks up a localized string similar to MSBUILD : error MSB1023: Cannot read the response file. {0}. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.RepeatedResponseFileError"> <summary> Looks up a localized string similar to MSBUILD : error MSB1013: The response file was specified twice. A response file can be specified only once. Any files named "msbuild.rsp" in the directory of MSBuild.exe or in the directory of the first project or solution built (which if no project or solution is specified is the current working directory) were automatically used as response files.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.ResponseFileNotFoundError"> <summary> Looks up a localized string similar to MSBUILD : error MSB1022: Response file does not exist.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.SchemaFileLocation"> <summary> Looks up a localized string similar to Validating project using schema file "{0}".. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.SchemaNotFoundError"> <summary> Looks up a localized string similar to MSBUILD : error MSB1026: Schema file does not exist.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.SchemaNotFoundErrorWithFile"> <summary> Looks up a localized string similar to MSBUILD : error MSB1026: Schema file '{0}' does not exist.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.SchemaValidationError"> <summary> Looks up a localized string similar to MSBUILD : MSB1044: Project is not valid. {0}. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.UnexpectedParametersError"> <summary> Looks up a localized string similar to MSBUILD : error MSB1002: This switch does not take any parameters.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.UnknownSwitchError"> <summary> Looks up a localized string similar to MSBUILD : error MSB1001: Unknown switch.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.UnsupportedOS"> <summary> Looks up a localized string similar to MSBUILD : error MSB1015: MSBuild does not run on this version of the operating system. It is only supported on Windows 2000, Windows XP, and later versions.. </summary> </member> <member name="P:PowerBuild.MSBuild.Strings.Using35Engine"> <summary> Looks up a localized string similar to Forcing load of Microsoft.Build.Engine because MSBUILDOLDOM=1.... </summary> </member> <member name="T:PowerBuild.Shared.Strings_shared"> <summary> A strongly-typed resource class, for looking up localized strings, etc. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.ResourceManager"> <summary> Returns the cached ResourceManager instance used by this class. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.Culture"> <summary> Overrides the current thread's CurrentUICulture property for all resource lookups using this strongly typed resource class. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.BuildAborted"> <summary> Looks up a localized string similar to MSB4188: Build was canceled.. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.BuildEngineCallbacksInTaskHostUnsupported"> <summary> Looks up a localized string similar to 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.. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.BuildStarted"> <summary> Looks up a localized string similar to Build started.. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.ConflictingTaskAssembly"> <summary> Looks up a localized string similar to MSB4008: A conflicting assembly for the task assembly "{0}" has been found at "{1}".. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.DirectoryNotFound"> <summary> Looks up a localized string similar to Could not find directory path: {0}. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.ExpectedEventToBeSerializable"> <summary> Looks up a localized string similar to Event type "{0}" was expected to be serializable using the .NET serializer. The event was not serializable and has been ignored.. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.FileLocation"> <summary> Looks up a localized string similar to {0} ({1},{2}). </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.FrameworkLocationHelper_CouldNotGenerateReferenceAssemblyDirectory"> <summary> Looks up a localized string similar to When attempting to generate a reference assembly path from the path "{0}" and the framework moniker "{1}" there was an error. {2}. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.FrameworkLocationHelper_UnsupportedFrameworkVersion"> <summary> Looks up a localized string similar to .NET Framework version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.TargetDotNetFrameworkVersion.. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.FrameworkLocationHelper_UnsupportedFrameworkVersionForWindowsSdk"> <summary> Looks up a localized string similar to .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.. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.FrameworkLocationHelper_UnsupportedVisualStudioVersion"> <summary> Looks up a localized string similar to Visual Studio version "{0}" is not supported. Please specify a value from the enumeration Microsoft.Build.Utilities.VisualStudioVersion.. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.InvalidProjectFile"> <summary> Looks up a localized string similar to MSB4025: The project file could not be loaded. {0}. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.InvalidVerbosity"> <summary> Looks up a localized string similar to MSB4103: "{0}" is not a valid logger verbosity level.. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.MissingProject"> <summary> Looks up a localized string similar to MSBuild is expecting a valid "{0}" object.. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.ModifyingTaskHostEnvironmentHeader"> <summary> Looks up a localized string similar to Making the following modifications to the environment received from the parent node before applying it to the task host:. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.ModifyingTaskHostEnvironmentVariable"> <summary> Looks up a localized string similar to Setting '{0}' to '{1}' rather than the parent environment's value, '{2}'.. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.NameInvalid"> <summary> Looks up a localized string similar to MSB5016: The name "{0}" contains an invalid character "{1}".. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.OM_NotSupportedReadOnlyCollection"> <summary> Looks up a localized string similar to This collection is read-only.. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.Shared_CannotChangeItemSpecModifiers"> <summary> Looks up a localized string similar to "{0}" is a reserved item metadata, and cannot be modified or deleted.. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.Shared_CannotConvertStringToBool"> <summary> Looks up a localized string similar to The string "{0}" cannot be converted to a boolean (true/false) value.. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.Shared_CanNotFindValidMSBuildLocation"> <summary> Looks up a localized string similar to MSB5024: Could not determine a valid location to MSBuild. Try running this process from the Developer Command Prompt for Visual Studio.. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.Shared_FailedCreatingTempFile"> <summary> Looks up a localized string similar to MSB5003: Failed to create a temporary file. Temporary files folder is full or its path is incorrect. {0}. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.Shared_FailedDeletingTempFile"> <summary> Looks up a localized string similar to MSB5018: Failed to delete the temporary file "{0}". {1}. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.Shared_InvalidFilespecForTransform"> <summary> Looks up a localized string similar to The item metadata "%({0})" cannot be applied to the path "{1}". {2}. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.Shared_InvalidProjectFile"> <summary> Looks up a localized string similar to MSB5019: The project file is malformed: "{0}". {1}. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.Shared_KillingProcess"> <summary> Looks up a localized string similar to MSB5002: The task executable has not completed within the specified limit of {0} milliseconds, terminating.. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.Shared_KillingProcessByCancellation"> <summary> Looks up a localized string similar to MSB5021: "{0}" and its child processes are being terminated in order to cancel the build.. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.Shared_ParameterCannotBeNull"> <summary> Looks up a localized string similar to Parameter "{0}" cannot be null.. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.Shared_ParameterCannotHaveZeroLength"> <summary> Looks up a localized string similar to Parameter "{0}" cannot have zero length.. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.Shared_ParametersMustHaveTheSameLength"> <summary> Looks up a localized string similar to Parameters "{0}" and "{1}" must have the same number of elements.. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.Shared_ProjectFileCouldNotBeLoaded"> <summary> Looks up a localized string similar to MSB5020: Could not load the project file: "{0}". {1}. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.Shared_TaskResourceNotFound"> <summary> Looks up a localized string similar to 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.. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.Shared_TaskResourcesNotRegistered"> <summary> Looks up a localized string similar to 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.. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.SolutionParseDuplicateProject"> <summary> Looks up a localized string similar to MSB5004: The solution file has two projects named "{0}".. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.SolutionParseInvalidProjectFileNameCharacters"> <summary> Looks up a localized string similar to MSB5005: Error parsing project section for project "{0}". The project file name "{1}" contains invalid characters.. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.SolutionParseInvalidProjectFileNameEmpty"> <summary> Looks up a localized string similar to MSB5006: Error parsing project section for project "{0}". The project file name is empty.. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.SolutionParseInvalidProjectSolutionConfigurationEntry"> <summary> Looks up a localized string similar to MSB5007: Error parsing the project configuration section in solution file. The entry "{0}" is invalid.. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.SolutionParseInvalidSolutionConfigurationEntry"> <summary> Looks up a localized string similar to MSB5008: Error parsing the solution configuration section in solution file. The entry "{0}" is invalid.. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.SolutionParseNestedProjectError"> <summary> Looks up a localized string similar to MSB5009: Error parsing the nested project section in solution file.. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.SolutionParseNestedProjectUndefinedError"> <summary> Looks up a localized string similar to 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.. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.SolutionParseNoHeaderError"> <summary> Looks up a localized string similar to MSB5010: No file format header found.. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.SolutionParseProjectDepGuidError"> <summary> Looks up a localized string similar to MSB5011: Parent project GUID not found in "{0}" project dependency section.. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.SolutionParseProjectEofError"> <summary> Looks up a localized string similar to MSB5012: Unexpected end-of-file reached inside "{0}" project section.. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.SolutionParseProjectError"> <summary> Looks up a localized string similar to MSB5013: Error parsing a project section.. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.SolutionParseVersionMismatchError"> <summary> Looks up a localized string similar to MSB5014: File format version is not recognized. MSBuild can only read solution files between versions {0}.0 and {1}.0, inclusive.. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.SolutionParseWebProjectPropertiesError"> <summary> Looks up a localized string similar to MSB5015: The properties could not be read from the WebsiteProperties section of the "{0}" project.. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.SubCategoryForSchemaValidationErrors"> <summary> Looks up a localized string similar to Schema validation. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.SubCategoryForSolutionParsingErrors"> <summary> Looks up a localized string similar to Solution file. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.TaskNotMarshalByRef"> <summary> Looks up a localized string similar to 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.. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.UnauthorizedAccess"> <summary> Looks up a localized string similar to You do not have access to: {0}. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.UnrecognizedSolutionComment"> <summary> Looks up a localized string similar to Unrecognized solution version "{0}", attempting to continue.. </summary> </member> <member name="P:PowerBuild.Shared.Strings_shared.UnrecognizedToolsVersion"> <summary> Looks up a localized string similar to MSB4132: The tools version "{0}" is unrecognized. Available tools versions are {1}.. </summary> </member> <member name="T:PowerBuild.Logging.InvokeDomainLogger"> <summary> Wrapper for loggers created in Invoke-MSBuild application domain. </summary> </member> <member name="T:PowerBuild.InvokeMSBuild"> <summary> Use MSBuild to build a project. </summary> <para type="synopsis"> Use MSBuild to build a project. </para> <para type="description"> Builds the specified targets in the project file. If a project file is not specified, MSBuild searches the current working directory for a file that has a file extension that ends in "proj" and uses that file. </para> <example> <code>Invoke-MSBuild -Project Project.sln -Target Build -Property @{Configuration="Release"} -Verbosity Minimal</code> </example> </member> <member name="P:PowerBuild.InvokeMSBuild.DetailedSummary"> <summary> Gets or sets detailed summary parameter. </summary> <para type="description"> Shows detailed information at the end of the build about the configurations built and how they were scheduled to nodes. </para> </member> <member name="P:PowerBuild.InvokeMSBuild.IgnoreProjectExtensions"> <summary> Get or sets project extensions to ignore. </summary> <para type="description"> List of extensions to ignore when determining which project file to build. </para> </member> <member name="P:PowerBuild.InvokeMSBuild.Logger"> <summary> Get or sets logger collection. </summary> <para type="description"> Use this loggers to log events from MSBuild. </para> </member> <member name="P:PowerBuild.InvokeMSBuild.MaxCpuCount"> <summary> Gets or sets number of concurrent processes to build with. </summary> <para type="description"> Specifies the maximum number of concurrent processes to build with. If the switch is not used, the default value used is 1. If the switch is used with a $null, value MSBuild will use up to the number of processors on the computer. </para> </member> <member name="P:PowerBuild.InvokeMSBuild.NodeReuse"> <summary> Gets or sets node reuse. </summary> <para type="description"> Enables or Disables the reuse of MSBuild nodes. </para> </member> <member name="P:PowerBuild.InvokeMSBuild.Project"> <summary> Gets or sets project to build. </summary> <para type="description"> Project to build. </para> </member> <member name="P:PowerBuild.InvokeMSBuild.Property"> <summary> Gets or sets properties. </summary> <para type="description"> Set or override these project-level properties. </para> </member> <member name="P:PowerBuild.InvokeMSBuild.Target"> <summary> Gets or sets targets to build. </summary> <para type="description"> Build these targets in the project. </para> </member> <member name="P:PowerBuild.InvokeMSBuild.ToolsVersion"> <summary> Gets or sets tools version. </summary> <para type="description"> The version of the MSBuild Toolset (tasks, targets, etc.) to use during build.This version will override the versions specified by individual projects. </para> </member> <member name="P:PowerBuild.InvokeMSBuild.Verbosity"> <summary> Gets or sets logging verbosity. </summary> <para type="description"> Display this amount of information in the event log. </para> </member> <member name="P:PowerBuild.BuildResult.CircularDependency"> <summary>Gets a flag indicating whether a circular dependency was detected.</summary> <returns>Returns true if a circular dependency was detected; false otherwise.</returns> </member> <member name="P:PowerBuild.BuildResult.ConfigurationId"> <summary>Gets the configuration ID for this build result set.</summary> <returns>Returns the configuration ID for this build result set.</returns> </member> <member name="P:PowerBuild.BuildResult.Exception"> <summary>Gets the exception generated for this build result set. </summary> <returns>Returns the exception generated for this build result set. Returns false if no exception occurred.</returns> </member> <member name="P:PowerBuild.BuildResult.GlobalRequestId"> <summary>Gets the build request id for this build result set.</summary> <returns>Returns the build request id for this build result set.</returns> </member> <member name="P:PowerBuild.BuildResult.Items"> <summary>Gets an enumerator over all items in this build result set.</summary> <returns>Returns an enumerator over all items in this build result set.</returns> </member> <member name="P:PowerBuild.BuildResult.NodeRequestId"> <summary>Gets the build request ID of the originating node.</summary> <returns>Returns the build request ID of the originating node.</returns> </member> <member name="P:PowerBuild.BuildResult.OverallResult"> <summary>Gets the overall result for this build.</summary> <returns>Returns the overall result for this build.</returns> </member> <member name="P:PowerBuild.BuildResult.ParentGlobalRequestId"> <summary>Gets the global build request ID which issued the request leading to this build result set.</summary> <returns>Returns the global build request ID which issued the request leading to this build result set.</returns> </member> <member name="P:PowerBuild.BuildResult.ResultsByTarget"> <summary>Gets an enumerator over all target results in this build result set.</summary> <returns>Returns an enumerator over all target results in this build result set.</returns> </member> <member name="P:PowerBuild.BuildResult.SubmissionId"> <summary>Gets the build submission which this build result set is associated with.</summary> <returns>Returns the build submission which this build result set is associated with.</returns> </member> <member name="P:PowerBuild.BuildResult.Targets"> <summary>Gets an enumerator over all targets in this build result set.</summary> <returns>Returns an enumerator over all targets in this build result set.</returns> </member> <member name="P:PowerBuild.BuildResult.Item(System.String)"> <summary>Gets an indexer which can be used to get the build result for the given target.</summary> <returns>The build result for the indexed target.</returns> <param name="target">The indexed target.</param> </member> <member name="M:PowerBuild.BuildResult.HasResultsForTarget(System.String)"> <summary>Determines if there are any results for the given target.</summary> <returns>Returns true if results exist; false otherwise.</returns> <param name="target">The target whose results are retrieved.</param> </member> <member name="T:PowerBuild.NewStructuredLogger"> <para type="synopsis"> Create new structured logger. </para> <para type="description"> Create new structured logger. For more details see <see href="https://github.com/KirillOsenkov/MSBuildStructuredLog">MSBuildStructuredLog</see>. </para> <example> <code>New-StructuredLogger -LogFile 1.buildlog</code> </example> </member> <member name="P:PowerBuild.NewStructuredLogger.LogFile"> <para type="description"> Path to the log file into which the build log will be written. Logger supports two formats: *.xml (for large human-readable XML logs) and *.buildlog (compact binary logs). Depending on which file extension you pass to the logger it will either write XML or binary. </para> </member> <member name="T:PowerBuild.NewConsoleLogger"> <para type="synopsis"> Create new console logger. </para> <para type="description"> Create new configured console logger. Parameters are equivalent of msbuild.exe's /consoleloggerparameters:<parameters> switch. </para> <example> <code>New-ConsoleLogger -Verbosity Minimal -PerformanceSummary</code> </example> </member> <member name="P:PowerBuild.NewConsoleLogger.DisableConsoleColor"> <para type="description"> Use the default console colors for all logging messages. </para> </member> <member name="P:PowerBuild.NewConsoleLogger.DisableMPLogging"> <para type="description"> Disable the multiprocessor logging style of output when running in non - multiprocessor mode. </para> </member> <member name="P:PowerBuild.NewConsoleLogger.EnableMPLogging"> <para type="description"> Enable the multiprocessor logging style even when running in non - multiprocessor mode.This logging style is on by default. </para> </member> <member name="P:PowerBuild.NewConsoleLogger.ErrorsOnly"> <para type="description"> Show only errors. </para> </member> <member name="P:PowerBuild.NewConsoleLogger.ForceConsoleColor"> <para type="description"> Use ANSI console colors even if console does not support it. </para> </member> <member name="P:PowerBuild.NewConsoleLogger.ForceNoAlign"> <para type="description"> Does not align the text to the size of the console buffer. </para> </member> <member name="P:PowerBuild.NewConsoleLogger.NoItemAndPropertyList"> <para type="description"> Don't show list of items and properties at the start of each project build. </para> </member> <member name="P:PowerBuild.NewConsoleLogger.NoSummary"> <para type="description"> Don't show error and warning summary at the end. </para> </member> <member name="P:PowerBuild.NewConsoleLogger.PerformanceSummary"> <para type="description"> Show time spent in tasks, targets and projects. </para> </member> <member name="P:PowerBuild.NewConsoleLogger.ShowCommandLine"> <para type="description"> Show TaskCommandLineEvent messages. </para> </member> <member name="P:PowerBuild.NewConsoleLogger.ShowEventId"> <para type="description"> Show eventId for started events, finished events, and messages. </para> </member> <member name="P:PowerBuild.NewConsoleLogger.ShowTimestamp"> <para type="description"> Display the Timestamp as a prefix to any message. </para> </member> <member name="P:PowerBuild.NewConsoleLogger.Summary"> <para type="description"> Show error and warning summary at the end. </para> </member> <member name="P:PowerBuild.NewConsoleLogger.Verbosity"> <para type="description"> Overrides the Verbosity setting for this logger. Default verbosity is Normal. </para> </member> <member name="P:PowerBuild.NewConsoleLogger.WarningsOnly"> <para type="description"> Show only warnings. </para> </member> <member name="T:PowerBuild.NewFileLogger"> <para type="synopsis"> Create new file logger. </para> <para type="description"> Create new configured file logger. Parameters are equivalent of msbuild.exe's /fileloggerparameters:<parameters> switch. </para> <example> <code>New-FileLogger build.log -Verbosity Normal -PerformanceSummary</code> </example> </member> <member name="P:PowerBuild.NewFileLogger.Append"> <summary> </summary> <para type="description"> Determines if the build log will be appended to or overwrite the log file.Setting the switch appends the build log to the log file; Not setting the switch overwrites the contents of an existing log file. The default is not to append to the log file. </para> </member> <member name="P:PowerBuild.NewFileLogger.DisableConsoleColor"> <para type="description"> Use the default console colors for all logging messages. </para> </member> <member name="P:PowerBuild.NewFileLogger.DisableMPLogging"> <para type="description"> Disable the multiprocessor logging style of output when running in non - multiprocessor mode. </para> </member> <member name="P:PowerBuild.NewFileLogger.EnableMPLogging"> <para type="description"> Enable the multiprocessor logging style even when running in non - multiprocessor mode.This logging style is on by default. </para> </member> <member name="P:PowerBuild.NewFileLogger.Encoding"> <para type="description"> Specifies the encoding for the file, for example, UTF-8, Unicode, or ASCII </para> </member> <member name="P:PowerBuild.NewFileLogger.ErrorsOnly"> <para type="description"> Show only errors. </para> </member> <member name="P:PowerBuild.NewFileLogger.ForceConsoleColor"> <para type="description"> Use ANSI console colors even if console does not support it. </para> </member> <member name="P:PowerBuild.NewFileLogger.ForceNoAlign"> <para type="description"> Does not align the text to the size of the console buffer. </para> </member> <member name="P:PowerBuild.NewFileLogger.LogFile"> <para type="description"> Path to the log file into which the build log will be written. </para> </member> <member name="P:PowerBuild.NewFileLogger.NoItemAndPropertyList"> <para type="description"> Don't show list of items and properties at the start of each project build. </para> </member> <member name="P:PowerBuild.NewFileLogger.NoSummary"> <para type="description"> Don't show error and warning summary at the end. </para> </member> <member name="P:PowerBuild.NewFileLogger.PerformanceSummary"> <para type="description"> Show time spent in tasks, targets and projects. </para> </member> <member name="P:PowerBuild.NewFileLogger.ShowCommandLine"> <para type="description"> Show TaskCommandLineEvent messages. </para> </member> <member name="P:PowerBuild.NewFileLogger.ShowEventId"> <para type="description"> Show eventId for started events, finished events, and messages. </para> </member> <member name="P:PowerBuild.NewFileLogger.ShowTimestamp"> <para type="description"> Display the Timestamp as a prefix to any message. </para> </member> <member name="P:PowerBuild.NewFileLogger.Summary"> <para type="description"> Show error and warning summary at the end. </para> </member> <member name="P:PowerBuild.NewFileLogger.Verbosity"> <para type="description"> Overrides the Verbosity setting for this logger. Default verbosity is Detailed. </para> </member> <member name="P:PowerBuild.NewFileLogger.WarningsOnly"> <para type="description"> Show only warnings. </para> </member> <member name="M:PowerBuild.NewFileLogger.ProcessRecord"> <summary> Processes the record. </summary> </member> <member name="T:PowerBuild.NewLogger"> <para type="synopsis"> Create new logger. </para> <para type="description"> Create new logger using class name and assembly. Parameters are equivalent of msbuild.exe's /l:<logger> switch. </para> <example> <code>New-Logger -ClassName FileLogger -Assembly Microsoft.Build.Engine -Parameters "LogFile=MyLog.log;Append;Verbosity=diagnostic;Encoding=UTF-8"</code> </example> </member> <member name="P:PowerBuild.NewLogger.Assembly"> <para type="description"> Logger assembly name or file path. </para> </member> <member name="P:PowerBuild.NewLogger.ClassName"> <para type="description"> Logger class name. Can contain partial or full namespace. </para> </member> <member name="P:PowerBuild.NewLogger.Parameters"> <para type="description"> Parameters passed to logger. </para> </member> <member name="P:PowerBuild.NewLogger.Verbosity"> <para type="description"> Overrides the Verbosity setting for this logger. Default verbosity is Normal. </para> </member> <member name="P:PowerBuild.TargetResult.Exception"> <summary>Gets the exception generated when the target was built.</summary> <returns>Returns the exception generated when the target was built. Return null if no exception occurred.</returns> </member> <member name="P:PowerBuild.TargetResult.Items"> <summary>Gets the set of build items output by the target. </summary> <returns>Returns the set of build items output by the target. </returns> </member> <member name="P:PowerBuild.TargetResult.ResultCode"> <summary>Gets the result code returned when the target was built.</summary> <returns>Returns the result code returned when the target was built.</returns> </member> </members> </doc> |