| |
 |
.Net |
|
|
|
| |
The Solution – Microsoft .NET |
|
|
|
|
| |
Microsoft's .NET initiative is broad-based and very ambitious. It includes the .NET Framework, which
encompasses the languages and execution platform, plus extensive class libraries providing rich built-in
functionality. Besides the core .NET Framework, the .NET initiative includes protocols (such as the Simple Object Access Protocol, commonly known as SOAP) to provide a new level of integration of
software over the Internet, and a set of pre-built web-based services called .NET My Services (formerly
codenamed Hailstorm).
Microsoft also released several products early in 2001, which were described as being part of the .NET Enterprise Server family: SQL Server 2000, Commerce Server 2000, BizTalk Server, Exchange 2000,
Host Integration Server (the successor to SNA Server), and Internet Security and Administration (ISA)
Server (the successor to Proxy Server).
Some of the marketing literature for these products emphasizes that they are part of Microsoft's .NET
strategy. However, it is important to understand the difference between these products and the .NET
Framework. The .NET Enterprise Servers are not based on the .NET Framework. Most of them are
successors to previous server-based products, and they use the same COM/COM+ technologies as
their predecessors.
These .NET Enterprise Servers still have a major role to play in future software development projects.
When actual .NET Framework projects are developed, most will depend on the technologies in the
.NET Enterprise Servers for functions like data storage and messaging.
|
| |
|
| |
Why .Net |
|
|
|
|
| |
Many of the goals Microsoft had in mind when designing .NET reflect the limitations we identified for
their earlier tools and technologies. |
| |
|
| |
Creating Highly Distributed Applications |
|
|
|
|
| |
The trend in business applications is towards a more highly distributed model. The next generation of
applications may have their elements distributed among various organizations. This contrasts with
today's dominant model in which all the elements of an application (except possibly a browser-based
client) are located solely within a single organization. |
| |
|
| |
Simplifying Software Development |
|
|
|
|
| |
Developers need to be able to concentrate on the business logic in their applications, and to stop writing
logic for things like state management and scalability. Writing software for the Internet should not
require expertise in a long list of Internet-specific technologies.
A related goal is to have development for the Internet look very much like development for other
platforms. A component accessed over a local network or over the Internet should be manipulated with
code very much like that for a component accessed on the local machine. The software platform should
be able to take care of the details in transmitting information to and from the component.
What is Microsoft .NET? |
| |
|
| |
Better User Interfaces over the Web |
|
|
|
|
| |
User interface development also needs to be as similar as possible for the Internet compared to local access.
While using local, platform-specific interfaces will always offer more flexibility than a browser-based
interface, Microsoft .NET aims to make those two types of interfaces as similar to develop as possible.
By making web-based user interfaces richer and more flexible than they are now, bringing them as close
as possible to the richness of local, forms-based interfaces.
|
| |
|
| |
Simplifying Deployment |
|
|
|
|
| |
The problems of DLL Hell, and the need for large installs of forms-based applications, are just two
examples of current deployment issues. Microsoft .NET aims to make deployment as simple as it was
for DOS – just copy a compiled module over to a system and run it. No registration, no GUIDs, no
special installation procedure. |
| |
| |
Support for a Variety of Languages |
|
|
|
|
| |
While the idea of one grand, unifying language sounds good in theory, in the real world, different types
of developers need different tools. Microsoft .NET is designed to support a multitude of languages, from
Microsoft and third-parties. This will allow the development community to evolve languages that best fit
various development needs. |
| |
| |
An Extendable Platform for the Future |
|
|
|
|
| |
A new platform needs the capability to adapt to changing conditions through extensions and variations. .NET is designed with greater extendibility and flexibility than any previous software development platform. |
| |
|
| |
Future Portability of Compiled Applications |
|
|
|
|
| |
Operating systems will make major changes and perhaps entirely new ones will be introduced in the
future. Investments in software development need to be carried forward to those platforms. The goal of
.NET is to allow applications to move from current platforms to future platforms, such as 64-bit
operating systems with a simple copy, and no recompilation. |
| |
|
| |
The Structure of Microsoft .NET |
|
|
|
|
| |
 |
