ASP.NET Programming – An Introduction to ASP.NET Programming & Development
ASP.NET stands for active server pages and .NET framework. ASP.NET is a highly popular programming language. Unlike ASP run time ASP.NET uses the common language runtime. CLR is .NET runtime and it manages the execution of the code. CLR allows the objects that are created in different languages to interact with each other; in this way it removes the language barrier. CLR offer simplification of designing of web application. It has many other advantages that must be considered.
CLR improves the performance of a web application. The ASP.NET code is compiled CLR code. The CLR provides just in time compilation, native optimization, and caching. Compilation is a two stage process. In first stage code is compiled into the Microsoft Intermediate Language (MSIL). In the second stage at the execution time it is compiled into the native code. It is noteworthy that only the portion of the code is compiled into the native code which is needed the most. This is called just in time compilation. This feature leads to the overall improvement in the performance. Thus, ASP.NET programming saves time and energy both.
ASP.NET programming is flexible. You can access entire .NET class library with ASP.NET application. You can use language that is best suitable to your application this way it is language independent. ASP.NET application uses a set of default authorization and authentication schemes so they are most secured
ASP.NET reduces the amount of code required. This way you can build large application with an ease. It has pre-application configuration. The application level configuration is stored in XML format, which is easy to read and write. This format makes it easy to apply new settings to applications without the help of any local administration tools.
Visual studio development environment provides rich tool box. It provides WYSIWYG editing, drag-and-drop server controls, and automatic deployment etc. The source code and HTML are together so ASP.NET pages are easy to maintain and write. The source code is executed on the server. This gives lots of power and flexibility to the web pages.
ASP.NET is purely a server side technology so ASP.NET code is executed on server before it is sent to the browser. The Web server continuously monitors the pages, components and applications running on it. If it notices any memory leaks, infinite loops, other illegal activities, it immediately destroys those activities and restarts itself.
He is expert asp programmer & working at one of the best asp net developer company is IndiaNIC, offering complete web design & development solution within your means. For more information contact us.
Article from articlesbase.com
Categories: ASP.NET Tags: ASP.NET, Development, Introduction, programming
Introduction and History of ASP.NET
ASP.NET is from the same family as ASP(Active Server Pages), it is what you can call as the next generation ASP. It is however a more advanced version of the classic ASP and it is written in .Net language.ASP.NET is a web application framework developed and marketed by Microsoft, it allows programmers to build dynamic web sites, web applications and web services. It was released in January 2002 with version 1.0 of the .NET Framework. It is the advanced version of ASP technology. ASP.NET is built on the Common Language Runtime (CLR), allowing programmers to write ASP.NET code using any supported .NET language.
According to Microsoft, “ASP.NET is a technology for building powerful, dynamic Web applications and is part of the .NET Framework”. Being built on CLR it allows the programmers to write codes using any supporting .Net language. It can also process SOAP messages as it is allowed by the ASP.NET SOAP extension. One of the main differences between ASP.NET and Classic ASP/PHP is the fact that ASP.NET is compiled, while Classic ASP is always interpreted.
Performance wise ASP.NET aims for performance benefits over other script-based technologies by compiling the server-side code to one or more DLL files on the web server. This compilation happens automatically the first time a page is requested. This feature provides the smoothness of development offered by scripting languages with the performance benefits of a compiled binary. However, the compilation might cause short delays to the web user when the newly-edited page is first requested from the web server, but won’t again unless the page requested is updated further. ASP.NET will compile the entire site in batches of 1000 files upon first request. If the compilation delay is causing problems, the batch size or the compilation strategy may be tweaked.
It gives developers the choice to pre-compile their files before deployment with the help of MS Visual Studio eliminating the need for just-in-time compilation in a production environment. Microsoft has also released some extension frameworks that plug into ASP.NET and extend its functionality. Some of them are ASP.NET AJAX, ASP.NET MVC Framework etc. It has also a improved run-time error handling capability, making it much better than the classic ASP.
After the success of ASP.NE T 1.0 Microsoft launched the 2.0 version of ASP.NET, almost all criticisms and complaints about 1.0 was answered by 2.0. Due to its advanced features ASP.NET has become one of the most successful products by Microsoft. It has helped the programmers to build many great and dynamic web sites and applications.
The author of this article has written various articles related to ASP.Net Development and Web Design India. He has experience of over 5 years in these fields.
Article from articlesbase.com
Find More ASP.NET Articles
Categories: ASP.NET Tags: ASP.NET, History, Introduction
WCF by Example – Introduction
This article is the first of a series that discusses how to design and develop a WPF client using WCF for communication and NHibernate for persistence purposes.
Designing enterprise applications requires a comprehensive set of skills. In small and medium projects allocation of time and resources could be not feasible to the extent that is in larger projects, it is at this time where a source for best practices and patterns can become very beneficial. There are plenty articles, books and other materials covering specific aspects but it is almost impossible to find a single place where all the technologies and patterns are used in conjunction providing a comprehensive discussion of the why and how.
The intention of these articles is to provide an example of how a full enterprise application is developed from the early stages to a full functional stage. The articles build on top of each other where new aspects are covered or/and existing functionality is enhanced as a result of aligning the architect to the business non-functional requirements.
It is assumed in the series that Agile practices are followed so the solution’s architect focuses in providing flexible mechanisms for RAD, DDD and TDD methodologies. One key aspect of the architect is the requirement to be able to deploy a full-functional client for business exploration purposes that requires a minimum infrastructure footprint; avoiding databases, deployment to IIS and so on.
The architect requirements are as follow:
Rich client using WPF Client connects to server using WCF services NHibernate is used for persistence purposes Client application can be run against in-memory repositories (Exploration Client) Deployment of the exploration client must be kept simple The application must be easily testable, tests can be run against in-memory or NHibernate repositoriesOther assumptions:
We have full control over the client and server components We are creating the database from scratch, we are not using some legacy database We are deploying the server components using IIS7 and WAS; we will use TCP/IP We have full design control over the PK in the database tables, we will using unique long fields for all our entities in this projectWe are going to start using a very simple business scenario in our series, the focus on the series is the architecture not the business domain. We may extend our domain in the future if we find that we want to explore some more complex architect concepts.
The business domain is based in a simple list of contacts, it is currently so simple that one single entity is only required: Customer. The solution name is eDirectory.
The source code can be found at codeplex: WCF by Example
The latest version can be found at the trunk branch, each chapter is located at its own tag branch. You may want to use the browse function within Codeplex to navigate among the branches.
The eDirectory application defines three well differentiated application components: the database, server and client.
Within the client and server the application is structured into layers, in most cases the layers are stacked one beside each other, continuous layers are provided with decoupled mechanisms so different implementations can be used. Some services are available across multiple layers.
As we earlier mentioned, we have full control of the clients and server. So we will not relay on late service discovery, instead the service contracts are available at both sides of the application. This is also true for the DTOs and some common business validation. As a result, a Common assembly is defined that contains components shared by the server and client applications.
In the server side we find the core components, the business domain declares the business entities and their behavior (action methods). Then services are declared that exposes our domain action methods. The services for persistence and serialisation constraints only expose DTOs between the client and server. As a result, the transformation of entities to DTOs needs to be addressed in a comprehensive manner.
In order to decouple our business domain from the database, the repository components are responsible for the persistence of our entities. We will define a generic interface between these two layers. Two concrete implementations of the repositories are available: in-memory and NHibernate.
The transaction manager is our “unit of work” implementation. It is responsible for our business transactions and the handling of business messages (warnings and exceptions).
Finally, but not the least, we have the client components. The client is a WPF application designed using the MVVM pattern. This pattern provides a neat view XAML component with none or very little code behind, the binding capabilities of XAML in conjunction with the ViewModel class leverages how the client renders the DTOs provided by the services layers.
The client decouples the service layers into two main components. The adapter is responsible for the managing of business messages retrieved during the execution of services. The WCF Proxy layer is responsible for the management of WCF services, the design is neat and is a nice way of decoupling the client from the WCF service.
Categories: C# Tags: Example, Introduction
Silverlight Introduction
This article will be very helpful for the beginners who want to know and start development on Silverlight projects, if you are already working on Silverlight you will find complete understanding of Silverlight Introduction. In this article I have started with definition of Silverlight, purpose of the Silverlight technology and different versions released so far. You will also see development tools required to work with Silverlight. End of this article you will get the complete introduction of Silverlight.
What is Silverlight? Silverlight is the new Microsoft technology on web platform for Rich Internet Applications (RIA) launched by Microsoft in 2007.Silverlight supports multiple browsers called cross-browser technology, which includes Internet Explorer, Firefox, and Safari, opera etc…Silverlight supports multiple Operating Systems called cross-platform technology, which includes Windows family of OS, Mac, and Linux with moonlight technology (Moonlight is an open source implementation of Silverlight, primarily for Linux and other Unix/X11 based operating systems).Silverlight is also supports multiple devices called cross-device technology, which include mobile devices to desktop browsers to 720p HDTV video modes etc…
Silverlight is a browser plug-in approximately 4MB in size, it is client side free software for easy and fast less than 10 sec one time installation available for any client side browsers.Silverlight supports the display of high-definition video files, and sending them over the Net. Silverlight applications are delivered to a browser in a text-based markup language called XAML. XAML is a declarative markup language that you can use to define the UI elements for your Silverlight-based application.Silverlight is considered as a competitor to Adobe’s flash technology.One of the design goals of the Silverlight technology is to fill the gap between windows application and web application in terms of creating Graphical User Interface (GUI). So far web developers were not able to make client happy in terms of UI, but now web developer will be able to full fill this with the help of Silverlight technology. Why Silverlight?
Here is the list of advantage why we should go with Silverlight over the Flash and other technologies already available: Support of .NET framework – if you are already .NET developer it is easy to start programming on Silverlight.Support of Managed code – you can write programming in your favorite language which .NET CLR supports like C#,VB.NET, Dynamic languages(IronPython, IronRuby).Better development tools -Visual Studio 2010, Expression Blend.Large community- available lot of learning resource as compare to Flash technology.Integration with Enterprise based technologies like WPF, LINQ etc…Silverlight releases
Silverlight 1.0
This is the first release of Silverlight technology in 2007. There are lot of releases happened in initial stage of Silverlight technology, however later at end of the year 2007 final release of version 1.0 got released. Originally this release was called WPF/E, which stands for Windows Presentation Foundation/ Everywhere. This release consists of the core presentation framework, which is responsible for UI, interactivity and user input, basic UI controls, graphics and animation, media playback and DOM integration.
The Major drawback of this release is not supporting managed code, which means you can’t use .NET supported programming languages for manipulating GUI elements. This was managed by scripting programming languages like Java Script (Only interpretation no compilation), which is hard for non Java Script programmers.
Applications are written either completely in XAML or in a mix of XAML and JavaScript with DOM (Document Object Model) to manipulate the user interface. Since there is no managed code there is no compilation required only JavaScript is interpreted on the client (browser).
Silverlight application starts by invoking the Silverlight control from the HTML page, which then loads up a XAML file. The XAML file contains a Canvas object, which acts as placeholder for other elements. Silverlight provides various geometrical primitives like lines, ellipses and other shapes, to elements like text, images, and media etc.
Silverlight 2.0
After Silverlight 1.0 there are preview releases to fix bugs from initial release and improved performance issues then released Silverlight 2.0 in March 2008. We can consider this is the first release of the Silverlight for start application development because of lot limitations in Silverlight 1.0 and was not ready for developing applications efficiently. This is the exciting release to the developers, which supports managed code, living in the .NET world without managed code is very difficulty (actually not possible ). Silverlight 2.0 supports .NET programming languages like C#, VB.NET to write business logic or manipulate UI Elements at client side. Silverlight 2.0 is based on .NET Framework 3.5.
You can have a code behind file for every XAML (.xaml) file like ASP.NET (.aspx) pages to handle the business logic. It can be used to programmatically manipulate both the Silverlight application and the HTML page which hosts the Silverlight control. The XAML markup as well as the code, is compiled into .NET assemblies which are then compressed using ZIP and stored in a .xap file.
In this release Silverlight came up with own library, which is subset of .NET framework’s Base Class Library this included controls, components, support of web services and LINQ API features. It is also provides security, not to access Silverlight platform API from outside the world.
Features of Silverlight 2.0: Rich base class library: – This is a compatible subset of the full .NET Framework. It supports Collection, Reflection, Regular Expressions, String Handling, Data Access, LINQ etc…
Powerful built-in controls: – These include verity of controls :
o Extensible control base classes
o Common controls: Textbox, Checkbox, Radiobutton, TabControl, Slider, ScrollViewer, ProgressBar, Calendar etc…
ayout controls: Grid, StackPanel etc…
ata controls:DataGrid, etc..
Advanced skinning and templating support: – This makes it easy to customize the look and feel of an application.
Deep zoom: – which allows users to zoom into, or out of, an image (or a collage of images), with smooth transitions, using the mouse wheel.
Networking support:- Out-of-the-box support allows calling REST, WS*/SOAP, POX, RSS and standard HTTP services, enabling users to create applications that easily integrate with existing back-end systems.
Programming Languages:- including Visual Basic, C#, JavaScript, IronPython and IronRuby, making it easier for developers already familiar with one of these languages to repurpose their existing skill sets.
Cross-platform and cross-browser support: – This includes support for Mac, Windows and Linux in Firefox, Safari and Windows Internet Explorer.
Security: – Silverlight CoreCLR uses an attribute-based security model, as opposed to the Code Access Security (CAS) model of the desktop version of .NET Framework.
Silverlight 3
Silverlight version 3.0 was release in July 9, 2009, which is an extension to Silverlight 2.0 and mainly provides improvements in graphics capabilities, media management, application development areas (additional controls, enhanced binding support, and out-of-browser functionality), and integration in the designers’ Expression Blend 3 tools.
Features of Silverlight 3.0: Improved graphics capabilities to support a richer and more interactive user interface
-> Support for 3D graphics
-> Animation
-> Pixel Shaders
-> Theme application support
-> Enhanced control-skinning
-> Improved text rendering
-> Bitmap APIs
Enhanced media management supporting high-quality and secured multimedia streaming
-> Support for new media formats
-> IIS Media Services-> Silverlight DRM for media streaming
Empowers developers to develop data-rich and media-rich interactive RIAs.
-> New networking APIs (new offline APIs Out-of-Browser functionality )
-> Silverlight 3 SDK
-> New FormsXAML controls
-> New DataManipulationXAML controls
-> New ContentXAML controls
-> Other user interface framework improvements
-> Search Engine Optimization (SEO)Silverlight 4.0
Silverlight version 4.0 beta was release on November 18, 2009, at the Professional Developers Conference in Los Angeles, Microsoft Corp.
Features of Silverlight 4.0 beta:
Development tools Visual Studio 2008 SP1: – Visual Studio provides productivity tools for developing applications using managed code. All the existing features of Visual Studio are available for Silverlight. In addition, this version of Visual Studio includes Silverlight-specific features, including IntelliSense, debugging, and Silverlight project templates that create and link all required files. http://www.microsoft.com/downloads/details.aspx?familyid=FBEE1648-7106-44A7-9649-6D9F6D58056E&displaylang=en
Microsoft Expression Blend: -This tool can be used to create and modify the presentation layer of an application by manipulating the XAML canvas and controls, working with graphics, and programming the presentation layer with a dynamic language such as JavaScript. http://www.microsoft.com/downloads/details.aspx?FamilyID=e82db5e2-7106-419e-80b0-65cce89f06bb&displaylang=en
Install Deep Zoom Composer: – This tool allows you to prepare your images for use with the Deep Zoom feature in Silverlight 3. http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=457b17b7-52bf-4bda-87a3-fa8a4673f8bf
Download Silverlight Toolkit: -This Toolkit is a Microsoft project containing Silverlight controls, components and utilities that can be downloaded and used in your Silverlight applications. It includes full source code, samples and tests. http://silverlight.codeplex.com/releases/view/36060
Download .NET RIA Services: – Microsoft .NET RIA Services simplifies the traditional n-tier application pattern by bringing together the ASP.NET and Silverlight platforms. The RIA Services provides a pattern to write application logic that runs on the mid-tier and controls access to data for queries, changes and custom operations. http://silverlight.net/getstarted/riaservices/Silverlight vs. Flash
Adobe Flash is the most popular competitor to Silverlight both supports browser plug-in and enables execution of rich content for the Web. Flash is not the new technology, which is already having long life span as compared to Silverlight. But it does not have huge community as expected; it may be cause of limited development tools, which are not kwon to most of the developers. Flash uses ActionScript as programming language and Flex as programming environment, which most of the developer are far from these technologies.
For ASP.NET developers to extend their websites using flash content is not so simples, they need to learning development environment as mentioned above like ActionScript and Flex, apart from that there is no way to generate Flash content using server-side .NET code, which means it’s difficult to integrate ASP.NET content and Flash content.
Silverlight aims to give .NET developers a better option for creating rich web content. Silverlight provides a browser plug-in with many similar features to Flash, but one that’s designed from the ground up for .NET. Silverlight natively supports the C# language and uses a range of .NET concepts. As a result, developers can write client-side code for Silverlight in the same language they use for server-side code (such as C# and VB), and use many of the same abstractions (including streams, controls, collections, generics, and LINQ).
S.No.
View the Original article
Categories: Programming Tags: anoop madhusudanan, briefly about c# and c# tools, c sharp compiler download, c# compilers, C# keywords classified, develop in c# in windows98, download C# compiler for windows xp, download different Types Of Compilers in C#, explain briefly about c# and c# tools, high volume wcf pollingduplex call, Introduction, multiform application in C#.Net, sample silverlight application imaging, scada silverlight, silverlight, silverlight 4.0 whiteboard, silverlight DataPointSeries Mouse Event, Silverlight DICOM, silverlight dragEnter, silverlight dragEnter dragOver dragLeave example, silverlight emf, silverlight scada wcf, silverlight toolkit "drag drop treeview", silverlight toolkit dragenter event, Silverlight WCF polling duplex white board, Silverlight4 tif, windows forum consumes silverlight duplex polling, www.silverlightconfiguration.net
