By default, the remote debugger negotiates the strongest Windows authentication provider that can be used between the Visual ...

By default, the remote debugger negotiates the strongest Windows authentication
                provider that can be used between the Visual Studio computer and the remote debugger's
                computer. Today, this will generally be Kerberos authentication if both computers
                are on the same domain. This is done to provide the best possible security.
                

                The '/ntlm' option instructions the remote debugger to instead use NTLM authentication
                provider. This option is generally not recommended. However, it can be very useful
                in situations where Kerberos is failing to authenticate.

Build {0} in project {1} has flavor {2} and platform {3} values longer than 440 characters combined, will be truncated in ... By checking this box, I confirm that I would like to proceed with upgrade using the FULL recovery model, and have sufficient ... By convention, .NET events have two parameters that specify the event sender and event data. Event handler signatures should ... By default, the Remote Debugger Configuration dialog configures the Windows Firewall rule to apply to all network profiles ... By default, the remote debugger negotiates the strongest Windows authentication provider that can be used between the Visual ... By default, this build machine will run a build controller as well as whatever number of build agents you select below. Build ... By default, when /DEBUG is specified, the linker creates a program database (PDB) which holds debugging information. The ... By deleting these configuration settings, you will remove reporting functionality from all the team projects associated with ... By deleting these configuration settings, you will remove SharePoint Products functionality from all the team projects associated ...