Company Profile

Star Wire (India) Limited, one of the leading Mini Steel Plant is engaged in the manufacturing of Alloy Steels, Stainless Steel and Special Steels for diversified engineering application in shape of castings, forging and rolled products. Plant is fully equipped with modern equipment and testing facilities which have created confidence and ability for manufacturing various sophisticated grades of steel conforming to international and National standards.

It has its own research and development center to facilitate the manufacturing activities and also catering to engineering and manufacturing industries for failure analysis and other analytical activities.

The plant is situated in Ballabgarh, about 37 KMs from Delhi - Capital of India on Main Mathura Road (NH No. 2). The location is at easy approach by Air, Rail and Road.

ABSTRACT

The project “Counseling Management system” is to exploit the computer technology with Internet Facility and all its aspects as necessity arises. The proposed project will be a web-based portal to provide support and services to the Students of participating in university counseling. The project will make available the Students care services of member colleges to its Students through the Internet. Through this proposed website the Students can register herself and take Admissions and support accordingly. The project “Counseling management system” is specially associated with online Admission procedure of any university, provide Admissions and support to Students and take their feedback. The overall objective is to develop The Counseling management system to provide fast and easy support to the Students who are applicable to take the admissions in a particular college of university according to their prospective

Counseling Management System

_______________________________________________________________________ Contents
_______________________________________________________________________
Abstract

CHAPTER 1 INTRODUCTION
1.1 Computerization and Internet Technologies
1.2 About Project
1.3 Project Objectives CHAPTER 2 PROJECT CATEGORY & REQUIREMENT SATISFACTION
2.1 Internet Technologies and .NET
2.2 Tools and Platform
2.3 Hardware
2.4 Software Requirement Specification

CHAPTER 3 PROJECT MODULES & TESTING AND VALIDATION CHECKS 3.1 Modules Description

CHAPTER 4
SCOPE OF FUTURE APPLICATION &
OVERVIEW OF THE DOCUMENT

Chapter-1 Introduction

1.1 Computerization and Internet Technologies
Since the advent of computer and information technology in the last two decades, every organization and individual wants the web-based services as it is convenient to use and easily accessible from anywhere in the world. The computerization has many benefits. Primarily a computer is helpful in four major aspects of any kind of organization:

* Time Efficiency * Cost Effective * Huge data storage capacity and * Simple operation

Moreover with the advent of the Internet technologies. World have change lot call it the social web. Through the .com bubble and bust, one trend has never wavered. Every year, millions more people around the world are using the internet to interact in more ways then ever before to date, find old classmates, check on medical elements and cures, to read and express alternative views of the news, and even to give live sales help online.

The service sector in today’s world is the fastest growing sector and the web-based services are not only the important but it is also in demand. With the fast growing network of optical fiver, making way to broadband it will be now easy and economical also to access the Internet, whether in monetary or information retrieval term.

The mere existence of the web is enriching. As it provides a huge diversity of views, take web logs, or blogs, which can assume the form of online diary or message board. The extract of all these is that if the data access retrieval and the goal everything is placed in an well order way on the net by using its technologies, we are not going to loose any way whether it is the user or the service provider.
A computer is now helpful in many other cases too:

1. Fast retrieval of information around the Globe by browsing the net. 2. Easy access by seating at home to most of the work places. 3. Easy database access with the invaluable functions of online entertainment and education for e.g. online education and many others. 1.2 About Project The project “Counseling Management System” is to exploit the computer technology with Internet Facility and all its aspects as necessity arises. The proposed project will be a web-based portal to provide Admissions in a particular college of any university for students. . The project "Counseling management system” is specially associated with online admission provide admission procedure and support to students and take their feedback. 1.3 Project Objective
The objective of the project “Counseling Management system” is to develop an online admission procedure of university of various colleges.
The major objectives of this project are as follows: -

* To provide a professional, moderator helps to candidates. * To provide a up to date information on status of seats. * To reduce the cost of counseling bone by the institutes. * O reduce the man power in physical counseling. * To provide a comfortable and convenient environment for the participating candidates. .

Chapter-2 Project Category & Requirement Satisfaction

2.1 Internet Technologies and .NET:
The undergoing project falls under Internet technologies & .NET category. Since the project is mainly responsible for creation of the website with the online database at backend. As we know that, the Internet is huge client server architecture. The client is the web browser; it is requesting a web based data, a file, or whatever, from some computer somewhere – anywhere –in the world. The server is that computer that holds the information you want.
VB.NET is a rich programming framework for building web-based applications. It offers outstanding support for both developers and administrators, providing improved ease-of-use, tool support, reliability, scalability, administration and security.
S.Q.L server 2000 is one of the leading R.D.B.M.S. software in the world. It is characterized by the quick retrieval of information from huge tables. This quality allows it to cater to the ever-changing business needs of the present age. It supports fourth generation language, SQL, thereby making it easier for the customers to grasp it, a development language where complicated procedures, functions etc. can be used.

Microsoft Visual Studio

Developed by | Microsoft | Stable release | 2005 Service Pack 1 (8.0.50727.762)(December 13,2006)[+/-] | Preview release | "Orcas" March 2007 CTP [+/-] | OS | Microsoft Windows | Available in | English, Italian | Genre | Integrated Development Environment | License | Microsoft EULA | Website | msdn.microsoft.com/vstudio |

Microsoft Visual Studio is the main Integrated Development Environment (IDE) from Microsoft. It can be used to develop console and GUI applications along with Windows Forms applications, web sites, web applications, and web services in both native code as well as managed code for all platforms supported by Microsoft Windows, Windows Mobile, .NET Framework, .NET Compact Framework and Microsoft Silverlight.

Visual studio includes the following: * Visual C++ * Visual C# * Visual Basic * Visual J# * Visual Web Developer * Some version includes a developer icon of Microsoft SQL Se

