The Microsoft .NET Framework 4 Client Profile redistributable package installs the .NET Framework runtime and associated files that are required to run most client applications.The .NET Framework is Microsoft's comprehensive and consistent programming model for building applications that have visually stunning user experiences, seamless and secure communication, and the ability to model a range of business processes.The .NET Framework 4 works side by side with older Framework versions.
In Microsoft SQL Server 2012, capability to correlate a connection ID between the client and the server is added. With this update SqlClient will send the connection ID information so that it can be logged on the server side. Additionally, the following capabilities are added to SqlClient to provide ways to retrieve the connection ID on the client side if it is available:
dotnetfx40 client x86 x32.exe
Click here to view or hide detailed informationIssue 1: Cannot set the WWW-Authenticate HTTP Response header in self-hosted WCF service scenariosIf you have a self-hosted WCF service, you could not send a www-Authenticate HTTP header in the response message. This is required for many custom authentication scenarios, such as enabling OAuth. This limitation was removed.Issue 2: Self-hosted BasicHttp service that uses https enabled fails in partial trustIf you have a self-hosted WCF service that uses BasicHttpBinding with security mode Transport and ClientCredentialType=None or Certificate, you could not run it in partial trust. The client request fails, and you receive the following exception:
Issue 11When a client requests the RESTful web service in an .asmx or a .svc file by using the ASP.NET pipeline and by using the extension-less URL handling, the state of the request might incorrectly change.
In this scenario, the WCF service does not respond to the client request. Additionally, the .svc.compile file incorrectly references the .NET Framework 4.Note The .svc.compile file is generated by the publishing process.
Secure connections using the TLSv1.2 protocol require Connector/NET 8.0.11 or later. In addition, your Microsoft Windows host must have the TLSv1.2 protocol enabled. Connections made using Windows named pipes or shared memory do not support the TLSv1.2 protocol. For general guidance about configuring the server and clients for secure connections, see Configuring MySQL to Use Encrypted Connections.
Connector/NET 6.7 includes new features such as Entity Framework 5 support, built-in Load Balancing (to be used with a back end implementing either MySQL Replication or MySQL Clustering), a Memcached client (compatible with Innodb Memcached plugin) and support for Windows Runtime (WinRT) to write store apps. This version also removes all features related to Visual Studio Integration, which are provided in a separate product, MySQL for Visual Studio.
Connector/NET 6.4 includes new features such as support for Windows authentication (when connecting to MySQL Server 5.5+), table caching on the client side, simple connection fail-over support, and improved SQL generation from the Entity Framework provider.
I tried removing the reference and just adding CrystalDecisions.ReportAppServer.CommLayer as a prerequisite but then I get an error when I try to run the application on the client PC that says CrystalDecisions.ReportAppServer.CommLayer is not in the GAC. 2ff7e9595c
Comentários