Just to add:

And the new list has problems with formatted bug descriptions, i.e. sample code and the like are just contained in the text without further formatting: Cf. this description of ADO:Net error 682773 in the 12.0.1.3924 list:

EF 4.1 is the latest release of Microsoft Entity Framework. The major new feature of EF 4.1 is "Code First". Support has now been added for Code First. Code First enables a different development workflow: defining data model objects by simply writing C# or VB.NET classes mapping to database objects without ever having to open a designer or define an XML mapping file. Optionally, additional configuration can be performed by using data annotations or the Fluent API. Model can be used to generate a database schema or map to an existing database. Here's an example which creates new database objects using the model: using System; using System.Collections.Generic; using System.ComponentModel.DataAnnotations; using System.Data.Entity; using System.Data.Entity.Infrastructure; using System.Linq; using iAnywhere.Data.SQLAnywhere; namespace CodeFirstExample { [Table( "EdmCategories", Schema = "DBA" )] public class Category { public string CategoryId { get; set; } [MaxLength( 64 )] public string Name { get; set; } public virtual ICollection<product> Products { get; set; } } [Table( "EdmProducts", Schema = "DBA" )] public class Product { public int ProductId { get; set; } [MaxLength( 64 )] public string Name { get; set; } public string CategoryId { get; set; } public virtual Category Category { get; set; } } [Table( "EdmSuppliers", Schema = "DBA" )] public class Supplier { [Key] public string SupplierCode { get; set; } [MaxLength( 64 )] public string Name { get; set; } } public class Context : DbContext { public Context() : base() { } public Context( string connStr ) : base( connStr ) { } public DbSet<category> Categories { get; set; } public DbSet<product> Products { get; set; } public DbSet<supplier> Suppliers { get; set; } protected override void OnModelCreating( DbModelBuilder modelBuilder ) { modelBuilder.Entity<supplier>().Property( s => s.Name ).IsRequired(); } } class Program { static void Main( string[] args ) { Database.DefaultConnectionFactory = new [...]

Possibly the file should be named "Try to Read me":)

You won't necessarily have to install the EBF to get access to the EBF documentation: the zip file (e.g. the SA16 EBF21592.zip) contains the file ReadMe_EBF.html. That's exactly the thing missing on the web page. But you still will have to download tons of MB before getting access to that information.

So I support the request for bringing that information back to the download page.

That may be true for the Windows 11.0.1.2960 EBF, but that is a SAP-ified re-release of the original 11.0.1.2960 EBF that was issued on April 16.

It is NOT true for the recent SAPified-only Windows 16.0.0.1644 EBF issued on September 13. That download contains 4 files; two useless SAP-ified text files, a new crappy text-style HTML read-me, and a file called EBF21802.zip which contains one single file: SA16_Windows.1600_1644_EBF.exe... that's the setup.exe file, and there is NO SIGN of the old-style HTML read-me.

Alas. Maybe that read-me will magically appear somewhere if you actually run the setup, but that's big step backwards.

Oh, well... I suppose it could be worse... SAP could start charging for EBFs.