Merge pull request #1452 from PowerShell/vors/remove-links

Remove unusable links from the source code
This commit is contained in:
Lee Holmes
2016-07-21 13:12:28 -07:00
committed by GitHub
3 changed files with 4 additions and 8 deletions
@@ -1305,9 +1305,8 @@ namespace Microsoft.PowerShell.Workflow
AddParameter("Depth", 10).
AddParameter("Path", tempPath).Invoke();
throw new Exception("Bug MSFT:246456 detected. Please capture " + tempPath + ", attach it to " +
"https://microsoft.visualstudio.com/DefaultCollection/WSSC/_workItems#id=246456&_a=edit, and " +
"then reassign the bug to leeholm.");
throw new Exception("Bug MSFT:246456 detected. Please capture " + tempPath + ", open a new issue " +
"at https://github.com/PowerShell/PowerShell/issues/new and attach the file.");
}
else
{
@@ -190,8 +190,7 @@ namespace System.Management.Automation.Security
// Temp path can sometimes be deleted. While many places in PowerShell depend on its existence,
// this one can crash PowerShell.
// A less sensitive implementation will be possible once AppLocker allows validation of files that
// don't exist:
// https://microsoft.visualstudio.com/DefaultCollection/WSSC/_workitems#_a=edit&id=1908704
// don't exist.
//
string testPathScript = null;
@@ -56,7 +56,6 @@ namespace System.Management.Automation.Internal
// Initialize EventSourceOptions for Writing informational messages
// WdiContext will ensure Universal Telemetry Client [UTC] will upload telemetry messages to Cosmos/xPert pipeline
// https://microsoft.sharepoint.com/teams/osg_core_fun/idt/OSGInstrument/SitePages/How%20to%20upload%20EventSource%20events.aspx
// MeasuresKeyword is to indicate that event is for understanding measures and reporting scenarios.
// This keyword results in the generation of Asimov compatible events for telemetry
@@ -90,8 +89,7 @@ namespace System.Management.Automation.Internal
/// </summary>
// EventSource data gets raised on the Client containing OS Environment information and supplied arguments as "data"
// Events are queued and uploaded to Cosmos/xPert. Here is a way of accessing the telemetry data:
// http://xpert/osg/?view=Search&source=PROD&start=3.06.2015-19.41&end=3.06.2015-21.41
// Events are queued and uploaded to Cosmos/xPert.
// Format of data generated on the Client:
// {
// "ver": "2.1",