A correctly implemented Dispose method can be called multiple times without throwing an exception. However, this is not guaranteed and to avoid generating a System.ObjectDisposedException you should not call Dispose more than one time on an object.
A copy of this file has previously been checked out to this machine. Do you want this copy to replace the previous one as ...
A copy of this file has previously been edited on this machine. Do you want this copy to replace the previous one as the ...
A copy of this file is checked out on another machine. The server copy may not contain your latest changes. Would you like ...
A copy of virtual machine will be stored in library for later reuse. Depending on the size of the virtual machine, this could ...
A correctly implemented Dispose method can be called multiple times without throwing an exception. However, this is not guaranteed ...
A crash report for this problem was recently created; a new crash report for this occurrence of the problem is not being ...
A crash report has been prepared for Microsoft using the Watson Crash Reporting Mechanism. The prepared report has been queued ...
A crash report is being prepared for Microsoft using the Watson Crash Reporting Mechanism. The prepared report will be queued ...
A critical exception was thrown when the '{0}' rule was applied. The exception text is: {1}. Static code analysis has been ...