'The Online Service is not available' Issue in Visual Studio Professional 2013 with Update 5

From here: windows - 'The Online Service is not available' Issue in Visual Studio Professional 2013 with Update 5 - Stack Overflow

I have worked in vscode 2013 until today. But when I'm trying to open my IDE in today morning, it gets 'Your license has gone stale and must be update' error message as following.

enter image description here

and after I tried to update license and sign In operations. when I'm trying to these two it gets 'The Online service is not available. Please try again later' error message as following.

enter image description here

I'm using windows operating system. Is anyone know how to solve this?

 

Solution:

ry this; it worked for me. Just add two DWORD values to the Windows Registry. Site go.microsoft.com now supports only TLS1.2 protocol.

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319]
  • "SystemDefaultTlsVersions"=dword:00000001
  • "SchUseStrongCrypto"=dword:00000001

Source

enter image description here

Cannot update Visual Studio 2013 License

For some reason I could not update my VS 2013 license today! The service was not available until I entered these registry Keys!

How to enable Transport Layer Security (TLS) 1.2 on clients - Configuration Manager | Microsoft Learn

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v2.0.50727]
"SystemDefaultTlsVersions" = dword:00000001
"SchUseStrongCrypto" = dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
"SystemDefaultTlsVersions" = dword:00000001
"SchUseStrongCrypto" = dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v2.0.50727]
"SystemDefaultTlsVersions" = dword:00000001
"SchUseStrongCrypto" = dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319]
"SystemDefaultTlsVersions" = dword:00000001
"SchUseStrongCrypto" = dword:00000001

How to Specify Assembly References Based On Build Configuration

To "Dynamically" change the path of a Reference in Visual Studio you first need to Unload the Project, then Edit the *proj file.

Go down to the References Section change the Hard Coded Path to $(Configuration). This will dynamically change the reference when the Configuration is changed.

    <Reference Include="Dafran.Exceptions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=08f619978b79cd15, processorArchitecture=MSIL">

      <SpecificVersion>False</SpecificVersion>

      <HintPath>\\zero\Builds\Dafran.Security\$(Configuration)\Dafran.Exceptions.dll</HintPath>

    </Reference>

How to disable Javascript Debugging in IE11?

From here: http://superuser.com/questions/803943/how-to-disable-javascript-debugging-in-ie11

The options in VS for exceptions to determine if the debugger should break on an exception. Though VS will always break on an unhandled exception and a language break (debugger). The options do not stop the script debugger from being attached when you launch IE from VS.

The options in VS to enable or disable JIT debugging change just the just-in-time debug feature. Enabling JIT debug simply means that if a running application not launched by VS hits a break condition the user should be prompted if they want to attach VS to debug the application. This also don't change if script debugging is enabled when you launch IE from VS.

The options in Internet Explorer to disable script debugging only changes if IE should run with debugging enabled always. In IE11 with VS2013 this feature is never needed but is there to support older versions of VS.

The easiest way to get the behavior you want is to do:
1. Right click on a aspx/html file there is a ‘Browse with…’ item. This will bring up a dialog to configure your browser.

2. Click the Add button. Add something like:
    Path: c:\Program Files (x86)\Internet Explorer\iexplore.exe
    Friendly name: Internet Explorer (no debug)

3. Set that as your default

This basically launches IE outsie Visual Studio so that those annoying Javascript errors stop happening. You will still be able to debug your code though.