Wakatime does not work in SSMS v18.10

[Slavchew]

Hello, I followed the instructions and did everything I found here in the Problems section, but it still doesn't report anything. If anyone can help I would be very gratefulл This is my SSMS about:

SQL Server Management Studio 15.0.18390.0 SQL Server Management Objects (SMO) 16.100.46521.71 Microsoft Analysis Services Client Tools 15.0.19714.0 Microsoft Data Access Components (MDAC) 10.0.19041.1 Microsoft MSXML 3.0 6.0 Microsoft .NET Framework 4.0.30319.42000 Operating System 10.0.19043

[togabrennan]

I'm seeing the same issue here with SSMS v18.10.

`

246

<time>2022/02/07 15:48:58.966</time>
<type>Information</type>
<source>VisualStudio</source>
<description>Begin package load [WakaTimePackage]</description>
<guid>{52D9C3FF-C893-408E-95E4-D7484EC7FA47}</guid>

247 2022/02/07 15:48:58.970 Error VisualStudio CreateInstance failed for package [WakaTimePackage]Source: 'mscorlib' Description: Could not load file or assembly 'file:///c:\program files (x86)\microsoft sql server management studio 18\common7\ide\extensions\wakatime\WakaTime.dll' or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515) System.IO.FileLoadException: Could not load file or assembly 'file:///c:\program files (x86)\microsoft sql server management studio 18\common7\ide\extensions\wakatime\WakaTime.dll' or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515) File name: 'file:///c:\program files (x86)\microsoft sql server management studio 18\common7\ide\extensions\wakatime\WakaTime.dll' ---> System.NotSupportedException: An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework. This release of the .NET Framework does not enable CAS policy by default, so this load may be dangerous. If this load is not intended to sandbox the assembly, please enable the loadFromRemoteSources switch. See http://go.microsoft.com/fwlink/?LinkId=155569 for more information. at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) at System.Reflection.RuntimeAssembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) at System.Reflection.RuntimeAssembly.InternalLoadFrom(String assemblyFile, Evidence securityEvidence, Byte[] hashValue, AssemblyHashAlgorithm hashAlgorithm, Boolean forIntrospection, Boolean suppressSecurityChecks, StackCrawlMark& stackMark) at System.Reflection.Assembly.LoadFrom(String assemblyFile, Evidence securityEvidence) at System.Activator.CreateInstanceFromInternal(String assemblyFile, String typeName, Boolean ignoreCase, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, Evidence securityInfo) at System.AppDomain.CreateInstanceFrom(String assemblyFile, String typeName) System.NotSupportedException: An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework. This release of the .NET Framework does not enable CAS policy by default, so this load may be dangerous. If this load is not intended to sandbox the assembly, please enable the loadFromRemoteSources switch. See http://go.microsoft.com/fwlink/?LinkId=155569 for more information. {52D9C3FF-C893-408E-95E4-D7484EC7FA47}

---

80004005 - E_FAIL ` SQL Server Management Studio 15.0.18390.0 SQL Server Management Objects (SMO) 16.100.46521.71 Microsoft Analysis Services Client Tools 15.0.19714.0 Microsoft Data Access Components (MDAC) 10.0.22000.1 Microsoft MSXML 3.0 4.0 6.0 Microsoft .NET Framework 4.0.30319.42000 Operating System 10.0.22000

[ErivandoBR]

Same here, SSMS v18.10 is not working.

API Key is OK, but it doesn't register in the dashboard.

Visual Studio and others are working.

[gandarez]

The extension has been bumped to version 3.0.0. Please follow the updated instructions on README to reinstall it.

[ErivandoBR]

The extension has been bumped to version 3.0.0. Please follow the updated instructions on README to reinstall it.

I confirm, Wakatime 3.0.0 working perfectly on SSMS v18.10 and v18.9.1.

Thank you very much.

[RicardoNoerr]

Having same issue with SSMS 20 when wakatime installed