Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

Sample analysis of ADO.NET assemblies

2025-03-30 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Development >

Share

Shulou(Shulou.com)06/02 Report--

This article mainly shows you the "sample analysis of ADO.NET assemblies", which is easy to understand and well-organized. I hope it can help you solve your doubts. Let the editor lead you to study and study the "sample analysis of ADO.NET assemblies".

Strongly named ADO.NET assemblies

The strong name (or digital signature) consists of the identity of the assembly, which includes the simple text name, version number, and culture information (if provided), public key, and digital signature of the assembly. The digital signature is generated from the assembly file using the appropriate private key. The assembly file contains the assembly manifest, which contains the names and hashes of all the files that make up the assembly.

Strongly named assemblies provide an identity for an application or component that other software can use to explicitly reference an application or component. Strong naming protects assemblies from impersonation of assemblies that contain malicious code. Strong naming also ensures version consistency between different versions of the component. Assemblies that will be deployed to the global assembly cache (GAC) must be strongly named.

ConnectionString syntax

The following example shows how to use the connectionStrings element of a configuration file to allow only specific connection strings. For more information about storing and retrieving connection strings from configuration files, see connection strings (ADO.NET).

KeyRestrictions syntax

The following example enables the same connection string, enables the Encrypt and PacketSize connection string options, but restricts the use of any other connection string options.

Containing the syntax of KeyRestrictionBehavior for PreventUsage, the following example enables the same connection string and allows the use of all connection parameters except User Id, Password, and Persist Security Info.

The above is all the content of the article "sample Analysis of ADO.NET assemblies". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Development

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report