Programming in .NET Assignment, Assignments of Javascript programming

Programming in .NET Assignment

Typology: Assignments

2017/2018

Uploaded on 04/27/2023

manish_mahaseth
manish_mahaseth 🇳🇵

9 documents

1 / 138

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Niraj Yadav
ISMT COLLEGE GAIRIGAUN,TINKUNE |
Programming in .net
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12
pf13
pf14
pf15
pf16
pf17
pf18
pf19
pf1a
pf1b
pf1c
pf1d
pf1e
pf1f
pf20
pf21
pf22
pf23
pf24
pf25
pf26
pf27
pf28
pf29
pf2a
pf2b
pf2c
pf2d
pf2e
pf2f
pf30
pf31
pf32
pf33
pf34
pf35
pf36
pf37
pf38
pf39
pf3a
pf3b
pf3c
pf3d
pf3e
pf3f
pf40
pf41
pf42
pf43
pf44
pf45
pf46
pf47
pf48
pf49
pf4a
pf4b
pf4c
pf4d
pf4e
pf4f
pf50
pf51
pf52
pf53
pf54
pf55
pf56
pf57
pf58
pf59
pf5a
pf5b
pf5c
pf5d
pf5e
pf5f
pf60
pf61
pf62
pf63
pf64

Partial preview of the text

Download Programming in .NET Assignment and more Assignments Javascript programming in PDF only on Docsity!

Niraj Yadav

ISMT COLLEGE GAIRIGAUN,TINKUNE |

Contents

Justification of use of Core Layer, Data Access Layer, Business Layer and Presentation layer:

  • Task
    • Introduction to ASP. NET........................................................................................................
    • Introduction of SOLID principle
    • Single Responsibility Principle (SRP):
    • Open/Closed Principle (OCP):
    • Liskov Substitution Principle (LSP):
    • Interface Segregation Principle:
    • Dependency Inversion Principle:
    • Characteristic of .NET framework
    • Interoperability:
    • Common Language Runtime engine (CLR):
    • Language Independence:
    • Base Class Library:
    • Security:
    • Simple Deployment:
    • Portability:
    • Features of .Net Framework...................................................................................................
    • Custom Object Libraries:
    • Class Libraries
    • The Base Class Library (BCL):
    • Managed Application
    • Unmanaged Application
    • Runtime
  • Conclusion:
  • Task 2:
    • Introduction
    • Introduction to .NET Framework Architecture
    • Languages supporting .NET:
    • Web Form, Web Services and Windows Form:
    • Web Forms
    • Windows Form
    • Windows mobile application:
    • NET Framework versions under different version of Windows.
  • Conclusion
  • Task 3:
    • Introduction:
    • Component of .Net Framework :............................................................................................
    • Common Language Runtime:
    • Common Language Specification (CLS) :
    • Common Type System:
    • Base Class Library/Framework Class Library
  • Task 4:
    • Introduction:
    • Pseudo-Code
    • Algorithm
    • Flowchart
    • Context Diagram
    • 0 - Level Data Flow Diagram
    • Use Case Diagram
  • Conclusion
  • Task
    • Introduction:
    • File Structure:
    • Data Dictionary:
    • Class and object used:............................................................................................................
    • Evaluation of potential delivery environment and interaction:
    • Introduction
    • Project Requirement
    • Scope Management
    • Cost Management
    • Schedule Management
    • Delivery Methods
    • Design State Management
    • Building Information Modeling
    • Quality Control
  • Task 6:
    • Introduction
    • Implementation of the .Net Programming solution based on prepared design specification.
    • Home Page:
    • Department Page Form
    • Employee Page Form.............................................................................................................
    • Course form Page
    • Level Page
    • Contact Page..........................................................................................................................
    • Login Page
    • Registration Page
    • Justification of design:
    • Implement event handling using control structures to meet the design algorithms.
    • Introduction
    • Event Handling Mechanism
    • Justification of Event Handling in “Mtech College”:-
    • Identify and implement opportunities for error handling and reporting.
    • Introduction
    • Error Handling/Exception Handling and Reporting
    • Reporting:-
    • screen templates Make effective use of an Integrated Development Environment (IDE) including code and
    • Integrated Development Environment (IDE)
    • Visual Studio 2012:
    • SQL Management studio 2014:..............................................................................................
  • Conclusion
  • Task
    • Test Log
    • Unit Testing
    • Integrated Testing
    • Stress Testing
    • Critical Review
    • Reviev
    • Body......................................................................................................................................
  • Conclusion
  • Task
    • Introduction
    • Independent Feedback
    • System Evaluation
    • Interface
    • Coding Architecture
    • Database Design
    • Security
    • Recommendation
  • Conclusion:
  • TASK 9...................................................................................................................................
    • Introduction
    • Scope...................................................................................................................................
    • User Manual
    • Introduction
    • Overview
    • Hardware and Software Specification
    • System Configuration
    • Diagrammatic Guidance
    • Home Page
    • Registration
    • Log In..................................................................................................................................
    • Dashboard:
    • Department, Employee, Student, Course and Level Page
  • Conclusion:
  • TASK 10.................................................................................................................................
    • Introduction
    • Systems Used
    • Areas Addressed
    • System Design:
    • DFD for Login:....................................................................................................................
    • User Registration:
    • Entire Process:
    • Data Dictionary
    • Architecture of the Application:
    • Software Functionality Testing:
    • Task Break Down
    • Choice of tools:
  • Conclusion:
  • References:-

