Today, we’re announcing that Microsoft 365 apps and services will no longer support Internet Explorer 11 (IE 11) by this time next year.
This is the first major-version release we’ve had in about three years (Autofac 4.0 was released in August 2016). There are some breaking changes and new features you should know about as you decide your upgrade strategy. Hopefully this will help you navigate those waters.
{
"dependencies": {
"Microsoft.Extensions.Caching.SqlServer": "1.1.0"
},
"tools": {
"Microsoft.Extensions.Caching.SqlConfig.Tools": "1.1.0-preview4-final"
}
} dotnet sql-cache create "Data Source=(localdb)\MSSQLLocalDB;Initial Catalog=sql_cache;Integrated Security=True;" "dbo" "AppSqlCache"
CREATE TABLE AppSqlCache ( Id NVARCHAR (449) COLLATE SQL_Latin1_General_CP1_CS_AS NOT NULL, Value VARBINARY (MAX) NOT NULL, ExpiresAtTime DATETIMEOFFSET NOT NULL, SlidingExpirationInSeconds BIGINT NULL, AbsoluteExpiration DATETIMEOFFSET NULL, CONSTRAINT pk_Id PRIMARY KEY (Id) ); CREATE NONCLUSTERED INDEX Index_ExpiresAtTime ON AppSqlCache(ExpiresAtTime);
public class AppSqlCache
{
public string Id { get; set; }
public byte[] Value { get; set; }
public DateTimeOffset ExpiresAtTime { get; set; }
public long? SlidingExpirationInSeconds { get; set; }
public DateTimeOffset? AbsoluteExpiration { get; set; }
} public class MyDBDataContext : DbContext
{
public virtual DbSet<AppSqlCache> AppSqlCache { get; set; }
protected override void OnModelCreating(ModelBuilder modelBuilder)
{
modelBuilder.Entity<AppSqlCache>(entity =>
{
entity.ToTable(name: "AppSqlCache", schema: "dbo");
entity.HasIndex(e => e.ExpiresAtTime).HasName("Index_ExpiresAtTime");
entity.Property(e => e.Id).HasMaxLength(449);
entity.Property(e => e.Value).IsRequired();
});
}
} public void ConfigureServices(IServiceCollection services)
{
services.AddDistributedSqlServerCache(options =>
{
options.ConnectionString = @"Data Source=(localdb)\MSSQLLocalDB;Initial Catalog=sql_cache;Integrated Security=True;";
options.SchemaName = "dbo";
options.TableName = "AppSqlCache";
}); public IActionResult Index()
{
HttpContext.Session.SetString("User", "VahidN");
return Json(true);
}
public IActionResult About()
{
var userContent = HttpContext.Session.GetString("User");
return Json(userContent);
} 
services.Add(ServiceDescriptor.Singleton<IDistributedCache, SqlServerCache>());
using System;
using System.Text;
using Microsoft.AspNetCore.Mvc;
using Microsoft.Extensions.Caching.Distributed;
namespace Core1RtmEmptyTest.Controllers
{
public class CacheTestController : Controller
{
readonly IDistributedCache _cache;
public CacheTestController(IDistributedCache cache)
{
_cache = cache;
}
public IActionResult SetCacheData()
{
var time = DateTime.Now.ToLocalTime().ToString();
var cacheOptions = new DistributedCacheEntryOptions
{
AbsoluteExpiration = DateTime.Now.AddYears(1)
};
_cache.Set("Time", Encoding.UTF8.GetBytes(time), cacheOptions);
return View();
}
public IActionResult GetCacheData()
{
var time = Encoding.UTF8.GetString(_cache.Get("Time"));
ViewBag.data = time;
return View();
}
public bool RemoveCacheData()
{
_cache.Remove("Time");
return true;
}
}
} Value VARBINARY (MAX) NOT NULL,
public byte[] Value { get; set; } 
<distributed-cache name="MyCacheItem2" expires-sliding="TimeSpan.FromMinutes(30)"> <p>From distributed-cache</p> @DateTime.Now.ToString() </distributed-cache>
1. .NET has better Performance
2. Node.js requires to mix & match languages to compensate for performance
3. C# is an amazing language
4. Best tooling available
5. Easier built-in development loop
6. Stable ecosystem
7. Compliance, privacy, and security
از Microsoft.Data.SqlClient 4 به بعد، حالت اتصال امن، پیشفرض شدهاست و اگر برنامه و سرور شما از این حالت پشتیبانی نمیکنند، از کار خواهند افتاد. برای بازگشت به حالت قبل، Encrypt=False را به رشتهی اتصالی خود اضافه کنید:
server=.;database=LicenseManager;integrated security=True;Encrypt=False"
this only affects the 4.x series. The much older .NET 3.5 SP 1 will continue to be supported. In this context, support means having access to technical support, security updates, and hotfixes.
As previously announced, starting January 12, 2016 Microsoft will no longer provide security updates, technical support or hotfixes for .NET 4, 4.5, and 4.5.1 frameworks. All other framework versions, including 3.5, 4.5.2, 4.6 and 4.6.1, will be supported
