از نسخه 1.9 به بعد از jQuery حذف شده است
The jQuery.browser() method has been deprecated since
jQuery 1.3 and is removed in 1.9. If needed, it is available
عبارت using و نحوه استفاده صحیح از آن
نگاهی به استاندارد ECMA-335
Edition | Release Date | CLR Version | Significant Changes |
---|---|---|---|
1st | December 2001 | 1.0 (February 2002) | N/A |
2nd | December 2002 | 1.1 (April 2003) | |
3rd | June 2005 | 2.0 (January 2006) | See below (link) |
4th | June 2006 | None, revision of 3rd edition (link) | |
5th | December 2010 | 4.0 (April 2010) | See below (link) |
6th | June 2012 | None, revision of 5th edition (link) |
In order to cleanse the data as we parse it, we thought using a try/catch would be ok. If we don’t catch the exceptions, we’re good, right?
Turns out it kills our performance when we throw a lot of exceptions, even if we don’t catch them. Each exception has some costs . We needed to find a way to handle this data without involving exceptions.
TryParse turns out to be a method designed to solve our problem. We ran some benchmarks to prove it.
The fourth preview of Entity Framework Core (EF Core) 8 is available on NuGet today!
Basic information
EF Core 8, or just EF8, is the successor to EF Core 7, and is scheduled for release in November 2023, at the same time as .NET 8.
EF8 previews currently target .NET 6, and can therefore be used with either .NET 6 (LTS) or .NET 7. This will likely be updated to .NET 8 as we near release.
EF8 will align with .NET 8 as a long-term support (LTS) release. See the .NET support policy for more information.
کار با کلیدهای اصلی و خارجی در EF Code first
public class Tb1 { public Tb1() { ListTb2 = new List<Tb2>(); } public int Id { get; set; } public string NameTb1 { get; set; } public virtual ICollection<Tb2> ListTb2 { get; set; } } public class Tb2 { public Tb2() { ListTb1 = new List<Tb1>(); } public int Id { get; set; } public string NameTb2 { get; set; } public virtual ICollection<Tb1> ListTb1 { get; set; } }
public class Tb1Map : EntityTypeConfiguration<Tb1> { public Tb1Map() { this.HasKey(x => x.Id); this.HasMany(x => x.ListTb2) .WithMany(xx => xx.ListTb1) .Map ( x => { x.MapLeftKey("Tb1Id"); x.MapRightKey("Tb2Id"); x.ToTable("Tb1Tb2"); } ); } } public class Tb2Map : EntityTypeConfiguration<Tb2> { public Tb2Map() { this.HasKey(x => x.Id); } }
var sv1 = new TableService<Tb1>(_uow); var sv2 = new TableService<Tb2>(_uow); var t1 = new Tb1 { NameTb1 = "T111" }; sv1.Add(t1); //var res1= _uow.SaveChanges(); var t2 = new Tb2 { NameTb2 = "T222" }; sv2.Add(t2); //var res2 = _uow.SaveChanges(); t1.ListTb2.Add(t2); var result = _uow.SaveChanges();
An error occurred while saving entities that do not expose foreign key properties for their relationships. The EntityEntries property will return null because a single entity cannot be identified as the source of the exception. Handling of exceptions while saving can be made easier by exposing foreign key properties in your entity types. See the InnerException for details.
{"The INSERT statement conflicted with the FOREIGN KEY constraint \"FK_Tb1Tb2_Tb2\". The conflict occurred in database \"dbTest\", table \"dbo.Tb2\", column 'Id'.\r\nThe statement has been terminated."}
Mapper.CreateMap<Employee, EmployeeDto>() .ForMember(d => d.FullName, opt => opt.MapFrom(src => src.FirstName + " " + src.LastName)); var employees = await db.Employees.ProjectTo<EmployeeDto>().ToListAsync();
public class Employee { [Computed] public string FullName { get { return FirstName + " " + LastName; } } } Mapper.CreateMap<Employee, EmployeeDto>(); var employees = await db.Employees.ProjectToListAsync<EmployeeDto>();
23.Visual Studio 2017 15.9 منتشر شد
Issues Fixed in 15.9.23
- Fixed C++ compiler bug for proper folding of inline variable dynamic initializers. Ported from the VS 2019 16.0 release.
- Security improvements in vctip.exe.
- A change to enable Enterprise IT administrators and deployment engineers to configure tools like Microsoft Update client & SCCM to determine applicability of VS2017 updates hosted on Microsoft Update Catalog & WSUS.