Search Forum
(57415 Postings)
Search Site/Articles

Archived Articles
712 Articles

C# Books
C# Consultants
What Is C#?
Download Compiler
Code Archive
Archived Articles
Advertise
Contribute
C# Jobs
Beginners Tutorial
C# Contractors
C# Consulting
Links
C# Manual
Contact Us
Legal

GoDiagram for .NET from Northwoods Software www.nwoods.com


              
Printable Version

Demo Networked Financial Systems Using C# and .NET: A Case Study
By Abebe Assefa

Contents

RequirementsKY
Objective
Technology Coverage
Overall Layout
Client Side Components
Remoting and Cryptography
Server Side Components
Other Helper Classes
The User Interface
The Remotoing and Cryptography Assemblies
Data Access Assemblies
The FinAnalytics Assembly
Namespaces, Files and Installation Guide
Running the Application
Conclusions
References
About the Author

Requirements

Besides understanding the more mundane aspects of C# and the .NET framework, you need to be well familiar with .NET REMOTING, Database (MS SQL), .NET Cryptography, SOAP, XML, ASP.NET and ADO.NET to follow this article and the corresponding code easily. Familiarity with the financial world is advantageous.

Objective

- The advent of C# and .NET has alleviated the design and development of applications to a completely new and MUCH BETTER!! Platform.
- In this article I will discuss some of the design and development issues that one might consider when using .NET framework for developing Network affiliated applications.
- The sample application is developed with the following issues in mind:
- Develop reusable components including the REMOTING and Cryptography modules;
- Provide easily configurable framework for local network access and develop components that could easily be reused to develop web services and applications accessible over the internet; and
- Provide a framework that better addresses performance and post release maintenance and enhancement issues.

Technology Coverage

- The implementation of the sample has touched almost all aspects of C# and .NET. These mainly include:
Serialization, Marshalling By Value and By Reference (MBV and MBR), Call Contexts, Threading, Events, Delegates, Reflection, Custom Attributes, Unsafe code (for including C++ style memory access), Remoting, Cryptography, UI and Configuration.
- For obvious reasons of space and for the sake of avoiding repetition, the detailed account of the underlying technology behind the code is not discussed. The discussion focuses on the design and implementation issues surrounding the overall framework of the application.

Overall Layout

- The application contains three major components; namely; Client side components, Server side components (remote objects) and secured Transport and Messaging components.
- The overall relationship between these components is depicted below:

To continue reading the article and view the source code, download FinNetApplications.zip