1 / 18

.NET Web Article Management System: Introduction, Modules, and Prerequisites

Learn about the .NET Web Article Management System, its modules, installation, and prerequisites. Discover the benefits of using .NET for developing web applications.

dpedro
Download Presentation

.NET Web Article Management System: Introduction, Modules, and Prerequisites

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. .NET WEB ARTICLE MANAGEMENT SYSTEM

  2. INTRODUCTION • What is article mgt. ? • Why is the project named so ?

  3. Modules • Web Articles • Message Board & Technical Chat • Search • Mail • Online Training On .Net • Web Advertising • Downloads

  4. ASP.NET QuickStart • What Is It? • Tutorial, ASP.NET samples • Syntax, architecture, features • Installation • Install Microsoft .NET Framework SDK • Visual Studio.NET installation and Components Update • Installation of Visual Studio.NET is not mandatory • .NET Framework Samples • ASP.NET QuickStart ASP.NET Web Services Writing a Simple Web Service

  5. Front page

  6. PREREQUISITES • Server Configuration • ·PIII or Above processor • ·256MB RAM • Database Configuration ·SqlServer2000 • Software Requirements ·Windows 2000 server • ·Internet Information • Server 5.0 • ·Visual Studio.NET ·Crystal Reports

  7. 3 TierArchitecture SQL server VB.net ASP.net

  8. Why we used .Net ? Processor Independence Multi-Lingual Avoids DLL hell Intellisense

  9. What Is . NET? • The combination of: • Framework • Common language runtime • Class libraries • ASP.NET • Web Services • .NET Enterprise Servers • The means to build the Web the way you want it!

  10. The .NET Framework Architecture VB C# C++ JScript 3rdParty CLS : Common Language Specification ASP.NET Windows Forms Web Forms Web Services ADO.NET Data & XML BCL : Base Class Library CLR : Common Language Runtime Operating System Services

  11. Thread Support COM Marshaler Type Checker Exception Manager Security Engine Debug Engine MSIL to Native Compilers (JIT) Code Manager Garbage Collector (GC) COMMON LANGUAGE RUNTIME Base Class Library Support Class Loader

  12. Cross Language Interoperability Development Tool such as Visual Studio.net Just-In-Time Compiler Source code: VB,VC++, COBOL…. Microsoft Intermediate Language (MSIL) Platform- Specific Code

  13. .Net Technologies(we use) • VB.NET • ASP.NET • ADO.NET

  14. Object Based Early Binding We can’t develop socket applications Doesn’t support thread programming Console applications are not allowed Object Oriented Late Binding Socket programming is supported Supports multithreading Console applications are allowed VB 6.0 Vs VB.NET

  15. Mixes layout (HTML) and logic (scripting code) Interpreting ASP code leads to performance loss No real state management Browser compatibility Update files only when server is down Uses scripting languages that are not strongly typed Separate layout and business logic Use services provided by the .NET Framework State management Cross-language integration Update files while the server is running! Code is compiled the first time a page is requested. ASP Vs ASP.NET

  16. Designed for connected access The RecordSet is the central data container RecordSet is one (1) table that contains all the data Tied to the physical data model Designed for disconnected access Can model data logically! The DataSet replaces the RecordSet DataSet can contain multiple tables ADO Vs ADO.NET

  17. Benefits of ADO.NET • Interoperability through use of XML - Human readable and decipherable text • Scalability through the disconnected - Connections are not maintained for long periods • Maintainability • - Separation of data logic and user interface

  18. Conclusion

More Related