Hi,
here's a list of topics the sample applications could treat:
- Sample for developing Web Services
- Advanced sample for using ADO.NET and the .NET data objects and controls
- .NET Remoting
- XSL and Schema capabilites of the .NET class library
- .NET Security model
- using Delphi components/COM Objects in ASP.NET
We should discuss now, which topics would be nice and reasonable to
demonstrate
by an application and who wants to do what. We should also debate a useful
example of use.
Since you requested more information on the .NET framework I'll shortly
describe the mentioned aspects of it.
The .NET framework consists in general of two core components:
- The "Common Language Runtime (CLR)":
.NET programs (.EXE) don't contain machine-code like traditional programs
but
are stored in the proprietary "Microsoft Intermediate Language" (MSIL). All
compilers
that create .NET programs create MSIL-.EXEs. The Common Language Runtime
that is of
course shipped with the .NET framework is executes the MSIL code
(also called "managed code").
Though developers are supposed to write only applications that use "managed
code",
i.e. write sourcecode that is completely managed by the CLR, there are
several
ways to communicate with native elements such as COM Objects etc.
- The ".NET Class Library" is a really BIG collection of libraries. Those
libraries
(about 10 files, located in the directory
"\WINDOWS\Microsoft.NET\<Version>\" )
are actually used for _everything_ in .NET. They provide basic
functionality,
for example for drawing Windows, Exceptions and even all data types are
stored
in those libraries. But they also contain advanced features like processing
XML, accessing Databases and the web etc. Every .NET application depends
largely
upon the class library. Since the class library is available on every
".NET-enabled"
system, it isn't directly compiled into the executable file whereby the
filesize
stays quite humble. To get a better feeling and understandig for the .NET
Class Library,
you should have a look at the ".NET Reflector tool"
(http://www.aisto.com/roeder/dotnet/).
To get the actual .NET framework you can download it from the Microsoft
Website:
http://msdn.microsoft.com/downloads/default.asp?URL=/downloads/sample.asp?ur
l=/msdn-files/027/001/829/msdncompositedoc.xml (small version - contains the
CLR, the Class Library,
some compilers and a few tools)
http://msdn.microsoft.com/downloads/default.asp?url=/downloads/sample.asp?ur
l=/msdn-files/027/000/976/msdncompositedoc.xml&frame=true ("full version"
[SDK] - contains the same as
above plus some more tools and the complete documentation of the framework)
Web Services capabilites of .NET: (Namespace: "System.Web.Services")
The .NET framework provides a huge amount of classes and functions for
developing
Web Services. The functionality is mainly capsulated in the
"System.Web.Services"
namespace of the .NET framework. Since Web Services are one of .NET's key
features,
we should absoluteley build an sample treating this topic.
ADO.NET: (Namespace: "System.Data")
ADO.NET is the largely renewed version of the ActiveX Data Objects - a set
of
objects/classes that provide a very powerful means for accessing data
sources
of any kind.
.NET Remoting: (Namespace: "System.Runtime.Remoting")
Mmh I have no clue yet ;-) seems like something for remote
communication/invokation :>
XSL/Schema/XPath: (Namespace: "System.Xml")
Besides the support for parsing standard XML documents, the .NET framework
offers
special functionality to handle XPath or XML applications like XSL(T) and
XML Schema.
.NET Security model: (Namespace: "System.Security")
A collection of classes and utilities for establishing a security
model/environment
within the .NET framework.
P.S.: Sorry for grammer and expression mistakes :-/
|