Task 1 Discus the principals, characteristics and features of programming using a .NET framework. [1.1, M1] Consider: (SOLID principles), Characteristics (Interoperability, common runtime Engine, Language Independence, Base class Library, Simplified Deployment, Security and Probability), and Features (Custom Objects Libraries, Class libraries, Managed and Unmanaged Applications, Runtime) Introduction to ASP. NET ASP.NET is a web development platform, which provides a programming model, a comprehensive software infrastructure and various services required to build up robust web applications for PC, as well as mobile devices. ASP.NET works on top of the HTTP (Hyper Text Transfer Protocol) protocol, and uses the HTTP commands and policies to set a browser-to-server bilateral communication and cooperation. ASP.NET is a part of Microsoft .Net platform. ASP.NET applications are compiled codes, written using the extensible and reusable components or objects present in .Net framework. These codes can use the entire hierarchy of classes in .Net framework. The fundamental component of .NET platform is .NET framework. This framework is consisted of runtime environment called the common language runtime and a set of supporting libraries. The runtime environment provides all the major operation during development such as installation, loading and the execution of .NET application. In .NET, the libraries act as the code provider for programming purposes which inclusively increase developer productivity. Similarly, the libraries also provide a layer for many OS APIs that provide isolation from OS dependencies. (Tutors Point, 2017). Introduction of SOLID principle Presently the majority of the modern programming languages including C# supports objected oriented programming because encapsulation, inheritance, overloading and polymorphism are code level features of objected oriented programming. SOLID principles include Single Responsibility Principle, Open/Closed Principle, Liskov Substitution Principle, Interface

Fig- 1. Open/Closed Principle The above code is an example which supports the Open Close Principle. In the design we use abstract draw() method in GraphicEditor for drawing objects, while moving the implementation in the concrete shape objects. Using the Open Close Principle the problems from the previous design are avoided, because GraphicEditor is not changed when a new shape class is added:  no unit testing required.  no need to understand the sourcecode from GraphicEditor.  since the drawing code is moved to the concrete shape classes, it's a reduced risk to affect old functionallity when new functionallity is added. Liskov Substitution Principle (LSP): The principle is named after Barbara Liskov. LSP states that "functions that use pointers or references to base classes must be able to use objects of derived classes without knowing it". LISKOV principle declares the parent should easily replace the child object. The object in a program should be replaceable with instances of their subtypes without changing the correctness of that program in LSP. For example: Suppose we have created a class named Special Customers that maintains a list of special Customers (may be they are special because they are frequent buyers, or they purchase high value items). This class is shown below:

Interface Segregation Principle: The Interface Segregation Principle states that clients should not be forced to implement interfaces they don't use. Instead of one fat interface many small interfaces are preferred based on groups of methods, each one serving one submodule. It is not a hard rule that has to be one-to-one mapping between classes and interfaces. It is rather in fact much better if one can create several smaller interfaces instead that can have multiple behaviors which can be easy to manipulate.

Characteristic of .NET framework Interoperability: The word ‘Interoperability’ refers that it have ability of diverse systems and organizations to work together (inter-operate). Interoperability enables you to preserve and take advantage of existing investments in unmanaged code. Code that runs under the control of the common language runtime (CLR) is called managed code, and code that runs outside the CLR is called unmanaged code. COM, COM+, C++ components, ActiveX components, and Microsoft Win API are examples of unmanaged code. + The .NET Framework enables interoperability with unmanaged code through platform invoke services, the System.Runtime.InteropServices namespace, C++ interoperability, and COM interoperability (COM interop). (MicroDoc, 2017) Common Language Runtime engine (CLR): The Common Language Runtime (CLR) is an Execution Environment. It works as a layer between Operating Systems and the applications written in .Net languages that conforms to the Common Language Specification (CLS). The main function of Common Language Runtime (CLR) is to convert the Managed Code into native code and then execute the Program. The Managed Code compiled only when it needed, that is it converts the appropriate instructions when each function is called. The Common Language Runtime (CLR)’s Just In Time (JIT) compilation converts Intermediate Language (MSIL) to native code on demand at application run time.