| |
|
| |
ASP .NET |
|
|
|
|
| |
ASP.NET is to Enable to build dynamic ,powerful and more secure applications using the least possible amount of code. It is a part of .NET Framework. Firstly we introduced What is .NET Framework . |
| |
|
| |
.NET Framework :- The .NET Framework is new and revolution platform created by Microsoft for developing applications. The .NET Framework allows the creation of Windows applications, web applications , web services, and pretty much anything else you can think of. |
| |
|
| |
The .NET Framework has been designed such that it can be used from any language. This includes Visual Basic, C#, C++, Jscript , and even older languages such as COBOL. |
| |
|
| |
ASP.NET uses for creating dynamic Web applications with IIS. ASP.NET files contain server-side logic and they use a compiled, even-driven programming model that improves performance and enables the separation of logic and user interface. |
| |
|
| |
ASP(Active Server Pages) is also used for Web Application. But Present scenario ASP.NET widely used compare to ASP. Now question arises that Why ASP.NET is more Popular compare to ASP because Some feature include in ASP.NET |
| |
|
| |
ASP .NET new feature Compare to ASP |
|
|
|
|
| |
Better Language Support |
| |
New ADO.NET Concepts have been implemented.ASP.NET supports full language (C#, VB.NET, C++) and not simple scripting like VBSCRIPT. |
| |
|
| |
Better controls than ASP |
| |
ASP.NET covers large set’s of HTML controls.Better Display grid like Datagrid, Repeater and datalist. Many of the display grids have paging support. |
| |
|
| |
Compiled Code |
| |
The first request for an ASP.NET page on the server will compile the ASP.NET code andkeep a cached copy in memory. The result of this is greatly increased performance. |
| |
|
| |
Better Authentication Support |
| |
ASP.NET supports forms-based user authentication, including cookie management and Automatic redirecting of unauthorized logins. |
| |
|
| |
User Accounts and Roles |
| |
ASP.NET allows for user accounts and roles, to give each user (with a given role) access
to different server code and executables. |
| |
|
| |
High Scalability |
| |
Much has been done with ASP.NET to provide greater scalability. Server to server communication has been greatly enhanced, making it possible to scale an application over several servers. |
| |
|
| |
Easy Configuration |
| |
Configuration of ASP.NET is done with plain text files. Configuration files can be uploaded or changed while the application is running. No need to restart the server. |
| |
|
| |
ASP.NET evolved and released new version. Presently Our company prefer ASP.NET 2.0(ASP.NET 2005) .ASP.NET 2.0 given new additional feature and goal . |
| |
|
| |
Goals of ASP.NET 2.0 |
|
|
|
|
| |
 |
Increase productivity by removing two by third of the code |
|
Simplify the administration of web applications |
|
Use the same controls for all types of devices |
|
Provide a faster and better web server platform |
|
Simplify compilation and installation |
|
| |
|
| |
New features in ASP.NET 2.0 are |
|
|
|
|
| |
|
Master Pages, Themes, and Web Parts |
|
Full support for XML standards like, XHTML, XML, and WSDL |
|
Roles, personalization, and internationalization services |
|
Improved site management |
|
Standard controls for navigation |
|
Standard controls for security |
|
Improved and simplified data access controls |
|
Improved compilation and deployment (installation) |
|
New and improved development tools |
|
| |
|
| |
ASP.NET 2.0 adds quite a few new events to allow you to follow the request-processing more closely and precisely. These new events in the following table. |
| |
|
| |
New Events in ASP.NET 2.0 |
|
|
|
|
| |
|
| |
| Events |
Description |
| PreInit |
| |
This occurs before the page begins initialization. This is the first event in the life of an ASP.NET 2.0 page. |
|
|
| InitComplete |
| |
This occurs when the page initialization is completed. |
|
|
| PreLoad |
| |
This occurs immediately after initialization and before the page begins loading the state information. |
|
|
| LoadComplete |
| |
This occurs at the end of the load stage of the page's life cycle. |
|
|
| PreRenderComplete |
| |
This occurs when the pre-rendering phase is complete and all child controls have been created. After this event, the personalization data and the view state are saved and the page HTML is rendered. |
|
|
|
| |
|
| |
|
| |
 |
