VSLG1012: Unable to create event '{0}'. Another logger with the same name might be running, or the object name might be in use by another application.
VS1726: Cannot list all the linked work items because you are not connected to the following Team Foundation Servers: {0}. ...
VS1729: There is not enough memory to finish generating the diagram. Try using a smaller call depth or more restrictive filters. ...
VSIP: Package '%s' intentionally omitted from load ( GUID = %s ). Run 'vsaenv /resetskippkgs' to clear all skipped packages. ...
VSLG1001: Logger name '{0}' is not valid. Logger name must contain only letters, number, period(.), dash (-) or underscore ...
VSLG1012: Unable to create event '{0}'. Another logger with the same name might be running, or the object name might be in ...
VSLG4004: TracelogProfiler.dll is not registered; historical data may fail to record. Use 'regsvr32 TracelogProfiler.dll' ...
VSLG4005: 32-bit TracelogProfiler.dll is not registered; historical data may fail to record for 32-bit processes. Use 'regsvr32 ...
VSLG4006: 64-bit TracelogProfiler.dll is not registered; historical data may fail to record for 64-bit processes. Use 'regsvr32 ...
VSP 7003: "{0}" Failed to stop monitor. This could happen if VSPerfMon.exe is detached before VSPerfASPNetCmd.exe finished ...