Fig6. Common Language Runtime engine Language Independence: A common runtime engine shared by all .NET aware languages. In .NET CLR accommodates more than one languages such as C#, VB.NET, Jscript, ASP.NET, C++ and also 22 other languages like Perl, Python, COBOL etc. A source code is converted to intermediate language code (IL) by the respective compiler, and then the IL code is converted to native code using the JIT compiler during the run-time. .NET regardless of the language you use the associated compiler emits IL instructions. For example if a c++ source code is compiled by c++ compiler it emits IL instructions and Metadata. Base Class Library: The programmer working with .NET structure are provided with the base class libraries that can be coordinated with any programming language based on .NET framework for example, C# and

Simple Deployment: The .NET system is simple and adaptable to convey after the web application has been produced. The visual studio software gives an approach to send a nearby or remote server in a PC for testing and execution reason. This mean one can easily test how a program is by basically utilizing the local server in the program interface. Some of the deployment features of .NET framework are mentioned below:  Components are deployed to application by default and are visible to that application only  Developer may choose any version of component and application provided by CRE of .NET framework  Reduces DDL conflict which affect the other application Portability: Portability is a .NET/Mono library. That is designed to permit nicer integration between software written in .NET and various OSes (primarily Linux and Windows, but OS X as well). It implements a more generic handling of paths, on top of both the .NET interface for paths and the XDG specification (on UNIX systems), and an alternative settings manager (using either the Windows registry or GConf). Features of .Net Framework Custom Object Libraries: Custom, user-defined classes are classes with properties, events, and methods, but with no visual representation. The same general rules that apply to defining other types of classes apply to defining custom classes. The objective of this tutorial is to quickly talk about a portion of the strategies accessible when utilizing more intricate custom objects. Class Libraries As specified before, .NET framework itself provide various classes, interface and data type sort that a developer can actualize in their application for services. These classes of .NET framework are for the most part sorted out into hierarchical tree structure and are dividend utilizing particular

namespace which help in the identification of that particular class. These classes are overseen and can be access to any system service as required during framework execution. These classes are a piece of the Object Oriented Program which helps in growing considerably more powerful application. These classes can likewise be incorporated with any third-party application that keeps running on the system itself. Some of the main functions supported by .NET framework classes are mentioned below:  Data types: User defined and Base class  Windows based GUI application  Web services  Web client  Server Application  Exception Handling  System Communication The Base Class Library (BCL): It includes a small subset of the entire class library and is the core set of classes that serve as the basic API of the Common Language Runtime. The classes in mscorlib.dll and some of the classes in System.dll and System.core.dll are considered to be a part of the BCL. The BCL classes are available in both .NET Framework as well as its alternative implementations including .NET Compact Framework, Microsoft Silverlight and Mono. Managed Application In .NET framework the application where the codes written for the program can directly be executed inside the CLR rather than OS is known as managed application. These codes of managed application utilize common language runtime to give different features to the application, for example, managing memory, and security protocols and even permit cross- language debugging. By utilizing managed code and compiling in this managed execution environment, you can avoid many typical programming errors that prompt security holes and unsteady applications. Likewise, numerous ineffective programming tasks are automatically

Runtime In .NET framework runtime feature is provided by the common language runtime which helps to run the code and provide all necessary services for the easy and smooth development of application. The codes that run with the help of CLR are known as managed code. The runtime automatically handles object layouts and also manage the object by releasing them from the program when they are no longer required. Likewise, the runtime also helps to design the components and applications where the objects are interacting in cross-language platform. The runtime also helps the objects written in other languages to communicate with the languages that are used to design the program by integrating their behavior Conclusion: The web application created using ASP.NET framework is considered as the safe one than alternate frameworks. ASP.NET is a programming framework used to make a web application more effortlessly and safely. .NET Framework is a programming infrastructure which helps in building, conveying and running application and services which makes the utilization of .net innovations like desktop application and web services. .NET Framework gives a controlled programming condition to building, installing and executing programming on Windows based operating systems. It consists of three major components i.e. Common Language Runtime (CLR), .NET Framework Class Library and ADO.NET. Thus, ASP.NET framework has been the programmer’s first decision to grow any web application created utilizing ASP.NET is secure and ensured.

Task 2: Critically compare different types of .NET framework architectures. [1.2, M3] Consider : Various types of languages, Web forms / Windows forms / Windows mobile applications, .NET Framework versions under different version of Windows. Introduction In present, .NET framework is one of the most utilized stages for developing web based application for desktop. It has brought lots of new and transformative component for efficient software development. .Net is made by Microsoft for the broadly useful of making web based application that conquer past era programming language in term of productivity and adequacy. Thus, Microsoft likewise brings the report on the arrival of new update that accompanies new more features and additional component that was not available from the old ones. Introduction to .NET Framework Architecture .NET is hierarchal, tiered, and modular. Every level of the .NET Framework is a layer of abstraction. .NET languages are the top level and the most abstracted level. The basic dialect runtime is the base level, the minimum abstracted, and nearest to the local environments. This is essential since the common language runtime works intimately with the working condition to oversee .NET applications. The .NET Framework is apportioned into modules, each with its own particular responsibility. Finally, since higher levels request for services just from the lower tiers, request services only from the lower tiers, .NET is hierarchal.