In the past, the following products were included: * Visual FoxPro is tightly integrated with its own relational database engine, which extends FoxPro's xBase capabilities to support SQL query and data manipulation. Unlike most database management systems * Visual InterDev is used to create web applications using Microsoft Active Server Pages (ASP) technologies. * Microsoft Visual J++ was Microsoft's implementation of the Java language (with Microsoft-specific extensions) and associated language services.

History:
Visual Studio 97
Microsoft first released Visual Studio in 1997, bundling together many of its programming tools for the first time. Visual Studio 97 was released in two editions, Professional and Enterprise. It included Visual Basic 5.0 and Visual C++ 5.0, primarily for Windows programming; Visual J++ 1.1 for Java and Windows programming; and Visual FoxPro 5.0 for database, specifically xBase programming. It introduced Visual InterDev for creating dynamically generated web sites using Active Server Pages. A snapshot of the Microsoft Developer Network library was also included.
Visual Studio 97 was Microsoft's first attempt at using the same development environment for multiple languages. Visual C++, Visual J++, InterDev, and the MSDN Library all used one environment, called Developer Studio. Visual Basic and Visual FoxPro used separate environments.

Visual Studio 6.0
The next version, version 6.0, was released in June 1998 and is the last version to run on the Win9x platform.[41] The version numbers of all of its constituent parts also moved to 6.0, including Visual J++ which jumped from 1.1, and Visual InterDev which was at 1.0. This version was the basis of Microsoft's development system for the next four years, as Microsoft transitioned their development focus to the .NET Framework.
Visual Studio 6.0 was the last version to include Visual Basic as most of its programmers knew it; subsequent versions would include a quite different version of the language based on .NET. It was also the last version to include Visual J++, which included deeper ties to Windows and proprietary extensions to the Java language that were incompatible with Sun's version. This caused Sun to sue Microsoft. As part of the settlement, Microsoft would no longer sell programming tools that targeted the Java Virtual Machine.
Visual Basic, Visual C++, and Visual FoxPro had their own IDE environments, while Visual J++ and Visual InterDev shared a common new environment. This new IDE environment was designed with extensibility in mind and would go on to become the integrated IDE for all languages with the release of Visual Studio .NET. Visual Studio 6.0 was also the last version to include Visual FoxPro.

Visual Studio .NET (2002)

