The admit maintains the full details about the student and staff. The external mark and assignment arks are also viewed by admit. The staff leave request is submitted by fill the form, the request approval is also made by the admit. Admission module: The admission is made in this module. The student can enroll by giving their personal details such as name, GU or PEG, the marks of the previously studied degree etc. The staff can also register in this module by giving the personal details. Student module: In this module the student can upload the completed assignments.
The e- books can also be studied by the student in this module. Staff module: The Student attendance and the staff attendance are maintained in this doodle. The assignments to the students are maintained in this module. The staff can upload the assignments and the students completed assignments is also viewed in this module. The uploading of the new e books is also done in this module. If the students are absent the message is send to the parent of the particular staff regarding the absence of the students.
Online examination: The online examination is conducted in this module; the student can write the online exam based on their subject degree. The marks are also calculated in this module. The admit can view this mark details. ABOUT THE SOFTWARE: Introduction TO . NET NET is the Microsoft development model in which software becomes available over the Internet. The . Net Framework is the infrastructure of -Net. .Net is built from the group up on open architecture. The goal of the Microsoft . Net platform is to simplify web development.
The . Net Framework provides the foundation upon which application and XML web services are build and executed the unified nature of the . Net Framework means that all applications, whether they are windows applications, web applications are XML web services are developer by using a common set tools and code, and are easily integrated with one another. The . Net Framework consists of the following elements: The Common Language Runtime. The runtime handles runtime services, including language integration, security and memory management.
During development, the runtime provides features that are needed to simplify development. Class Libraries. Class libraries provide reusable code for most common task, including data access, XML web service development, and web and windows forms. Benefits of. Net Framework: The benefits of using the -Net Framework for developing application include: Based on Web standards and practices. Design using unified application models. Easy for developers to use. About PVC#. Net: Visual (pronounced C sharp) is designed to be a fast and easy way to create . Net applications, including Web services and ASP . NET Web applications.
Applications written in Visual C# are built on the services of the common language runtime and take full advantage of the . Net Framework. With its many innovations, C# enables rapid application development while retaining the expressiveness and elegance of C-style languages. Visual Studio supports Visual with a full-featured Code Editor, project templates, designers, code wizards, a powerful and easy-to-use debugger and other lolls. The . Net Framework class library provides access to a wide range of operating system services and other useful, well-designed class that speed up the development cycle significantly.
C# is a simple, elegant, type-safe, object-oriented language recently developed by Microsoft for building a wide range of applications. C# is designed to bring rapid development to the C++ programmer without sacrificing the power and control that are a hallmark of C and C++. Because of the heritage, C# has a high degree of fidelity with C and C++, and developers familiar with these languages can quickly become productive in C# revised intrinsic code trust mechanisms for a high level of security, garbage collection and type safety.
C# supports single inheritance and creates Microsoft intermediate language (MISS) as to native code compilers. As an object-oriented language, supports the concepts of encapsulation, inheritance and polymorphism. All variables and methods, including the Main method, the application’s entry point are encapsulated within class definitions. A class may inherit directly from one parent class, but it may implement any number of interfaces. Methods that override virtual methods n a parent class require the override keyword as a way to avoid accidental redefinition.
Net Framework Architecture: C# programs run on the . Net Framework, an integral component of Windows that includes a virtual execution System called the Common Language Runtime (CLC), an international standard that is the basis for creating and development environments in which languages and libraries work together seamlessly. Source code written in is compiled into an intermediate language (IL) that conforms to the CLIP specification. The IL code, along with resources such as bitmaps and strings, is stored on disk in an executable file called assembly, habitually with an extension of . Exe or . Del. An assembly contains a manifest that provides information on the assembly’s types, version, and culture and security requirements. When the C# program is executed, the assembly is loaded into the CLC, which might take various actions based on the information in the manifest. Then, if the security requirements are met, the CLC performs Just In Time (II T) compilation to convert the IL code into native machine instructions. The CLC also provides other services related to automatic garbage collection, exception handling and resource management.
Code that is executed by the CLC is sometimes referred to as “managed code” in contrast to “unmanaged code” which is compiled into native machine language that targets a specific system. Language interoperability is a key feature of the . Net Framework. Because the IL code produced by the compiler conforms to the Common Type Specification (ACTS), IL code generated from C# can interact with code that was generated from the . Net versions of Visual Basic, Visual C++, Visual or any of more than 20 other ACTS-compliant languages.
A single assembly may contain multiple modules written in different . NET languages and the types can reference each other just as if they were written in the same language. FEATURES OF ASP. NET What is . NET? When . NET was announced in late 1 999, Microsoft positioned the technology as a platform for building and consuming Extensible Markup Language (XML) Web services. XML Web services allow any type of application, be it a Windows- or browser-based application running on any type of computer system, to consume data from any type of server over the Internet.
The reason this idea is so great is the way in which the XML messages are transferred: over established standard protocols that exist today. Using protocols such as SOAP, HTTP, and ESMTP, XML Web services make it possible to expose data over the wire with little or no modifications to your existing code. Since the initial announcement of the . NET Framework, it’s taken on many new and different meanings to different people. To a developer, . NET means a great environment for creating robust distributed applications. To an IT manager, . NET means simpler deployment of applications to end users, tighter security, and simpler management.
To a COT or CIO, . NET means happier developers using state-of-the-art development technologies and a smaller bottom line. Figure presents a high-level overview of the . NET Framework and how XML Web services are positioned. Figure 1. 1 . Stateless XML Web services model. To understand why all these statements are true, you need to get a grip on what the . NET Framework consists of, and how it’s truly a revolutionary step forward for application architecture, development, and deployment. NET Framework Now that you are familiar with the major goals of the .
NET Framework, let’s briefly examine its architecture. As you can see in Figure 1-2, the . NET Framework sits on top of the operating system, which can be a few different labors of Windows and consists of a number of components . NET is essentially a system application that runs on Windows. Conceptually, the CLC and the JOB are similar in that they are both runtime infrastructures that abstract the underlying platform differences. However, while the JOB officially supports only the Java language, the CLC supports any language that can be represented in its Common Intermediate Language (CEIL).
The JOB executes botched, so it can, in principle, support many languages, too. Unlike Java’s botched, though, CEIL is never interpreted. Another conceptual difference between the two infrastructures is that Java ode runs on any platform with a JOB, whereas . NET code runs only on platforms that support the CLC. In April, 2003, the International Organization for Standardization and the International Electro technical Committee (ISO/ ICE) recognized a functional subset of the CLC, known as the Common Language Interface (CLIP), as an international standard.
This development, initiated by Microsoft and developed by ECMA International, a European standards organization, opens the way for third parties to implement their own versions of the CLC on other platforms, such as Linux or Mac SO X. For information on third-party and open source projects working to implement the ISO/ICE CLIP and C# specifications The layer on top of the CLC is a set of framework base classes. This set of classes is similar to the set of classes found in SST, MFC, TTL, or Java.
These classes support rudimentary input and output functionality, string manipulation, security management, network communications, thread management, text management, reflection functionality, collections functionality, as well as other functions. On top of the framework base classes is a set of classes that extend the base classes to purport data management and XML manipulation. These classes, called ADO. NET, support persistent data management-?data that is stored on backbend databases. Alongside the data classes, the .
NET Framework supports a number of classes to let you manipulate XML data and perform XML searching and XML translations. Classes in three different technologies (including web services, Web Forms, and Windows Forms) extend the framework base classes and the data and XML classes. Web services include a number of classes that support the development of lightweight distributed components, which work even in the face Of firewalls and NAT software. These components support plug-and-play across the Internet, because web services employ standard HTTP and SOAP. Web Forms, the key technology behind ASP.
NET, include a number of classes that allow you to rapidly develop web Graphical User Interface (GUI) applications. If you’re currently developing web applications with Visual Interned, you can think of Web Forms as a facility that allows you to develop web Guise using the same drag-and- drop approach as if you were developing the Guise in Visual Basic. Simply drag-and-drop controls onto your Web Form, double-click on a control, and write the code to respond to the associated event. Windows Forms support a set of classes that allow you to develop native Windows GUI applications.
You can think of these classes collectively as a much better version of the MFC in C++ because they support easier and more powerful GUI development and provide a common, consistent interface that can be used in all languages. The Common Language Runtime At the heart of the . NET Framework is the common language runtime. The common language runtime is responsible for providing the execution environment that code written in a . NET language runs under. The common language runtime can be compared to the Visual Basic 6 runtime, except that he common language runtime is designed to handle all .
NET languages, not just one, as the Visual Basic 6 runtime did for Visual Basic 6. The following list describes some of the benefits the common language runtime gives you: Automatic memory management Cross-language debugging Cross-language exception handling Full support for component versioning Access to legacy COM components COPY deployment Robust sec rite model You might expect all those features, but this has never been possible using Microsoft development tools. Figure 1. 3 shows where the common language runtime fits into the . NET Framework. Figure 1. 3. The common language runtime and the .
NET Framework. Note Code written using a . NET language is known as managed code. Code that uses anything but the common language runtime is known as unmanaged code. The common language runtime provides a managed execution environment for . NET code, whereas the individual runtimes of non-. NET languages provide an unmanaged execution environment. Inside the Common Language Runtime The common language runtime enables code running in its execution environment to have features such as security, versioning, memory management and exception handling because of the way . NET code actually executes.
When you compiled Visual Basic 6 forms applications, you had the ability to compile down to native node or p-code. Figure 1. 4 should refresh your memory Of what the Visual Basic 6 options dialog looked like. Figure 1. 4. Visual Basic 6 compiler options dialog. When you compile your applications in . NET, you aren’t creating anything in native code. When you compile in . NET, you’re converting your code-?no matter what . NET language you’re using-?into an assembly made up of an intermediate language called Microsoft Intermediate Language (MISS or just IL, for short).
The IL contains all the information about your application, including methods, properties, events, types, exceptions, security objects, and so on, and it also includes metadata about what types in your code can or cannot be exposed to other applications. This was called a type library in Visual Basic 6 or an IDOL (interface definition language) file in C++. In . NET, it’s simply the metadata that the IL contains about your assembly. The file format for the IL is known as PEE (portable executable) format, which is a standard format for processor-specific execution.
When a user or another component executes your code, a process occurs called just- n-time (KIT) compilation, and it’s at this point that the IL is converted into the specific machine language of the processor it’s executing on. This makes it very easy to port a . NET application to any type of operating system on any type of processor because the IL is simply waiting to be consumed by a KIT compiler. The first time an assembly is called in . NET, the KIT process occurs. Subsequent calls don’t re-KIT the IL; the previously Jetted IL remains in cache and is used over and over again. Hen you learn about Application Center Test, you also see how the warm-up time of the KIT process can affect application performance. Understanding the process of compilation in . NET is very important because it makes clear how features such as cross- language debugging and exception handling are possible. You’re not actually compiling to any machine-specific code-?you’re simply compiling down to an intermediate language that’s the same for all . NET languages. The IL produced by J# . NET and C# looks just like the IL created by the Visual Basic .
NET compiler. These instructions are the same, only how you type them in Visual Studio . NET is different, and the power of the common language runtime is apparent. When the IL code is Jetted into machine-specific language, it does so on an as-needed basis. If your assembly is IAMB and the user is only using a fraction of that IAMB, only the required IL and its dependencies are compiled to machine language. This makes for a very efficient execution process. But during this execution, how does the common language runtime make sure that the IL is correct?
Because the compiler for each language creates its own IL, there must be a process that makes sure what’s compiling won’t corrupt the system. The process that validates the IL is known as verification. Figure 1. Demonstrates the process the IL goes through before the code actually executes. Figure 1. 5. The KIT process and verification. When code is KIT compiled, the common language runtime checks to make sure that the IL is correct. The rules that the common language runtime uses for verification are set forth in the Common Language Specification (CLC) and the Common Type System (ACTS).
The . NET Framework Class Library The second most important piece of the . NET Framework is the . NET Framework class library (FCC). As you’ve seen, the common language runtime handles the dirty work of actually running the code you write. But to write the code, you need a foundation of available classes to access the resources of the operating system, database server, or file server. The FCC is made up of a hierarchy of namespace that expose classes, structures, interfaces, enumerations, and delegates that give you access to these resources.
The namespace are logically defined by functionality. For example, the System-Data namespace contains all the functionality available to accessing databases. This namespace is further broken down into System. Data. Clients, which exposes functionality specific to SQL Server, and System. Data. Lolled, which exposes specific functionality for accessing LOLLED data sources. The bounds of a namespace aren’t necessarily defined by specific assemblies within the FCC; rather, they’re focused on functionality and logical grouping.
In total, there are more than 20,000 classes in the FCC, all logically grouped in a hierarchical manner. Figure 1. 8 shows where the FCC fits into the . NET Framework and the logical grouping of namespace. Figure The . NET Framework class library. To use an FCC class in your application, you use the Imports statement in Visual Basic . NET or the using statement in When you reference a namespace in Visual Basic . NET or you also get the convenience of auto- complete and auto-list members when you access the objects’ types using Visual Studio .