.net-4.6.1

Why can't Jenkins find this .NET AssemblyFoldersEx registry key?

|▌冷眼眸甩不掉的悲伤 提交于 2019-12-02 09:14:38
So I have a project that builds fine on my development machine, but not on my CI server (Jenkins). Jenkins can't find my Primary Interop Assemblies even after I've copied over various folders from my machine to make them available to it. On my machine, where everything works, I can turn on my Visual Studio's option for "diagnostic"-level output, and I can see how it figures out where these PIA's are at... Primary reference "Microsoft.mshtml, Version=7.0.3300.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a". Resolved file path is "C:\Program Files (x86)\Microsoft.NET\Primary Interop

Confused about behavior of ?. operator

折月煮酒 提交于 2019-12-01 22:07:21
Here is my code class Address { public bool IsAppartment { get; set; } } class Employee { public string Name { get; set; } public Address Address { get; set; } } class Program { static void Main(string[] args) { Employee employee = new Employee() { Name = "Charlie" }; if (employee.Address?.IsAppartment ?? true) { Console.WriteLine("Its an apartment"); } else { Console.WriteLine("No employee address or not an apartment"); } } } The output of this program Its an apartment According to the definition of ?. operator if one operation in a chain of conditional member or element access operations

.Net Framework 4.6.1 not defaulting to TLS 1.2

…衆ロ難τιáo~ 提交于 2019-11-28 16:41:06
Our client have recently upgrade the security protocol to TLS 1.2. Therefore We have our application upgraded to 4.6.1 expecting the security protocol will be default to TLS 1.2 but it is not. Any idea why? Kartik Gupta I had a similar problem and this is what worked for me. open Powershell and check for supported protocols by using [Net.ServicePointManager]::SecurityProtocol Run the following 2 cmdlets to set .NET Framework strong cryptography registry keys : set strong cryptography on 64 bit .Net Framework (version 4 and above) Set-ItemProperty -Path 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\

Type 'Object' is defined in an assembly that is not referenced (NET Standard 2.0/.NET Framework 4.6.1)

喜欢而已 提交于 2019-11-27 14:21:50
问题 I'm using the .NET Standard 2.0 preview, on which my Class Libraries are based. After having trouble with a few NuGet packages, especially regarding archive extraction, I decided to migrate my .NET Core 2.0 Console projects back to the .NET Framework 4.6.1. The .NET Framework 4.6.1 is supposed to implement the .NET Standard 2.0 specification - according to different sources. Especially the dotnet/standard GitHub Repo. Unfortunately, the migration to the .NET Framework resulted in the