Microsoft released Visual Studio .NET, codenamed Rainier (for Washington's Mount Rainier), in February 2002 (the beta version was released on the Microsoft developer network in 2001). The biggest change was the introduction of a managed code development environment using the .NET Framework. Programs developed using .NET are not compiled to machine language (like C++ is, for example) but instead to a format called Microsoft Intermediate Language (MSIL) or Common Intermediate Language (CIL). When an MSIL application is executed, it is compiled while being executed into the appropriate machine language for the platform it is being executed on, thereby making code portable across several platforms. Programs compiled into MSIL can be executed only on platforms which have an implementation of Common Language Infrastructure. It is possible to run MSIL programs in Linux or Mac OS X using non-Microsoft .NET implementations like Mono and DotGNU.This was the first version of Visual Studio to require an NT-based Windows platform. The installer enforces this requirement. Microsoft introduced C# (C-sharp), a new programming language that targets .NET. It also introduced the successor to Visual J++ called Visual J#. Visual J# programs use Java's language syntax. However, unlike Visual J++ programs, Visual J# programs can only target the .NET Framework, not the Java Virtual Machine that all other Java tools target.
Visual Studio .NET 2003
In April 2003, Microsoft introduced a minor upgrade to Visual Studio .NET in 2003 called Visual Studio .NET 2003, codenamed Everett (for the city of the same name). At that point, it referred to the previous version as Visual Studio .NET 2002. It included an upgrade to the .NET Framework, version 1.1. It also came with built-in support for developing programs for mobile devices, using either ASP.NET or the .NET Compact Framework. As well, the Visual C++ compiler was improved to be more standards-compliant, especially in the area of partial template specialization. Visual C++ Toolkit 2003, a free version of the same C++ compiler shipped with Visual Studio .NET 2003 without the IDE, though it is no longer available and now superseded by the Express Editions. The internal version number of Visual Studio .NET 2003 is version 7.1 while the file format version is 8.0.Microsoft released Service Pack 1 for Visual Studio 2003 on September 13, 2006.Visual Studio .NET 2002 and 2003 shipped in four editions: Academic, Professional, Enterprise Developer, and Enterprise Architect. The Visual Studio .NET 2003 Enterprise Architect edition included an implementation of Microsoft Visio 2002's modeling technologies, which focused on creating Unified Modeling Language-based visual representations of an application's architecture. "Enterprise Templates" were also introduced, to help larger development teams standardize coding styles and enforce policies around component usage and property settings. Visual Studio 2005 Team Suite included Visio for Enterprise Architects 2005 (VEA 2005) based on Visio 2003
Visual Studio 2005
Visual Studio 2005, codenamed Whidbey (a reference to Whidbey Island in Puget Sound), was released online in October 2005 and hit the stores a few weeks later. Microsoft removed the ".NET" moniker from Visual Studio 2005 (as well as every other product with .NET in its name), but it still primarily targets the .NET Framework, which was upgraded to version 2.0. It is the last version available for Windows 2000. Visual Studio 2005's internal version number is 8.0 while the file format version is 9.0. Microsoft released Service Pack 1 for Visual Studio 2005 on 14 December 2006.. An additional update for Service Pack 1 that offers Windows Vista compatibility was made available on 3 June 2007.
Visual Studio 2005 was upgraded to support all the new features introduced in .NET Framework 2.0, including generics and ASP.NET 2.0. The IntelliSense feature in Visual Studio was upgraded for generics and new project types were added to support ASP.NET web services. Visual Studio 2005 also includes a local web server, separate from IIS, that can be used to host ASP.NET applications during development and testing. It also supports all SQL Server 2005 databases. Database designers were upgraded to support the ADO.NET 2.0, which is included with .NET Framework 2.0. C++ also got a similar upgrade with the addition of C++/CLI which is slated to replace the use of Managed C++. Other new features of Visual Studio 2005 include the "Deployment Designer" which allows application designs to be validated before deployments, an improved environment for web publishing when combined with ASP.NET 2.0 and load testing to see application performance under various sorts of user loads.
Future development
Visual Studio 2008, codenamed Orcas, is the successor to Visual Studio 2005. It was released to MSDN subscribers on 19 November 2007 alongside .NET Framework 3.5. The codename Orcas is, like Whidbey, a reference to an island in Puget Sound, Orcas Island. The source code for the Visual Studio 2008 IDE will be available under a shared source license to some of Microsoft's partners and ISVs.
Visual Studio 2008 is focused on development of Windows Vista, 2007 Office system, and Web applications. Among other things, it brings a new language feature, LINQ, new versions of C# and Visual Basic languages, a Windows Presentation Foundation visual designer, and improvements to the .NET Framework. It also features a new HTML/CSS editor influenced by Microsoft Expression Web. J# is not included.Visual Studio 2008 requires .NET Framework 3.5 and by default configures compiled assemblies to run on .NET Framework 3.5; but it also supports multi-targeting which lets the developers choose which version of the .NET Framework (out of 2.0, 3.0, 3.5, Silverlight CoreCLR or .NET Compact Framework) the assembly runs on. Visual Studio 2008 also includes new code analysis tools, including the new Code Metrics tool. For Visual C++, Visual Studio adds a new version of Microsoft Foundation Classes (MFC 9.0) that adds support for the visual styles and UI controls introduced with Windows Vista. For native and managed code interoperability, Visual C++ introduces the STL/CLR, which is a port of the C++ Standard Template Library (STL) containers and algorithms to managed code. STL/CLR defines STL-like containers, iterators and algorithms that work on C++/CLI managed objects

.NET Framework

Microsoft .NET Framework is a software component that is a part of Microsoft Windows operating systems. It has a large library of pre-coded solutions to common programming problems and manages the execution of programs written specifically for the framework. The .NET Framework is a key Microsoft offering and is intended to be used by most new applications created for the Windows platform. The pre-coded solutions that form the framework's Base Class Library cover a large range of programming needs in areas including user interface, data access, database connectivity, cryptography, web application development, numeric algorithms, and network communications. The class library is used by programmers who combine it with their own code to produce applications.
Programs written for the .NET Framework execute in a software environment that manages the program's runtime requirements. This runtime environment, which is also a part of the .NET Framework, is known as the Common Language Runtime (CLR). The CLR provides the appearance of an application virtual machine so that programmers need not consider the capabilities of the specific CPU that will execute the program. The CLR also provides other important services such as security, memory management, and exception handling. The class library and the CLR together compose the .NET Framework. The .NET Framework is included with Windows XP, Windows Server 2003, Windows Server 2008 and Windows Vista, and can be installed on some older versions of Windows
Principal Design Features
The .NET framework was designed with several intentions: * Interoperability:- Because interaction between new and older applications is commonly required, the .NET Framework provides means to access functionality that is implemented in programs that execute outside the .NET environment. Access to COM components is provided in the System.Runtime.InteropServices and System.EnterpriseServices namespaces of the framework, and access to other functionality is provided using the P/Invoke feature. * Common Runtime Engine:- Programming languages on the .NET Framework compile into an intermediate language known as the Common Intermediate Language or CIL (formerly known as Microsoft Intermediate Language, or MSIL). In Microsoft's implementation this intermediate language is not interpreted but rather compiled in a manner known as just-in-time compilation (JIT) into native code. The combination of these concepts is called the Common Language Infrastructure (CLI). Microsoft's implementation of the CLI is known as the Common Language Runtime (CLR). * Language Independence:- The .NET Framework introduces a Common Type System, or CTS. The CTS specification defines all possible datatypes and programming constructs supported by the CLR and how they may or may not interact with each other. Because of this feature, the .NET Framework supports the exchange of instances of types between programs written in any of the .NET languages. This is discussed in more detail in Microsoft .NET Languages. * Base Class Library:- The Base Class Library (BCL), part of the Framework Class Library (FCL), is a library of functionality available to all languages using the .NET Framework. The BCL provides classes which encapsulate a number of common functions, including file reading and writing, graphic rendering, database interaction and XML document manipulation. * Simplified Deployment:- Installation of computer software must be carefully managed to ensure that it does not interfere with previously installed software, and that it conforms to increasingly stringent security requirements. The .NET framework includes design features and tools that help address these requirements. * Security:- The design is meant to address some of the vulnerabilities, such as buffer overflows, that have been exploited by malicious software. Additionally, .NET provides a common security model for all applications. * Portability:- The design of the .NET Framework allows for it to be platform agnostic, and thus be cross platform compatible. That is, a program written to use the framework should run without change on any type of system for which the framework is implemented. Microsoft's commercial implementations of the framework cover Windows, Windows CE, and the Xbox 360. In addition, Microsoft submits the specifications for the Common Language Infrastructure (which includes the core class libraries, Common Type System, and the Common Intermediate Language)and the C# language,and the C++/CLI language to both ECMA and the ISO, making them available as open standards. This makes it possible for third parties to create compatible implementations of the framework and its languages on other platforms.

.NET Framework Architecture

Common Language Infrastructure(CLI)
The core aspects of the .NET framework lie within the Common Language Infrastructure, or CLI. The purpose of the CLI is to provide a language-agnostic platform for application development and execution, including functions for exception handling, garbage collection, security, and interoperability. Microsoft's implementation of the CLI is called the Common Language Runtime or CLR. The CLR is composed of four primary parts: * Common Type System (CTS) * Common Language Specification (CLS) * Metadata * Virtual Execution System (VES) * Just-in-Time Compiler (JIT)

Assemblies
The intermediate CIL code is housed in .NET assemblies. As mandated by specification, assemblies are stored in the Portable Executable (PE) format, common on the Windows platform for all DLL and EXE files. The assembly consists of one or more files, one of which must contain the manifest, which has the metadata for the assembly. The complete name of an assembly (not to be confused with the filename on disk) contains its simple text name, version number, culture, and public key token. The public key token is a unique hash generated when the assembly is compiled, thus two assemblies with the same public key token are guaranteed to be identical. A private key can also be specified known only to the creator of the assembly and can be used for strong naming and to guarantee that the assembly is from the same author when a new version of the assembly is compiled (required to add an assembly to the Global Assembly Cache).

Metadata
All CIL is Self-Describing through .NET metadata. The CLR checks on metadata to ensure that the correct method is called. Metadata is usually generated by language compilers but developers can create their own metadata through custom attributes. Metadata also contains information about the assembly. Metadata is also used to implement the reflective programming capabilities of .NET Framework.

Base Class Library (BCL)
The Base Class Library, sometimes incorrectly referred to as the Framework Class Library (FCL) (which is a superset including the Microsoft.* namespaces), is a library of classes available to all languages using the .NET Framework. The BCL provides classes which encapsulate a number of common functions such as file reading and writing, graphic rendering, database interaction, XML document manipulation, and so forth. The BCL is much larger than other libraries, but has much more functionality in one package.

Security
.NET has its own security mechanism with two general features: Code Access Security (CAS), and validation and verification. Code Access Security is based on evidence that is associated with a specific assembly. Typically the evidence is the source of the assembly (whether it is installed on the local machine or has been downloaded from the intranet or Internet). Code Access Security uses evidence to determine the permissions granted to the code. Other code can demand that calling code is granted a specified permission. The demand causes the CLR to perform a call stack walk: every assembly of each method in the call stack is checked for the required permission and if any assembly is not granted the permission then a security exception is thrown.When an assembly is loaded the CLR performs various tests. Two such tests are validation and verification. During validation the CLR checks that the assembly contains valid metadata and CIL, and it checks that the internal tables are correct. Verification is not so exact. The verification mechanism checks to see if the code does anything that is 'unsafe'. The algorithm used is quite conservative and hence sometimes code that is 'safe' is not verified. Unsafe code will only be executed if the assembly has the 'skip verification' permission, which generally means code that is installed on the local machine.

Standardization and licensing
In August 2000, Microsoft, Hewlett-Packard, and Intel worked to standardize CLI and the C# programming language. By December 2001, both were ratified ECMA standards (ECMA 335 and ECMA 334). ISO followed in April 2003 - the current version of the ISO standards are .While Microsoft and their partners hold patents for the CLI and C#, ECMA and ISO require that all patents essential to implementation be made available under "reasonable and non-discriminatory (RAND) terms." In addition to meeting these terms, the companies have agreed to make the patents available royalty-free. However, this does not apply for the part of the .NET Framework which is not covered by the ECMA/ISO standard, which includes Windows Forms, ADO.NET, and ASP.NET. Patents that Microsoft holds in these areas may deter non-Microsoft implementations of the full framework. On October 3, 2007, Microsoft announced that much of the source code for the .NET Framework Base Class Library (including ASP.NET, ADO.NET and Windows Presentation Foundation) will be made available with the final release of Visual Studio 2008 towards the end of 2007 under the shared source Microsoft Reference License. The source code for other libraries including Windows Communication Foundation (WCF), Windows Workflow Foundation (WF) and Language Integrated Query (LINQ) will be added in future releases. Being released under the Microsoft Reference License means this source code is made available for debugging purpose only, primarily to support integrated debugging of the BCL in Visual Studio.

Versions
.NET Framework 1.0
This is the first release of the .NET Framework. Released on February 13, 2002. Available for Windows 98, NT 4.0, 2000, and XP. Mainstream support by Microsoft for this version ended July 10th, 2007, and extended support ends July 14th, 2009

.NET Framework 1.1
This is the first major .NET Framework upgrade. It is available on its own as a redistributable package or in a software development kit, and was published on April 3, 2003. It is also part of the second release of Microsoft Visual Studio .NET (released as Visual Studio .NET 2003). This is the first version of the .NET Framework to be included as part of the Windows operating system, shipping with Windows Server 2003. Mainstream support for .NET Framework 1.1 ends on October 14th, 2008, and extended support ends on October 8th, 2013. Since .NET 1.1 is a component of Windows Server 2003, extended support for .NET 1.1 on Server 2003 will run out with that of the OS - currently June 30th, 2013.

Changes since 1.0 * Built-in support for mobile ASP.NET controls. Previously available as an add-on for .NET Framework, now part of the framework. * Security changes - enable Windows Forms assemblies to execute in a semi-trusted manner from the Internet, and enable Code Access Security in ASP.NET applications. * Built-in support for ODBC and Oracle databases. Previously available as an add-on for .NET Framework 1.0, now part of the framework. * .NET Compact Framework - a version of the .NET Framework for small devices. * Internet Protocol version 6 (IPv6) support. * Numerous API changes.

.NET Framework 2.0
Released with Visual Studio 2005, Microsoft SQL Server 2005, and BizTalk 2006. * The 2.0 Redistributable Package can be downloaded for free from Microsoft, and was published on 2006-01-22. * The 2.0 Software Development Kit (SDK) can be downloaded for free from Microsoft. * It is included as part of Visual Studio 2005 and Microsoft SQL Server 2005. * Version 2.0 is the last version with support for Windows 2000, Windows 98 and Windows Me. * It shipped with Windows Server 2003 R2 (not installed by default).

Changes since 1.1 * Numerous API changes. * A new hosting API for native applications wishing to host an instance of the .NET runtime. The new API gives a fine grain control on the behavior of the runtime with regards to multithreading, memory allocation, assembly loading and more (detailed reference). It was initially developed to efficiently host the runtime in Microsoft SQL Server, which implements its own scheduler and memory manager. * Full 64-bit support for both the x64 and the IA64 hardware platforms. * Language support for Generics built directly into the .NET CLR. * Many additional and improved ASP.NET web controls. * New data controls with declarative data binding. * New personalization features for ASP.NET, such as support for themes, skins and webparts. * .NET Micro Framework - a version of the .NET Framework related to the Smart Personal Objects Technology initiative.

.NET Framework 3.0
.NET Framework 3.0, formerly called WinFX, includes a new set of managed code APIs that are an integral part of Windows Vista and Windows Server 2008 operating systems. It is also available for Windows XP SP2 and Windows Server 2003 as a download. There are no major architectural changes included with this release; .NET Framework 3.0 uses the Common Language Runtime of .NET Framework 2.0. Unlike the previous major .NET releases there was no .NET Compact Framework release made as a counterpart of this version.
.NET Framework 3.0 consists of four major new components: * Windows Presentation Foundation (WPF), formerly code-named Avalon; a new user interface subsystem and API based on XML and vector graphics, which uses 3D computer graphics hardware and Direct3D technologies. See WPF SDK for developer articles and documentation on WPF. * Windows Communication Foundation (WCF), formerly code-named Indigo; a service-oriented messaging system which allows programs to interoperate locally or remotely similar to web services. * Windows Workflow Foundation (WF) allows for building of task automation and integrated transactions using workflows. * Windows CardSpace, formerly code-named InfoCard; a software component which securely stores a person's digital identities and provides a unified interface for choosing the identity for a particular transaction, such as logging in to a website.

.NET Framework 3.5
Version 3.5 of the .NET Framework was officially released to manufacturing (RTM) on November 19, 2007. As with .NET Framework 3.0, version 3.5 uses the CLR of version 2.0. In addition, it installs .NET Framework 2.0 SP1, which adds some methods and properties to the BCL classes in version 2.0 which are required for version 3.5 features such as Language Integrated Query (LINQ). These changes do not affect applications written for version 2.0, however.[15]
As with previous versions, a new .NET Compact Framework 3.5 was released in tandem with this update in order to provide support for additional features on Windows Mobile and Windows Embedded CE devices.
The source code of the Base Class Library in this version has been partially released under Microsoft Reference License

.NET vs. Java and Java EE
The CLI and C# have many similarities to Sun's JVM and Java. They are strong competitors. Both are based on a virtual machine model that hides the details of the computer hardware on which their programs run. Both use their own intermediate byte-code, Microsoft calling theirs Common Intermediate Language (CIL; formerly MSIL) and Sun Java bytecode. On .NET the byte-code is always compiled before execution, either Just In Time (JIT) or in advance of execution using the ngen.exe utility. With Java the byte-code is either interpreted, compiled in advance, or compiled JIT. Both provide extensive class libraries that address many common programming requirements and address many security issues that are present in other approaches. The namespaces provided in the .NET Framework closely resemble the platform packages in the Java EE API Specification in style and invocation.
.NET in its complete form (Microsoft's implementation) is only available on Windows platforms and partially available on Linux and Macintosh whereas Java is fully available on nearly all platforms.From its beginning .NET has supported multiple programming languages and at its core remains platform agnostic and standardized so that other vendors can implement it on other platforms (although Microsoft's implementation only targets Windows, Windows CE, and Xbox platforms). The Java platform was initially built to support only the Java language on many operating system platforms under the slogan "Write once, run anywhere." Other programming languages have been implemented on the Java Virtual Machine but are not widely used.[citation needed]
Sun's reference implementation of Java (including the class library, the compiler, the virtual machine, and the various tools associated with the Java Platform) is becoming open source under the GNU GPL license with Classpath exception.

Criticisms
Some concerns and criticisms relating to .NET include: * Applications running in a managed environment such as the Microsoft framework's CLR or Java's JVM tend to require more system resources than similar applications that access machine resources more directly. Some applications, however, have been shown to perform better in .NET than in their native version.[citation needed] This could be due to the runtime optimizations made possible by such an environment, the use of relatively well-performing functions in the .NET framework, just-in-time compilation of managed code, or other aspects of the CLR. * As JIT languages can be more easily reverse-engineered than native code to algorithms used by an application there is concern over possible loss of trade secrets and the bypassing of license control mechanisms. Many obfuscation techniques already developed, however, can help to prevent this; indeed Microsoft's Visual Studio 2005 includes such a tool produced by PreEmptive Solutions (see dotfuscator). * In a managed environment such as the Microsoft framework's CLR or Java's JVM the regularly occurring garbage collection for reclaiming memory suspends execution of the application for an unpredictable lapse of time (typically no more than a few milliseconds). This makes such environments unsuitable for applications such as those that must respond to events with sub-second timing (see real-time computing). * Since the framework is not pre-installed on older versions of Windows an application that requires it must verify that it is present, and if it is not, guide the user to install it. This requirement may deter some from using the application. * Newer versions of the framework (3.5 and up) are not pre-installed on any versions of the Windows operating system. Some developers have expressed concerns about the large size (around 54 MB for end-users with .NET 3.0 and 197 MB with .NET 3.5) and reliability of .NET framework runtime installers for end-users.

Alternative implementations
The Microsoft .NET Framework is the predominant implementation of .NET technologies. Other implementations for parts of the framework exist. Since the runtime engine is described by an ECMA/ISO specification, other implementations of it are unencumbered by copyright issues. It is more difficult to develop alternatives to the base class library (BCL), which is not described by an open standard, and may be subject to copyright restrictions. Additionally, parts of the BCL have Windows-specific functionality and behavior, so implementation on non-Windows platforms can be problematic.
Some alternative implementations of parts of the framework are listed here. * Microsoft's Shared Source Common Language Infrastructure is a shared source implementation of the CLR component of the .NET Framework. It runs on Microsoft Windows XP, FreeBSD, and Mac OS X 10.2. * Portable.NET (part of DotGNU) provides an implementation of the Common Language Infrastructure (CLI), portions of the .NET Base Class Library (BCL), and a C# compiler. It supports a variety of CPUs and operating systems. * Mono is an implementation of the CLI and portions of the .NET Base Class Library (BCL), and provides additional functionality. It is dual-licensed under free software and proprietary software licenses. Mono is being developed by Novell, Inc. It includes support for ASP.NET, ADO.NET, and evolving support for Windows Forms libraries. It also includes a C# compiler, and a VB.NET compiler is in pre-beta form. * CrossNet is an implementation of the CLI and portions of the .NET Base Class Library (BCL). It is free software. It parses .NET assemblies and generates unmanaged C++ code that can be compiled and linked within any ANSI C++ application on any platform. * .NET for Symbian .NET Compact Framework implementation for Symbian (S60)

* INTRODUCTION TO ADO.NET

Earlier, most of the Windows Applications consisted of static information. These allowed the visitor to read information only. Windows Applications were not very interactive and did not store any information about the user. If information about user has to be stored, a database will come into the picture and a data access strategy is required. This data access strategy will allow the programmer to make a connection with the database and provide commands to retrieve, insert, update, and delete data. In this session, we will be covering Microsoft’s latest release in data access strategies- ADO.NET, designed specifically for database handling in web applications.

DATA CONNECTIVITY IN ADO.NET

Previously, most of the applications being built were client-server application. Client-server application needs to maintain a continuous connection with the database as long as the application is running. Maintaining a continuous connection is not advantages due to the following reasons;

Most databases can only maintain a small number of connections simultaneously. The overhead of maintaining these connections reduces the overall performance of the application.

Increasing the size of such applications is very difficult since the application might not perform well when the number of users is more as when the number of users is less.
Moreover, when there are many users in an organization and two users need to share the same data, then some means must be created by which these users can pass the data back and forth.

Due to the above disadvantage of maintaining a continuous connection, Microsoft has created the disconnected data architecture for ADO.NET. Applications using ADO.NET connect to the database only to retrieve or update data. Once that is done, the data base is free to service other users. Thus, the database is not tied up with users who are not using the database but are still maintaining a connection to it.

THE ADO.NET OBJECT MODEL

ADO.NET has evolved from ADO data access model. ADO.NET possesses two core components.

Datasets
NET Data providers

The .NET data provider permits the user to create a connection to the database for the purpose of allowing the user to retrieve the data in to a data reader or a dataset as per the user’s requirements. The data in a dataset is stored in the form of a data table object. Also, the user can insert, update, and delete data using the command objects.

The ADO.NET object model is illustrated in the following figure:

DATA SETS

Data can be retrieved from the database and directly displayed to the user through forms whenever the user raises the request. Every such request made by the user has to be fulfilled by fetching the data from the server. This will increase the number of trips back and forth to the server. Fetching the data in a group will reduce the no. of trips that need to be made to the server. Additionally, many a times, a group of data may need to be handled sequentially. For example consider the calculation of price per item in an order. The unit rate of an item should be multiplied by the quantity bought for each item to get the total price per item .Thus, an object that can hold the data fetched from the server is very essential. Datasets serve this purpose.

Dataset is an object in which the data retrieved from the database can be stored .the datasets can contain one or more tables and information about the relationships and constraints. The data in the dataset is stored in the form of data table objects. The data table structure is defined by rows and columns and constraints. The column is defined by data column object. The data column object is referenced by the column property of the data table. The constraints that can be set on the table are:

1 Unique constraint

The unique constraint object ensures that all the rows in the table contain a unique value for the column to which the unique constraint object is assigned.

2 Foreign key constraint

In this object restricts the updating and deletion of data in tables that are related.

The actual data is represented by the data view object. The data in the data row can be changed. This object maintains both the original and current state of the data.

.NET DATA Providers

It contains objects that provide access to the data from various data sources. The data can also be manipulated through these data providers. The data sources can either be based on a database or non-database store like XML and excel spreadsheets . the .NET data providers perform all the interaction required between the dataset and the database. The .NET data providers uses the following objects:

3 connection object

it is used to establish a connection between the application and database .

4 command object

it allow the user to retrieve and manipulate data in the database. The command object specifies the action that has to be performed on the database. The command object is carried over to the database on the connection object.

* DATAGRID

After adding records to the dataset, the next step is to view the records in a dataset. One control can be used for viewing and modifying the records is the datagrid control. First the data source for the datagrid is specified using the datasource property and then the data is bound to the specified using the databind( ) method . a datagrid can be created using the following syntax .

DATAVIEW

A data view is used to present a customized view of the data of a data table. A data view can be filtered, searched or sorted. For example, a data view can be used to filter out the employee data and retrieve data of only managers from the employee table . by using data views, two controls can be used to display different views/versions of the same table from the dataset. For example one control is used to display all the records from the table, while another control can display rows that are limited by a specific condition. This condition is set using the “row filter” property.

SQL Server

Microsoft SQL Server is a relational database management system (RDBMS) produced by Microsoft. Its primary query language is Transact-SQL, an implementation of the ANSI/ISO standard Structured Query Language (SQL) used by both Microsoft and Sybase.

History:
The code base for MS SQL Server (prior to version 7.0) originated in Sybase SQL Server, and was Microsoft's entry to the enterprise-level database market, competing against Oracle, IBM, and, later, Sybase itself. Microsoft, Sybase and Ashton-Tate originally teamed up to create and market the first version named SQL Server 1.0 for OS/2 (about 1989) which was essentially the same as Sybase SQL Server 3.0 on Unix, VMS, etc. Microsoft SQL Server 4.2 was shipped around 1992 (available bundled with Microsoft OS/2 version 1.3). Later Microsoft SQL Server 4.21 for Windows NT was released at the same time as Windows NT 3.1. Microsoft SQL Server v6.0 was the first version designed for NT, and did not include any direction from Sybase.
About the time Windows NT was released, Sybase and Microsoft parted ways and pursued their own design and marketing schemes. Microsoft negotiated exclusive rights to all versions of SQL Server written for Microsoft operating systems. Later, Sybase changed the name of its product to Adaptive Server Enterprise to avoid confusion with Microsoft SQL Server. Until 1994 Microsoft's SQL Server carried three Sybase copyright notices as an indication of its origin.
Since parting ways, several revisions have been done independently. SQL Server 7.0 was the first true GUI based database server and was a rewrite from the legacy Sybase code. It was succeeded by SQL Server 2000, which was the first edition to be launched in a variant for the IA-64 architecture.
In the six years since release of Microsoft's previous SQL Server product (SQL Server 2000), advancements have been made in performance, the client IDE tools, and several complementary systems that are packaged with SQL Server 2005. These include: an ETL tool (SQL Server Integration Services or SSIS), a Reporting Server, an OLAP and data mining server (Analysis Services), and several messaging technologies, specifically Service Broker and Notification Services.
Services:
SQL Server also includes an assortment of add-on services. While these are not essential for the operation for the database system, these provide value added services on top of the core database management system. These services either run as a part of some SQL Server component or out-of-process as Windows Service and presents their own API to control and interact with them.
Service Broker:- The Service Broker, which runs as a part of the database engine, provides a reliable messaging and message queuing platform for SQL Server applications. Used inside an instance, it is used to provide an asynchronous programming environment. For cross instance applications, Service Broker communicates over TCP/IP and allows the different components to be synchronized together, via exchange of messages.
Replication Services:- SQL Server Replication Services are used by SQL Server to replicate and synchronize database objects, either in entirety or a subset of the objects present, across replication agents, which might be other database servers across the network, or database caches on the client side. Replication follows a publisher/subscriber model, i.e., the changes are sent out by one database server ("publisher") and are received by others ("subscribers"). SQL Server supports three different types of replication * Transaction replication * Merge replication * Snapshot replication
Analysis Services:- SQL Server Analysis Services adds OLAP and data mining capabilities for SQL Server databases. The OLAP engine supports MOLAP, ROLAP and HOLAP storage modes for data. Analysis Services supports the XML for Analysis standard as the underlying communication protocol. The cube data can be accessed using MDX queries.Data mining specific functionality is exposed via the DMX query language. Analysis Services includes various algorithms - Decision trees, clustering algorithm, Naive Bayes algorithm, time series analysis, sequence clustering algorithm, linear and logistic regression analysis, and neural networks - for use in data mining
Reporting Services:- SQL Server Reporting Services is a report generation environment for data gathered from SQL Server databases. It is administered via a web interface. Reporting services features a web services interface to support the development of custom reporting applications. Reports are created as RDL files.Reports can be designed using recent versions of Microsoft Visual Studio(including Visual Studio.NET 2003 onwards) with Business Intelligence Development Studio, installed or with the included Report Builder. Once created, RDL files can be rendered in a variety of formats including Excel, PDF, CSV, XML, TIFF (and other image formats), and HTML Web Archive.
Notification Services:- SQL Server Notification Services is a platform for generating notifications, which are sent to Notification Services subscribers. A subscriber registers for a specific event or transaction (which is registered on the database server as a trigger); when the event occurs, Notification Services uses Service Broker to send a message to the subscriber informing about the occurrence of the event
Integration Services:- SQL Server Integration Services is used to integrate data from different data sources. It is used for the ETL capabilities for SQL Server for data warehousing needs. Integration Services includes GUI tools to build data extraction workflows integration various functionality such as extracting data from various sources, querying data, transforming data including aggregating, duplication and merging data, and then loading the transformed data onto other sources, or sending e-mails detailing the status of the operation

The SQL server 2000 include following features  Queries  Constraints  Procedures  Triggers  Batch Implementation  Functions  Cursors  Stored Procedures

Requirement specification 2.2 tools and platform of the project Platform : Windows The Operating System : Windows XP Professional Framework : Vb.Net Front-End Tool : Vb.NET with ASP.Net Editing tool : SQL Server 2000 ,2005 Scripting : VB.NET Back-End Tool : SQL SERVER 2000,2005 2.3 hardware Processor : Intel Core2Duo T5470@ 1.60GHz 1.60GHz

Memory : 1.00 G.B. DDR2 RAM

Network Adapter : Ethernet Adaptor

Modem : 56kbps Voice Fax Data

Secondary Storage : Hard Disk (80 G.B)

2.4 SOFTWARE REQUIREMENT SPECIFICATION The software requirement specification (SRS) is very important part of the software building process, which describes the actual user level requirement from technical point of view. i.e. what the user exactly wants? The objective of preparing the software requirement specification is to represent the requirements of the software in such a manner that ultimately leads to successful software implementation. It is the result of the analysis process of the software development. It should contain all the data the software is going to process, the function it will provide, and the behavior it will exhibit. This Software Requirements Specifications (SRS) is defined in IEEE Std. 830-1993, IEEE Recommended Practice for Software Requirements Specifications. The synopsis is prepared in the way to fulfill almost all the points needed in S.R.S.

Chapter-3 Project Modules & Testing And Validation Checks

The proposed website will have its main page and will be mainly divided into 14 Modules partially dependent and partially independent Modules are: 1. USER REGISTRATION 2. FORGOTTEN PASSWORD 3. TO CHANGE PASSWORD 4. ADMINISTRATOR 5. RESULT 6. SCREEN SHOTS

3.1 MODULES DSCRIPTION The modules descriptions are as follows USER REGISTRATION:
USER REGISTRATION is the module which checks for a valid student when the student enters his user Id/password and link to the correct page or denies and link to the registration page.He/she has to enter his/her particulars like application no,name,father's name,password,rank etc .It is the module, which handles the student's registration. FORGOTTEN PASSWORD
This modle has its own importance if a student has become forget his /her password then at the time of counseling he/she can use another features of forgotten password.
He/she entres his/her old password with new password,then this module creates a new password for candidates. . TO CHANGE PASSWORD His module helps the candidates to change his password at any time but for this he/she has to enter his/her user name,new password,confirm password,then it can change his/her password with new one. ADMINISTRATOR This module helps the candiates to provide a particular college according to their prospectives,according to their ranks. RESULT At last this module tell the candidates about their result of counseling on theire computer screen that which college you got it and which branch in that college.

SCREEN SHOTS

TESTING AND VALIDATION CHECKS

Approach of web app testing adopts the basic principle for all software testing and applies a strategy and tactics that have been recommended for object oriented system .the following steps summarizes the approach: 1. The content model for the web app is reviewed to uncover errors. This is like copy editing. 2. The design model for the web application as reviewed to uncover navigation error. Use cases derived as part of the analyst activity, allow a web Engineer to exercise each usage scenario against the architectural and navigational design. These non-executable test help uncover Error in navigation. 3. Selected processing component and web page is unit tested. When web apps are considered, the concepts of the unit changes, each web page encapsulated in itself content navigation link as well As script, form and applet (processing element). It is not always possible or practical to test each of these characteristics individually. 4. The architecture is constructed and integration tests are conducted.
The strategy for integration testing depends upon the architecture that has been chosen for the web application.

5. The assembled web application is tested for overall functionality and content delivery.
Like conventional validation, the validation of web based systems and application focuses on user visible action and user recognizable output from the system. To assist in the derivation of validation tests the tester should draw upon use cases the use cases provides a scenario that has high likelihood of uncovering errors in user interaction requirement.
6. The web application is implemented in a variety of different environmental configuration and is tested for compatibility with each configuration.

7. The web application is tested by controlled and monitored population of end user.
Finally with the modular concept inside the application it is being also tested for its Reliability:
The system reliability will be insured through data integrity rules built into the database at the backend and the system rules built into the front-end application. The system will take assurance from the user before making any changes permanent. MAINTAINABILITY: The system has been designed taking care of modularity. Faults in the system can be traced to modules and thus VALIDATION CHECKS
This will be as such to maintain consistent and persistent information on the web when most of the time the project has to deal with uploads so a minor error will down the impression of the company.
Therefore, validation checks by software itself using the flavors of JavaScript and manual checks are also necessary as: - 1. Correct entry of data in the form. 2. Correct updating of question and with the most suitable answer etc

Chapter-4 Scope of Future Applications & Overview of the Document Software scope describes the data and control to be processed, function performance, constraints, interfaces and reliability. Function describes in the statement of scope are evaluated and in some case refined to provide more detail prior to the beginning of the estimation. Because both cost and schedule estimates are functionally oriented, some degree of decomposition is often useful.
We can implement easily this application. Reusability is possible as and when we require in this application. We can update it next version. We can add new features as and when we require. There is flexibility in all the modules. Scope of this document is to put down the requirements, clearly identifying the information needed by the user, the source of the information and outputs expected from the system. Future scope
It is directly dependent on the lay stone of the project that is we will have to design a system which when the time passes having a better system initially should not become a joke later.
It is highly likely that the scope will change as the web application project moves forward; the web e-process model should be incremental. This allows the development team to “freeze” the scope for one increment so that an operational web application release can be created. The next increment may scope changes suggested by a review of the preceding increment, but once the second increment commences, scope is again frozen temporarily. This approach enables the Web-App team to work without having to accommodate a continual stream of changes but still recognizes the continuous evolution characteristics of most web application. Besides that, the following basic quality in the software always safeguards the future scope of the software. Reusability: Reusability is possible as and when we require in this application. We can update it next version. Reusable software reduces design, coding and testing cost by amortizing effort over several designs. Reducing the amount of code also simplifies understanding, which increases the likelihood that the code is correct. We follow up both types of reusability: Sharing of newly written code within a project and reuse of previously written code on new projects. Extensibility: This software is extended in ways that its original developers may not expect. The following principles enhance extensibility like Hide data structure, Avoid traversing multiple links or methods, Avoid case statements on object type and distinguish public and private operations. Understandability: A method is understandable if someone other than the creator of the method can understand the code (as well as the creator after a time lapse). We use the method with small and coherent helps to accomplish this. Cost-effectiveness: Its cost is under the budget and make within given time period. It is desirable to aim for a system with a minimum cost subject to the condition that it must satisfy all the requirements can be rectified easily. The entire source code is well structured and commented to ensure clarity and readability.

Portability: since it is a internet based application so its portability and usability depends upon the Clint connected with the internet. The interface designed that is the web page designing which is one of the major part of web application because it is the first impression regardless of the value of its contents interface should must grab a potential user immediately

OVERVIEW OF THE DOCUMENT

This document contains the system and software requirements in terms of what the system will be and what is expected from the system. This will also highlight the system behavior in terms of queries and reports generated by the system. It contains the user characteristics, access controls, assumptions, and dependencies on the system. The benefit of the system: Reduce in overheads paper works, zero delays in project completion, etc.
At last but not the least this project helps the all students to attend the university counseling without any problem. He/she an participate easily and comfortable in university counseling without any delay and have not pay a lot .
Its very time safety project and it’s so easy to handle .So this project is very effective for a university counseling.