No my issue has not been resolved. Here what I have done so far:
If I used this script to create an Assembly
create assembly [system.net.http]
from 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\System.Net.Http.dll'
with permission_set = unsafe;
go
Then I got this error:
Warning: The Microsoft .NET Framework assembly 'system.net.http, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
Msg 10327, Level 14, State 1, Line 3
CREATE ASSEMBLY for assembly 'System.Net.Http' failed because assembly 'System.Net.Http' is not trusted. The assembly is trusted when either of the following is true: the assembly is signed with a certificate or an asymmetric key that has a corresponding login with UNSAFE ASSEMBLY permission, or the assembly is trusted using sp_add_trusted_assembly.
Then I used the script below to create the assembly using the sp_add_trusted_assembly as suggested by the error above.
EXEC sp_configure 'clr enabled', 1;
RECONFIGURE;
declare @assembly varbinary(max) =0x4D5A90000300000004000000FFFF0000B800000000000000400000000000000000000000000000000000000000000000000000000000000000000000800000000E1FBA0E00B409CD21B8014CCD21546869732070726F6772616D2063616E6E6F742062652072756E20696E20444F53206D6F64652E0D0D0A2400000000000000504500004C010300DCF40A660000000000000000E00022200B013000001A000000060000000000003A380000002000000040000000000010002000000002000004000000000000000600000000000000008000000002000000000000030060850000100000100000000010000010000000000000100000000000000000000000E83700004F00000000400000C002000000000000000000000000000000000000006000000C000000B03600001C0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000200000080000000000000000000000082000004800000000000000000000002E746578740000004018000000200000001A000000020000000000000000000000000000200000602E72737263000000C00200000040000000040000001C0000000000000000000000000000400000402E72656C6F6300000C000000006000000002000000
declare @hash varbinary(64) = HASHBYTES('SHA2_512', @assembly);
EXEC sys.sp_add_trusted_assembly @hash, N'system.net.http, version=4.2.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a.';
The trusted System.Net.Http assembly created. How do i know? Because if the used the script above again. SSMS told me it is already trusted (see below)
Configuration option 'clr enabled' changed from 1 to 1. Run the RECONFIGURE statement to install.
Msg 10345, Level 16, State 1, Procedure sys.sp_add_trusted_assembly, Line 1 [Batch Start Line 8]
The assembly hash '0xE1D04DC51869A558CCAECBE7A07CD3C1E7D8F1FA096A1E1D83EA2FAE91A27DA940659353E6E3BC66238FCC3E77854B1C289EB3EA3E56F9F97BC84B62122A0C69' is already trusted.
The problem is when I try to publish my CLR C# Stored Procedure again I got the same error
Creating [FUSEAutomation]...
(47,1): SQL72014: .Net SqlClient Data Provider: Msg 6503, Level 16, State 12, Line 1 Assembly 'system.net.http, version=4.2.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a.' was not found in the SQL catalog.
(47,0): SQL72045: Script execution error. The executed script:
CREATE ASSEMBLY [FUSEAutomation]
AUTHORIZATION [dbo]
FROM 0x4D5A90000300000004000000FFFF0000B800000000000000400000000000000000000000000000000000000000000000000000000000000000000000800000000E1FBA0E00B409CD21B8014CCD21546869732070726F6772616D2063616E6E6F742062652072756E20696E20444F53206D6F64652E0D0D0A2400000000000000504500004C010300DCF40A660000000000000000E00022200B013000001A000000060000000000003A380000002000000040000000000010002000000002000004000000000000000600000000000000008000000002000000000000030060850000100000100000000010000010000000000000100000000000000000000000E83700004F00000000400000C002000000000000000000000000000000000000006000000C000000B03600001C0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000200000080000000000000000000000082000004800000000000000000000002E746578740000004018000000200000001A000000020000000000000000000000000000200000602E72737263000000C00200000040000000040000001C0000000000000000000000000000400000402E72656C6F6300000C000000006000000002000000
An error occurred while the batch was being executed.
I am not sure where to go from here.