| Building a Custom Data Provider for Use with the .NET Data Access Framework |
| MSDN |
| The System.Data.dll assembly in the .NET Framework contains namespaces whose base classes can be used to create custom data providers. These namespaces also define a number of data access interfaces and base classes that let developers create data providers that will interoperate with other custom providers. Using the ADO.NET classes Connection, Command, DataReader, and DataAdapter, writing a provider is easier than writing one for OLE DB. This article explains these classes and their implementation, and how they can be used to write a variety of different kinds of data providers. |
|
| Commands in ADO .NET |
| MSDN |
| In ADO there are three possible ways to update a data source. One is through direct SQL commands, like INSERT, DELETE and UPDATE, or more complex and sophisticated stored procedures. Another is through batch update, where you submit a new image of a certain table to the server all at once. The third way is through direct fields update using server cursors. |
|
| Real SOAP Security |
| MSDN |
| I have a confession to make. I have been writing and speaking about SOAP for over two years, constantly trumpeting SOAP's ability to meet real-world security demands. I must confess that in reality, there is almost no mention at all of security in the SOAP specification. You could say that SOAP, as it exists today, is not secure. But don't stop the presses in order to blast headlines exposing The Great XML Web Services Security Hoax just yet. First of all, the 17 people who have read my columns could hardly constitute the use of such an adjective as "Great." Secondly, despite the fact that SOAP as we know it today has no real support for security, there are secure XML Web Services in existence today. More importantly, there will be even better security for SOAP in the future.
|
|
| Updated Web Services Secure Conversation Language (WS-SecureConversation) |
| MSDN |
| Updated Web Services Secure Conversation Language (WS-SecureConversation) |
|
| Updated Web Services Trust Language (WS-Trust) |
| MSDN |
| Updated Web Services Trust Language (WS-Trust) |
|
| Verify and Add Digital Signatures to Form Data in InfoPath 2003 Using MSXML 5.0 or .NET Framework Managed Code |
| MSDN |
| Learn how to build managed code applications that employ MSXML 5.0 and .NET Framework code to add and verify digital signatures in InfoPath forms. |
|
| Web Services Enhancements 2.0 Support for WS-Policy |
| MSDN |
| Want to write less code and interoperate more? Use the assertions support in WSE 2.0 and the standard expressions for Web service applications in WS-Policy to enter a whole new age of reason. |
|
| WS-Security Drilldown in Web Services Enhancements 2.0 |
| MSDN |
| Use WSE 2.0 to implement security, trust, and secure conversations in Web services architecture. See the security-related changes since WSE 1.0. |
|
| XML Signatures |
| C# Corner |
| Security is a main concern in any application development especially where there is an exchange of critical information with an external system. There are ways to securely send and receive data such as HTTPS and Public Key Cryptography. In today’s world, XML has become a standard means for data communication between applications. Recent specifications from W3C on XML Signature addresses the issue of securely sending and receiving data that complies with most of the algorithms, PGP, RSA DSA etc. In this article we will explore XML Signature specification from W3C and its implementation in .NET using C#. |
|
