.Apple Technologies

RECOVER HIDDEN FILES AND FOLDERS OF PEN DRIVE USING CMD PROMPT

2016-01-22T00:58:00.002-08:00

Generally we will facing a big problem as hiding and not showing our files when we use our pen drives and memory cards in some other systems coz of virus problem
To remove such virus follow the steps

Open administrative command prompt.
Go to your pen-drive drive letter. Suppose your USB disk is G:. Type G: and press Enter
Now type the below command to remove system file, hidden read-only attribute
attrib -s -h -r /s /d *.*
Delete Autorun.inf from USB – Disk.
This makes all files visible and you are now able to delete them .
del *.lnk
Now to remove the shortcuts from pen-drive , Check the size of any One or Few Shortcuts, all be same.
Delete suspicious files, on errror check task manager for process with same name or any suspicious process and end it.
Open Explorer and right Click on Pen-drive , Click Open.
Search with Advance Search for all files of same size in Pen-drive.
Select All and Delete

jQuery interview Question - Part II

2015-05-12T23:33:00.002-07:00

Previous I already posted basic Interviews question in jQuery Basic Interview Question
Here some more for you

21. What is the difference between size and length of jQuery?

Size and length both returns the number of element in an object. But length is faster than the size because length is a property and size is a method.

22. Can we add more than one ‘document.ready’ function in a page?

Yes, we can add more than one document.ready function in a page. But, body.onload can be added once in a page.

23. What is the use of jQuery load method?

jQuery load method is a powerful AJAX method which is used to load the data from a server and assign the data into the element without loading the page.

24. Whether our own specific characters are used in place of $ in jQuery?

Yes, We can use our own variable in place of $ by suing the method called no Conflict ( ) method.

var sample = $.noConflict( )

25. What are the four parameters used for jQuery Ajax method?

The four parameters are

URL – Need to specify the URL to send the request
type – Specifies type of request(Get or Post)
data – Specifies data to be sent to server
Cache – Whether the browser should cache the requested page

26. What is the use of jQuery filter?

The jQuery filter is used to filter the certain values from the object list based on the criteria. Example is to filter certain products from the master list of products in a cart website.

27. Which program is useful for testing jQuery?

QUnit is used to test jQuery and it is very easy and efficient.

28. What is CDN?

CDN is abbreviated as Content Distribution network and it is said to be a group of companies in different location with network containing copies of data files to maximize bandwidth in accessing the data.

29. What are the two types of CDNs?

There are two types of CDNs:

Microsoft – Load jQuery from Ajax CDN
Google – Load jQuery from Google libraries API

30. Which sign is used as a shortcut for jQuery?

Dollar ($) sign is used as a shortcut for jQuery.

31. Is jQuery is a client or server scripting?

jQuery is a client scripting.

32. What is the script build up by jQuery?

jQuery is a Javascript file and it is single javascript file that contains common DOM, event effects and Ajax functions.

33. How can we debug jQuery?

There are two ways to debug jQuery:
Debugger keyword

Add the debugger to the line from where we have to start debugging and then run Visual Studio in Debug mode with F5 function key.
Insert a break point after attaching the process

34. What are all the ways to include jQuery in a page?

Following are the ways to include jQuery in a page:

Local copy inside script tag
Remote copy of jQuery.com
Remote copy of Ajax API
Local copy of script manager control
Embedded script using client script object

35. What is the use of jQuery.ajax method ()?

jQuery.ajax method is used for asynchronous HTTP requests.

36. Where can we download JQuery?

jQuery javascript can be downloaded from jQuery official website – www.jquery.com

37. Is jQuery is a replacement of JavaScript?

No, jQuery is not a replacement of JavaScript.

38. What is called chaining?

Chaining is used to connect multiple events and functions in a selector.

39. What are the advantages of jQuery?

Following are the advantages of jQuery:

Just a JavaScript enhancement
Coding is simple, clear, reusable
Removal of writing more complex conditions and loops

40. Whether C# code behind can be called from jQuery?

Yes, we can call C# code behind from jQuery.

41. What is the use of jQuery.data() method?

jQuery data method is used to associate data with DOM nodes and JavaScript objects. This method will make a code very concise and neat.

42. What is the difference between onload() and document.ready()?

In a page, we can have only one onload function but we can have more than one document.ready function. Document.ready function is called when DOM is loaded but onload function is called when DOM and images are loaded on the page.

43. What is the use of jQuery each function?

jQuery each function is used to loop through each and every element of the target jQuery object. It is also useful for multi element DOM, looping arrays and object properties.

44. How method can be called inside code behind using jQuery?

$.ajax can be called and by declaring WebMethod inside code behind using jQuery.

45. Which is the fastest selector in jQuery?

ID and Element are the fastest selectors in jQuery.

46. What is the slowest selector in jQuery?

Class selectors are the slowest selectors in jQuery.

47. Where jQuery code is getting executed?

jQuery code is getting executed on a client browser.

48. What is the method used to define the specific character in place of $ sign?

‘NoConflict’ method is used to reference a jQuery and save it in a variable. That variable can be used instead of Sign.

49. Why jQuery is better than JavaScript?

jQuery is a library used for developing Ajax application and it helps to write the code clean and concise. It also handles events, animation and Ajax support applications.

50. What are the types of selectors in jQuery?

There are three types of selectors in jQuery:

CSS Selector
XPath Selector
Custom Selector

jQuery Important Interview Questions

2015-03-28T07:32:00.002-07:00

1. What is jQuery?
jQuery is not a programming language but a well written JavaScript code. It is a JavaScript code, which do document traversing, event handling, Ajax interactions and Animations.

2. Why jQuery is needed?
jQuery is needed for the following list:

Used to develop browser compatible web applications
Improve the performance of an application
Very fast and extensible
UI related functions are written in minimal lines of codes

3. Whether jQuery HTML work for both HTML and XML documents?
No, jQuery HTML only works for HTML documents not for XML Documents.

4. What are the methods used to provide effects?
Some of the effects methods are:

Show( )
Hide( )
Toggle( )
FadeIn( ) and
FadeOut( )

5. What is the advantage of using minimized version of jQuery?
Efficiency of web page increases when minimized version of jQuery is used.min.js file will be more than 50% less than the normal js file. Reduction in the file size makes the web page faster.

6. Is jQuery is a JavaScript or JSON library file?
jQuery is a library of JavaScript file and it consists of DOM, event effects and the Ajax functions. jQuery is said to be a single JavaScript file.

7. Which operating system is more compatible with jQuery?
Mac, Windows and Linux are more compatible with the jQuery.

8. How can we include jQuery library in ASP.Net project?
Download the jQuery library from jQuery.com and include that reference in the asp.net page.

9. Which command will give a version of jQuery?
The command $.ui.version returns jQuery UI version.

10. In what scenarios jQuery can be used?
jQuery can be used in following scenarios:

Apply CSS static or dynamic
Calling functions on events
Manipulation purpose
Mainly for Animation effects

11. What is the difference between find and children methods?
Find method is used to find all levels down the DOM tree but children find single level down the DOM tree.

12. What is jQuery connect?
A ‘ jQuery connect’ is a plugin used to connect or bind a function with another function. Connect is used to execute function from any other function or plugin is executed.

13. How to use connect?
Connect can be used by downloading jQuery connect file from jQuery.com and then include that file in the HTML file. Use $.connect function to connect a function to another function.

14. What are the features of jQuery, has been used in web applications?
jQuery uses features like Sliding, File uploading and accordian in web applications.

15. What are the browser related issues for jQuery?
Browser compatibility of jQuery plugin is an issue and needs lot of time to fix it.

16. Whether we need to add jQuery file in both Master and Content page?
jQuery file should be added to the Master page and can use access from the content page directly without having any reference to it.

17. What are the basic selectors in jQuery?
Following are the basic selectors in jQuery:

Element ID
CSS Name
Tag Name
DOM hierarchy

18. Can we call C# code behind using jQuery?
Yes, we can call C# code from jQuery as it supports .net application.

19. What is the use jQuery.data method?
jQuery.data methods is used to associate the data with the DOM nodes and the objects. This data method makes the jQuery code clear and concise.

20. What is the use of each function in jQuery?
Each function is used to iterate each and every element of an object. It is used to loop DOM elements, arrays and the object properties.

Click here for More Interview Question

All the best

2014-12-10T09:13:00.003-08:00

My dear students, Friends and blog followers,

Thanx for ur support. I hope this blog can little bit help to your career.

I will share new technology and new concepts in a quick time.

This is a comma but not a fullstop.

Yours

Hanumantha Rao

Routing in MVC

2014-11-15T09:48:00.000-08:00

Routing within the ASP.NET MVC framework serves two main purposes:

It matches incoming requests that would not otherwise match a fi le on the file system and maps the requests to a controller action.
It constructs outgoing URLs that correspond to controller actions.

The preceding two items describe only what Routing does in the context of an ASP.NET MVC application.

NOTE:
One constant area of confusion about Routing is its relationship to ASP .NET MVC. In its pre-beta days, Routing was an integrated feature of ASP.NET MVC. However, the team saw that it would have a useful future as a fundamental
feature of ASP.NET that even Web Pages could build on, so it was extracted
into its own assembly and made part of the core ASP.NET framework. The
proper name for the feature is ASP.NET Routing, but everyone simply shortens
it to Routing.
Putting this feature into ASP.NET meant that it became a part of the .NET
Framework (and, by association, Windows). So, while new versions of
ASP.NET MVC ship often, Routing is constrained by the schedule of the larger
.NET Framework; hence, it hasn’t changed much over the years.
ASP.NET Web API is hostable outside of ASP.NET, which means it can’t use
ASP.NET Routing directly. Instead, it introduces a clone of the Routing code.
But when ASP.NET Web API is hosted on ASP.NET, it mirrors all the Web API
routes into the core ASP.NET Routing’s set of routes. Routing, as it applies to
ASP.NET Web API

Comparing Routing to URL Rewriting

To better understand Routing, many developers compare it to URL rewriting. After all, both approaches are useful in creating a separation between the incoming URL and what ends up handling the request. Additionally, both techniques can be used to create pretty URLs for Search Engine Optimization (SEO) purposes.
The key difference is that URL rewriting is focused on mapping one URL to another URL. For example, URL rewriting is often used for mapping old sets of URLs to a new set of URLs. Contrast that to Routing, which is focused on mapping a URL to a resource.
You might say that Routing embodies a resource-centric view of URLs. In this case, the URL represents a resource (not necessarily a page) on the Web. With ASP.NET Routing, this resource is a piece of code that executes when the incoming request matches the route. The route determines how the
request is dispatched based on the characteristics of the URL — it doesn’t rewrite the URL.
Another key difference is that Routing also helps generate URLs using the same mapping rules that it uses to match incoming URLs. URL rewriting applies only to incoming requests and does not help in generating the original URL.
Another way to look at it is that ASP.NET Routing is more like bidirectional URL rewriting.
However, this comparison falls short because ASP.NET Routing never actually rewrites your URL.
The request URL that the user makes in the browser is the same URL your application sees throughout the entire request life cycle.

Page development in Sharepoint

2014-10-04T01:01:00.004-07:00

Bydefault Sharepoint server has two types of pages. 1.Page(Wiki) 2.Web Part Page

1.Page: This is a normal wiki page. In this page we can add text, images, links, ..
2.Web Part Page : This is also a page but here we can't create any text. Only for adding webparts to the page.

We have another type of page is called Publishing page. This is the combination of both page and webpart. If we want to create publishing page means first we should show this option in page list like below.

SiteActions --> SiteSettings --> SiteActions --> ManageSiteFeatures --> SharePoint Server Publishing ----> Activate. Now you will find the option Publishing page.

==================================

Webpart Page
SiteActions --> MoreOptions --> Page ---> Web Part Page ---> Create -->
i.Name : SPDemoPage .... Check/uncheck :Overwrite if file already exists?

ii.Layout : Select a layout template to arrange Web Parts in zones on the page. Multiple Web Parts can be added to each zone. Specific zones allow Web Parts to be stacked in a horizontal or vertical direction, which is illustrated by differently colored Web Parts. If you do not add a Web Part to a zone, the zone collapses (unless it has a fixed width) and the other zones expand to fill unused space when you browse the Web Part Page.
Choose any one layout template.
Ex.Header, Footer , 3columns / Full page, Vertical / Header leftcol, body

iii.Save Location : Select the document library where you want the Web Part Page to be saved. choose any one of the following
SiteAssets / Shared Documents / SitePages

A new webpart page will be opened. now you can add webparts by click on Add a web part.
After adding webparts to the page then click on Stop Editing option. Now page is ready.
*While adding webparts you can also drag webparts from one place to another place.

Web part zone is like div tag in asp.net / html.
We can add / delete or move webparts from one place to another place.

Publishing Page

This page is the combination of wiki page and web part page. We have 5 types of publishing pages available. Those are
1.Articles
2.Wiki Page
3. Project
4. Redirect
5. Welcome

SiteActions --> MoreOptions --> Page ---> Publishing Page --> Create -->
1.Page Title and Description : Enter a URL name, title, and description for this page.

2.Page Layout : Select a page layout to control how the page will be displayed.
i.(Article page) body only: The article page with body only contains a rich text field.
ii.(Article page) Image on left : The article page with image on left contains an image field and a rich text field
iii.(Article page) Image on right :The article page with image on right contains an image field and a rich text field.
iv.(Article page) Summary Links : The article page with links contains an image field and summary links.

v.(Enterprise Wiki Page) Basic page:A basic page layout containing a single content area.

vi.(Project Page) Basic Project Page:A basic page layout containing a single content area.

vii.(Redirect Page)Redirect : This page layout contains a redirect control for automatically directing readers to any specified URL.

viii.(Welcome Page) Blank Web part page: Page layout for creating web part pages
ix.(Welcome Page)Splash : The welcome with splash contains an image field on left, a rich text field and Web Part zones arranged in a header, and 2 columns. The left navigation pane is hidden.
x.(Welcome Page) Summary Links :The welcome page with summary links contains an image field on left, a rich text field, 2 summary links, and Web Part zones arranged in a header, a footer, and 2 columns.
xi.(Welcome Page) Table of contents: The welcome page with table of contents contains an image field on left, a rich text field, a table of contents Web Part, and Web Part zones arranged in a header, a footer, and 2 columns.

Click on Create.
Now you can add text, images ..... after completion of creating Save the page then click on Publish --> Publish ---> Enter any comments if ... Continue click

While you are developing the publishing page its status is 'Checked out' Means it is under design. So no one cant access this page.

Like you can create all publish pages of enterprisewiki, basic project page, redirect page and welcome page.

============================================================

Sharepoint Realtime Interview questions

2014-09-23T09:23:00.001-07:00

Important interview questions for Sharepoint Developer
Q. How will you deploy files such as Css, js in SharePoint 2010?
Ans. The most preferable way to deploy files in SharePoint is by using the solution package. In SharePoint 2010 you can create an empty project with VS 2010 and then add a new SharePoint Mapped folder in it. This will give the desired location in 14 hive where you can then add a file to deploy.

Q. Can you display a page as a modal dialog?
Ans. Yes, any page can be displayed as modal dialog. A Modal dialog takes options as a parameter and we can speciy the url for any page usually saved in _layouts.

Q. Can you display the modal dialog from a webpart?
Ans. Yes a modal dialog can be displayed from within a webpart code since its a JavaScript block that can be registered on the page.

Q. What is difference between an Application page and a Custom aspx page in SharePoint 2010. If you have to deploy a page with some code in it which one would you prefer?
Ans.
Application Page – You would typically use an applictaion page when you need some content that is merged with SharePoint master page. A master page enables application pages to share the same appearance and behavior as other pages on a site. Application page generally gets deployed in _layouts and inhertirs the look and feel of the site that you are using.
A Custom .net aspx page on the other hand would need content and master page tags in your page to make it inherit the look and feel of the site.
I would prefer deploying an application page with code as it is much easier and has built-in templates available in VS 2010.

Q. What is Docuement Set and how is it useful to the end users?
Ans. A Document Set is a group of related documents that can be created in one step and then managed as a single entity. This can be seen as a folder of documents with a cover letter(welcome page) and which can share common data between its documents (share document set info\columns).
Document Set is very useful when it comes to managing the documents for a single project or task. For e.g. a manager while working on a project wants to create a single folder\entity with all the documents related to that project. He also wants that each document shares the project info (for e.g. Project Id, Manager name etc.) and can be checked in\checked out individually. Document Set will also allow him to add a cover letter\welcome page to the entity(or his set of documents) and use some basic document features like record version history, start a workflow, e-mail document set etc.

Q. What are Projected Fields in SPQuery and when would you use that?
Ans. In SharePoint 2010, Referential integrity can now be implemented using Lookup columns. Joins and ProjectedFields properties of SPQuery were introduced to facilitate this. Projected Fields are the fields which you can access when a list is joined by a lookup columns. These are additional columns from a parent lookup column list.

Q. What is WebProvisioned event receiver and when would you use that?
Ans. WebProvisioned event receiver is fired after the site has been created and is fully provisioned(asynchronous). For e.g. if you want to update the site title of logo after its been created or if you want to add a new list\library after the out-of-box site has been created you can use the WebProvisioned event handler.

Q. If you have to add a new Ribbon button to one of the existing tabs how will you identify the location?
Ans. The Its typically Ribbon.Tabs.group.Controls._children.

Q. How does Client object model works ?
Ans. When we use SharePoint client API’s to perform a specific task, the SharePoint Foundation 2010 managed client object model bundles up these uses of the API into XML and sends it to the server that runs SharePoint Foundation. The server receives this request, and makes appropriate calls into the object model on the server, collects the responses, forms them into JavaScript Object Notation (JSON), and sends that JSON back to the SharePoint Foundation 2010 managed client object model. The client object model parses the JSON and presents the results to the application as .NET Framework objects (or ECMAScript objects for ECMAScript).

Q. How many types of Client Object model extension are available in 2010 and when would you use one or the other.
Ans. To develop rich client side solutions, three set of client-side APIs has been introduced in the Microsoft.SharePoint.Client namespace. The three APIs are targeted for three different types of clients.
1. .net Managed applications – These are used when we have to create console applications or window applications, web applications which are not running inside SharePoint Contex.
2. For Silverlight applications
3. ECMAScript – It is a client object model extension for using with JavaScript or JScript. This is used for creating applications which are hosted inside SharePoint. For example, web part deployed in SharePoint site can use this JavaScript API for accessing SharePoint from browser using JavaScript.

Q. What is difference between Load() and LoadQuery() methods ?
Ans. Load method populates the client object directly with what it gets data from the server i.e. a collection object like ListItemCollection etc. but LoadQuery returns the data as a completely new collection in IEnumerable format. Other major difference is that the Collections that you load using the Load() method are eligible for garbage collection only when the client context variable itself goes out of scope where as, in these collections go out of scope at the end of IEnumerable<List>list.

Q. How can you write efficient and better performing client object applications ?
Ans. You can always use Lambda expressions in your queries to return only specific properties that will be used in your block. You can also use LoadQuery() method and specify multiple levels of properties to load for e.g. while returning specific properties of the lists using LoadQuery(), you can also specify the fields to return from each list to optimize the data access.

Q. How do you access ECMAScript object model API’s ?
Ans. The ECMAScript library is available in a number of JS files in the LAYOUTS folder. The main file among number of .js files is SP.js. When you include this file in the APSX page using a ScriptLink control, all other required JS files are loaded automatically. By linking SP.js to your page, the SP namespace gets registered. SP is the SharePoint namespace that contains all objects. For debugging purposes every js file also has a ‘debug’ equivalent in the same folder.

Q. What is the purpose of calling clientContext.ExecuteQuery() ?
Ans. ExecuteQuery gives you the option to minimize the number of roundtrips to the server from your client code. All the components loaded into the clientcontext are executed in one go.

New Article

2014-08-25T10:41:00.002-07:00

SharePoint 2013

2014-08-22T02:19:00.003-07:00

Welcome to the world of SharePoint 2013. SharePoint 2013 Production version is released & Live implementations are going on. In this article I would like to re-iterate the features of SharePoint as a whole & advantages of going with it.

Sharepoint Features
Depending on the business perspective the features of SharePoint are many:

How to Install SharePoint 2013?

As SharePoint is a server side software, it requires the Windows Server operating system. You can start with a new installation or use a Virtual Machine. Once you have the Operating System ready, you can download and install SharePoint 2013 from the following link: http://technet.microsoft.com/en-us/evalcenter/hh973397.aspx .

Hardware Requirements

Following are the core hardware requirements:

CPU 64-bit
RAM 8 GB
HDD 80 GB

Software Requirements

Following are the software requirements:

Windows Server 2012
Microsoft SQL Server 2012 64-bit
Internet Information Services 7.5
Microsoft .NET 4.5

Routing MVC 4

2014-07-18T12:42:00.002-07:00

Routing

· All ASP.NET MVC traffic starts out like any other website traffic: with a request to a URL. This means that, despite the fact that it is not mentioned anywhere in the name, the ASP.NET Routing framework is at the core of every ASP.NET MVC request.

· In simple terms, ASP.NET routing is just a pattern-matching system. At startup, the application registers one or more patterns with the framework’s route table to tell the routing system what to do with any requests that match those patterns.

· When the routing engine receives a request at runtime, it matches that request’s URL against the URL patterns registered with it (Figure 1-6).

· When the routing engine finds a matching pattern in its route table, it forwards the request to the appropriate handler for that request.

Otherwise, when the request’s URL does not match any of the registered route patterns, the routing engine indicates that it could not figure out how to handle the request by returning a 404 HTTP status code.

Configuring Routes

ASP.NET MVC routes are responsible for determining which controller method (otherwise known as a controller action) to execute for a given URL. They consist of the following properties:

Unique name : A name may be used as a specific reference to a given route

URL pattern : A simple pattern syntax that parses matching URLs into meaningful

segments

Figure 1-6. ASP.NET routing

Defaults : An optional set of default values for the segments defined in the URL pattern Constraints

A set of constraints to apply against the URL pattern to more narrowly define the URLs that it matches

The default ASP.NET MVC project templates add a generic route that uses the following URL convention to break the URL for a given request into three named segments, wrapped with brackets ({}):

“controller”, “action”, and “id”: {controller}/{action}/{id} This route pattern is registered via a call to the MapRoute() extension method that runs during application startup (located in App_Start/RouteConfig.cs):

routes.MapRoute(

"Default", // Route name

"{controller}/{action}/{id}", // URL with parameters

new { controller = "Home", action = "Index",

id = UrlParameter.Optional } // Parameter defaults

);

In addition to providing a name and URL pattern, this route also defines a set of default parameters to be used in the event that the URL fits the route pattern, but doesn’t actually provide values for every segment.

For instance, Table 1-1 contains a list of URLs that match this route pattern, along with corresponding values that the routing framework will provide for each of them.

Table 1-1. Values provided for URLs that match our route pattern

URL Controller Action ID

/auctions/auction/1234 AuctionsController Auction 1234

/auctions/recent AuctionsController Recent

/auctions AuctionsController Index

/ HomeController Index

· The first URL (/auctions/auction/1234) in the table is a perfect match because it satisfies every segment of the route pattern, but as you continue down the list and remove segments from the end of the URL, you begin to see defaults filling in for values that are not provided by the URL.

· This is a very important example of how ASP.NET MVC leverages the concept of convention over configuration: when the application starts up, ASP.NET MVC discovers all of the application’s controllers by searching through the available assemblies for classes that implement the System.Web.Mvc.IController interface (or derive from a class that implements this interface, such as System.Web.Mvc.Controller) and whose class names end with the suffix Controller.

· When the routing framework uses this list to figure out which controllers it has access to, it chops off the Controller suffix from all of the controller class names.

· So, whenever you need to refer to a controller, you do so by its shortened name, e.g., AuctionsController is referred to as Auctions, and Home Controller becomes Home.

· What’s more, the controller and action values in a route are not case-sensitive. This means that each of these requests—/Auctions/Recent, /auctions/Recent, /auctions/recent, or even /aucTionS/rEceNt—will successfully resolve to the Recent action in the AuctionsController.

· Note: URL route patterns are relative to the application root, so they do not need to start with a forward slash (/) or a virtual path designator (~/).

· Route patterns that include these characters are invalid and will cause the routing system to throw an exception.

· As you may have noticed, URL routes can contain a wealth of information that the routing engine is able to extract.

· In order to process an ASP.NET MVC request, however, the routing engine must be able to determine two crucial pieces of information: the controller and the action.

· The routing engine can then pass these values to the ASP.NET MVC runtime to create and execute the specified action of the appropriate controller.

Modifying our first MVC 4 Web Application

2014-07-15T11:30:00.004-07:00

Apart from the generated code I’m just going to add some more pieces to this MVC Web Application. I will be publishing a full fledge ePhoneBook on ASP.NET MVC 4 later. This sample code will help you to get more understanding on MVC 4.

The first thing I’m going to do is adding a PhoneBook Model class .

I have changed the PhoneBookModel code as below,

In this class I have mentioned the validation attribute for the elements. The ValidationAttributes are comes fromSystem.ComponentModel.DataAnnotations. There are multiple validation attributes available and all are self-descriptive.

The above image shows the available validation attributes. Read More on Validation Attribute from MSDN.

Now let’s add required views (Create, Edit, Delete, Details, List), to add the views just right click on the View folder and click on Add --> Views menu.

Now I’m going to add the Listing view, I have given the View Name as “Index” and selected the 'create a strongly typed view' Model from the Drop-down so that the code will be generated accordingly to the Model. If the created PhoneBookModel is not showing in the dropdown then build the application and then check.

Now we can specify which scaffolding template to use so that the code will be generated as per the template , I have selected “List” template like below

When you click on ‘OK’ button the Index.cshtml is ready.

The same way I have added all files for this sample project

The details page looks like

If you look at the code from Create template all validations are in place

Now we need to add Controller actions for these scaffolding items.

Click on the Add --->Controller menu, once you have clicked on that menu then a popup will be shown like below ,

There are multiple controller templates available in this dialogue box

Empty MVC controller

MVC controller with read/write actions and views, using Entity Framework

MVC controller with empty read/write actions

Empty API controller

API controller with read/write actions and views, using Entity Framework

API controller with empty read/write actions

I choosed “MVC controller with empty read/write actions” controller template Now give the controller name as PhoneBookController. Note that MVC requires the name of all controllers to end with "Controller".

Click on “Add” button to add the controller to our application, now the controller file is created as per our template selection and added to our project, click here to see the generated file

Now I’m going to modify the newly added controller file, the first thing I have added a property that will have a default values for the ePhoneBook

After that I have modified the Created method same as below,

If you see this method the return type is ActionResult, What’’s ActionResult. An action result represents a command that the framework will perform on behalf of the action method. The ActionResult class is the base class for action results. It Encapsulates the result of an action method and is used to perform a framework-level operation on behalf of the action method.

ContentResult
EmptyResult
FileResult

FileContentResult
FilePathResult
FileStreamResult

HttpUnauthorizedResult

HttpUnauthorizedResult
HttpNotFoundResult

JavaScriptResult
JsonResult
RedirectResult
RedirectToRouteResult
ViewResultBase
PartialViewResult
ViewResult

Running Our First MVC 4 Application

2014-07-15T11:29:00.002-07:00

Now we will run our newly created ePhoneBook application. We can run this in debug mode or without debug. To run this go to the Menu Debug -->Start Debugging/Start without debugging.

You can also use the shortcut key F5 / Ctrl + F5 to run this application

The run command is also there in the Standard Toolbar, the below given image shows the run toolbar in VS 2012 IDE.

The below given image shows the run command in standard toolbar of VS 2010

Once you have run the application you can see the below Home page

If you want to debug your application then you need to set a break-point at the location where you want to hit the debugger.

To set breakpoints just go to the menu Debug -->Toggle Breakpoint.

You can use the shortcut key F9 also for the same. you might want to note the short keys for Step Into (F11) and Step Over (F10). Once you hit the breakpoint you can resume debugging by pressing F5.

To demonstrate the debugging I have placed two breakpoints, one in Home Controller – About() and About.cshtml. When I clicked on About Menu the first break point got hit.

You can Step Over by F10 or just resume to the next breakpoint by F5. I pressed F5 and the second breakpoint got hit.

If you want see the value then you can see in watch window and also there are other windows too, to add a object to Watch Window, select the required object and right click and click on AddWatch.

Once you have placed the object in Watch window you can see the current value in that window

If you resume your breakpoints you can see the About page in action,

Have you noticed that the url is very user friendly with no extensions and all. The ASP.NET MVC routing takes care of this URL routing. Read more on routing on MSDN.

To stop debugging you need to press Shift + F5 or go to the Debug menu and click on Stop Debugging.

Stopping Debugging from the standard toolbar

If you want to make any changes while debugging then you can edit and continue the application, if that option is enabled. to check this option is enabled or not, go to Tools->Options then

In ASP.MVC, Layout is used to give similar look and feel for the entire application this was called master page in ASP.NET Web forms. Below given the Layout page in our application,

You can see that the Menus like Home, About Contact was shown from this Layout. So how this page is called? So where the content page is placed, it’s simple, the `@RenderBody` mentioned that the content page will be displayed in that area.

This Layout can be mentioned in individual views or in `_viewstart` file. The ViewStart file called the Layout in below syntax,

While debugging our application we have noticed something named ViewBag. It's a dynamic data dictionary.

As we have used Internet Application Project template the code is generated with Membership management. Let’s have a look into that.

Now I’m going to create a User named Shemeer using the Register link.

If you want you can place a breakpoint on AccountController’s register action. When I click ‘Register’ Button it reaches the `WebSecurity.CreateUserAndAccount()`.

This method saves my credential to the `aspnet*` database. Wondering J this database was created automatically as part of memebership management and this database by default resides under the `App_Data` folder.

And the connection string has been created inside the web.config also

Now I'm trying to login using the Login page

I’m able to login and my user name is showing in right top corner as logged in

MVC -4 View Engine

2014-07-15T11:28:00.000-07:00

What's a View Engine?

View Engine are responsible for rendering the HTML from your views to the browser. The view engine template will have different syntax for implementation. Currently there are few number of view engines available for MVC and the top four view engines are Razor, traditional ASPX, Spark and NHaml. I have written another article on comparison of different view engines.

Razor is the preferred View Engine for MVC, ASPX View Engine is the legacy View Engine and this option is there for backward compatibility.

I will be explaining more about Razor on another article.

Once you click 'OK' after selecting the appropriate project template Visual Studio will create a MVC Web Application project with default files and folders as per the Template Selection.

If look at the visual studio status bar you can see that the project creation progress and the files adding to the project. ASP.NET MVC 4 project template is using Nuget Package Manager to install and manage the assembly references in your application. the below files in status bar adding by Nuget.

Package.Config File contains the list of the Nuget Package used in this project.

Now Visual Studio created our project in place and the solution file looks like ,

I have explained the Project Items/ Application folder structure in another article, before continuing with our newly created project I just wanted to explain the Project Templates.

Project Templates

Currently MVC 4 Application in Visual Studio 2010 and Visual Studio 2012 offers 6 different types of project templates. (Previously it was 7 but the final version of MVC 4 doesn't shipped with ASP.NET Single Page Application due to some compatibility)

I will be explaining the Basic, Empty, Internet Application, Intranet Application, Mobile Application and Web API project templates here.

Empty

The Empty template created the minimum references and resources required to run an Asp.net MVC application.As you can see in below image, Models, Controllers, App_Data are completely empty folders and View folder only contains web.config and a Global.asax file and web.config.App_Start folder contains 3 configuration files ( FilterConfig.cs, RouteConfige.cs and WebApiConfig.cs ).

This option will be good if you plan to create everything from scratch.

Basic

After comparing the Empty project image and Basic project image we can say that The Basic template is somewhat similar to Empty template. In addition to the Empty project , Content , Script folder are present in this template and Shared folder is present inside Views and also in App_Start folder apart from the three files in empty template, basic template added one more file named BundleConfig.cs (Bundling and minimization).

Same like Empty Template,this option also good if you plan to create everything from scratch.

Internet Application

The Internet Application extends Basic Template with two controllers( Account controller and Home controller) with all the logic and functionality implemented in actions and views. In this template membership management functionality gives the option to user to register and login, change password etc in the website.

It's a template used usually to start a normal web project in action.

Intranet Application

The Intranet Application template is same like the Internet Application template, except that it is preconfigured to use Windows-based authentication.

This template will be a good option if you plan to create an intranet web site.

Mobile Application

The Mobile Application template is another variation of the Internet Application template. This template, however, is optimized for mobile devices and includes the jQuery Mobile JavaScript framework and views that apply the HTML that works best with jQuery Mobile.

If you plan to target touch based mobile devices then this template is the right option.

Web API

The Web API template is yet another variation of the Internet Application template that includes a preconfigured Web API controller.ASP.NET Web API is a framework that makes it easy to build HTTP services that reach a broad range of clients, including browsers and mobile devices. ASP.NET Web API is an ideal platform for building RESTful applications on the .NET Framework.

Web API is a great choice for quickly and easily creating data services that your AJAX-enabled applications can easily consume.

If we want to create a Test project while creating the MVC project itself then we need to mark the Create Unit Test Project Check box. If you don't want to do this at the first time you can add a unit test project later also.

If we are creating MVC Application with Test project then the solution explorer will look like below .

Creating MVC 4 Application

2014-07-15T11:25:00.001-07:00

Creating an ASP.NET MVC Application – myPhoneBook

In this article all screen shots are based out of Visual Studio 2012 but If you are using Visual Studio 2010 then you will find similar UIs there too.To Create a new MVC 4 application we need to click on 'New Project' menu. 'New Project' menu can be accessed from the start page itself or File --> New --> Project menu.

The below given image shows how to create a New Project from start page.

Creating New Project from File -->New -->Project.

Clicking on New Project menu will show a popup for selecting the required type of Project from the installed templates list. We can create Windows Application or normal ASP.NET Web Application etc using this popup but now we are more interested to create a new ASP.NET MVC 4 Web Application from scratch.

Give a proper name for this new MVC 4 application and click 'OK' button. I have given 'ePhoneBook' name as I'm going to use this project for all my MVC 4 series.

When you click 'OK', you’ll be presented with another dialog with Project Templates

Select appropriate Project Template (discussed in another section), View Engine and also if you want you can opt for creating a Test Project for this application. You can create a test project later also if you don't want to do right now. I have selected the Internet Application with Razor View Engine.

MVC 4 Introduction

2014-07-15T11:23:00.001-07:00

Introduction

ASP.NET MVC 4 is a framework for building scalable, standards-based web applicationsusing well-established design patterns and the power of ASP.NET and the .NET Framework.
In this article I will give an introduction to ASP.NET MVC 4 from a beginner’s perspective.
This article is meant for all kind of beginner users who wanted to get started with ASP.NET MVC 4.
I have included a small comparison between ASP.NET MVC and ASP.NET Web forms for those who have already explored ASP.NET Web forms
Currently ASP.NET MVC 4 is supported in Visual Studio 2010 and Visual Studio 2012, previous versions of Visual Studio does not support ASP.NET MVC 4 as of now.
If you don’t have ASP.NET MVC 4 in your box then install MVC 4 for Visual Studio 2010 or else use Visual Studio 2012 to get started with this article .

What is ASP.NET MVC?

ASP.NET supports three different development models named Web Pages, MVC and Web Forms.

ASP.NET MVC is a web application development framework built on top of Microsoft’s .NET Framework. ASP.NET Web Form was a replacement for Microsoft’s Active Server Pages (ASP) but ASP.NET MVC is not a replacement for ASP.NET Web Forms and it’s just an alternate way of making an ASP.NET website.

ASP.NET MVC is open source!- In March 2012, Scott Guthrie announced on his blog that Microsoft had released part of their web stack (including ASP.NET MVC, Razor and Web API) under an open source license (Apache License 2.0).

Download from Codeplex.com

Why MVC?

ASP.NET MVC helps to reduce the complexity of the web application by dividing an application into three layers, Model, View and Controller. This separation (loose coupling) helps in some long term benefits like isolation of components while development and also this separation provides better support for test-driven development (TDD). ASP.NET MVCweb site are good in performance and also easy to maintain.

MVC Release History

The Current Version of ASP.NET MVC is 4 and it was released on 15^th Aug 2012. ASP.NET MVC 4 is packaged with Visual Studio 2012 and MVC 4 can be installed for Visual Studio 2010. Below I have mentioned the release history of ASP.NET MVC.

DATE	VERSION
10 Dec 07	ASP.NET MVC CTP
13 Mar 09	ASP.NET MVC 1.0
16 Dec 09	ASP.NET MVC 2 RC
04 Feb 10	ASP.NET MVC 2 RC 2
10 Mar 10	ASP.NET MVC 2
06 Oct 10	ASP.NET MVC 3 Beta
09 Nov 10	ASP.NET MVC 3 RC
10 Dec 10	ASP.NET MVC 3 RC 2
13 Jan 11	ASP.NET MVC 3
20 Sep 11	ASP.NET MVC 4 Developers Preview
15 Feb 12	ASP.NET MVC 4 Beta
31 May 12	ASP.NET MVC 4 RC
15 AUG 12	ASP.NET MVC 4

In this article we are discussing more about the latest version of MVC, that's MVC 4. Read more from Wikipedia onMVC Release History.

MVC Architecture

The Model-View-Controller (MVC) pattern is an architectural design principle that separates the application components of a Web application into three layers. This separation gives you more control over the individual parts of the application, which lets you more easily develop, modify, and test them.

The Model

Model contains and exposes the properties and application logic In a better way we can say that The model represents core business logic and data. In the ePhoneBook Sample the 'PhoneBookModel' class represents the properties of a “Phone Book” in the application and may expose properties such as First Name, Last Name and Mobile Number etc and also it may expose methods.

The View

The View is responsible for creating the response HTML or any responses back to the browser like pdf, html or excel etc. In other way we can sat that the view is responsible for transforming a model or models into a visual representation.

The Controller

Controller is responsible for processing user inputs from view and give responses back to the view. It means that the controller decides the action and performs the tasks/logic based on the parameters.Controller acts as the coordinator between the view and the model.

Comparing ASP.NET MVC with ASP.NET Web Forms

If you have already worked with ASP.NET Web forms then you might be interested to see some comparisons between these two.
The main thing is that both ASP.NET Web form and ASP.NET MVC are built on top of ASP.NET Framework.
There are some similarities and differences between these two.
ASP.NET Web forms web development is very easy compared to ASP.NET MVC apps. and Web forms doesn't require a developer to be an expert in JavaScript and HTML to write a web application but ASP.NET MVC is full of scripting technologies and it requires a good command over scripting technologies.
ASP.NET Web form is very rich with server controls but in ASP.NET MVC there are no server controls supported and its fully depend on HTML controls. If you look at the below image you can see that no server controls are present in the toolbox.

There is no View State in ASP.NET MVC. we can use HtmlHelpers in ASP.NET MVC for rendering HTML controls in a view.
ASP.NET MVC is based on Separation Of Concerns that's why ASP.NET MVC is pluggable and flexible system.
Implementing Test projects with ASP.NET MVC is simple than Web forms.
ASP.NET MVC request cycle is very simpler than Web forms and MVC gives a good performance.
In my opinion I feel for a Web form developer, ASP.NET MVC is difficult to learn and understand as its much into coding not much drag and drop but once its fully understood then its very easy.
Layout page is the Master page available in ASP.NET MVC and partial views can be considered as a replacement of user control in Web form.
Web form uses normal Web-form syntax where as MVC app uses customizable syntax default to Razor.
There are many more similarities and differences, Once you start writing code with ASP.NET MVC you will learn more.

Creating a New ASP.NET MVC Project

2014-06-03T00:41:00.001-07:00

We are going to start by creating a new MVC project in Visual Studio. Select New Project from the File menu to open the New Project dialog. If you select the Web templates, you’ll see that the MVC 3 installer has created a new item called ASP.NET MVC 3 Web Application, as shown in Figure 1

Set the name of the new project to PartyInvites and click the OK button to continue. You will see another dialog box, shown in Figure 2, which asks you to choose between three different types of MVC project templates.

The Empty option creates a project with only the minimum files and folders required for an MVC 3 application. The Internet Application option creates a small example application that you can modify and build on. It includes user registration and authentication, navigation, and a consistent visual style.
The Intranet Application option is similar to Internet Application, but is designed for use in environments that authenticate users through a domain/Active Directory infrastructure. For this chapter, we are going to keep things simple. Select the Empty option, leave the Use HTML5 semantic
markup option unchecked, and click OK to create the new project.
Once Visual Studio creates the project, you’ll see a number of files and folders displayed in the Solution Explorer window. This is the default structure for an MVC 3 project. You can try to run the application now by selecting Start Debugging from the Debug menu (if it prompts you to enable debugging, just click the OK button). You can see the result in Figure 3-3. Since we started with the empty project template, the application doesn’t contain anything to run, so we see a 404 Not Found Error.

When you’re finished, be sure to stop debugging by closing the browser window that shows the error, or by going back to Visual Studio and selecting Stop Debugging from the Debug menu.

Adding the First Controller

In MVC architecture, incoming requests are handled by controllers. In ASP.NET MVC, controllers are just simple C# classes (usually inheriting from system.Web.Mvc.Controller, the framework’s built-in controller base class). Each public method in a controller is known as an action method, meaning you
can invoke it from the Web via some URL to perform an action. The MVC convention is to put controllers in a folder called Controllers, which Visual Studio created for us when it set up the project.
You don’t need to follow this or most other MVC conventions, but we recommend that you do—not least because it will help you make sense of the examples in this book.
To add a controller to our project, right-click the Controllers folder in the Visual Studio Solution Explorer window and choose Add and then Controller from the pop-up menus, as shown in Figure -4.

When the Add Controller dialog appears, set the name to HomeController, as shown in Figure 3-5.
This is another convention: the names we give to controllers should be descriptive and end with Controller.

The Scaffolding options section of the dialog allows us to create a controller using a template with common functions. We aren’t going to use this feature, so ensure that the Empty controller item is selected in the Template menu, as shown in the figure.
Click the Add button to create the controller. Visual Studio will create a new C# code file in the Controller folder called HomeController.cs and open it for editing. You can see that the class is called HomeController and it is derived from System.Web.Mvc.Controller. Edit the code in this file so that it matches Listing -1.

Listing -1. Modifying the HomeController Class

using System.Web.Mvc;
namespace PartyInvites.Controllers {
public class HomeController : Controller {
public string Index() {
return "Hello, world";
}
}
}

We haven’t created anything exciting, but this is a good way of getting started with MVC. We’ve created an action method called Index, which returns the string “Hello, world”. Run the project again by selecting Start Debugging from the Visual Studio Debug menu. The browser will display the result of the
Index action method, as shown in Figure -6.

Who Should Use ASP.NET MVC?

2014-06-03T00:19:00.002-07:00

As with any new technology, the fact of ASP.NET MVC’s existence isn’t a compelling reason to adopt it.
Here, we’ll give you our view of how the MVC Framework compares with the most obvious alternatives.
We’ve tried to be as unbiased as two people writing a book about the MVC Framework can be, but we know that there is a limit to our objectivity. The following sections are technology-based comparisons.
When selecting a web application framework, you should also consider the skills of your team, the work involved in porting any existing projects, and your relationship with, and confidence in, the technology source.

Comparisons with ASP.NET Web Forms
We have already detailed the weaknesses and limitations in traditional ASP.NET Web Forms, and how ASP.NET MVC overcomes many of those problems. That doesn’t mean that Web Forms is dead, though.
Microsoft has repeatedly stated that both technologies are being actively developed and actively supported, and that there are no plans to retire Web Forms. In some ways, your choice between the two is a matter of development philosophy.

Consider these points:

Web Forms takes the view that UIs should be stateful, and to that end, adds a sophisticated abstraction layer on top of HTTP and HTML, using View State and postbacks to create the effect of statefulness.
This makes it suitable for drag-anddrop Windows Forms–style development, in which you pull UI widgets onto a canvas and fill in code for their event handlers.
MVC embraces HTTP’s true stateless nature, working with it rather than fighting against it.
The MVC Framework requires you to understand how web applications actually work.
Given that understanding, it provides a simple, powerful, modern approach to writing web applications, with tidy code that’s easier to extend and maintain over time, and that’s free of bizarre complications and painful limitations.
There are certainly cases where Web Forms is at least as good as, and probably better than, MVC.
The obvious example is small, intranet-type applications that are largely about binding grids directly to database tables or stepping users through a wizard.
Web Forms drag-and-drop development strengths can outweigh its weaknesses when you don’t need to worry about bandwidth consumption or search engine optimization.
If, on the other hand, you are writing applications for the Internet or larger intranet applications, you will be attracted by the bandwidth efficiency, better browser compatibility, and better support for automated testing that MVC offers.

Creating Excel file in C#

2014-05-17T21:56:00.001-07:00

The following section explains how to create an Excel file programmatically using C#. Before you create an Excel file in C# , you have to add the Microsoft Excel 12.0 Object Library to you project.
Create a new project and add a Command Button to the Form. Form the following pictures you can find how to add Excel reference library in your project. Select reference dialogue from Project menu Select Microsoft Excel 12.0 Object Library and click OK button

Copy and paste the following source code in your C# project file.

using System;
using System.Windows.Forms;
using Excel = Microsoft.Office.Interop.Excel;

namespace WinFormsExcelDemo
{
public partial class Form1 : Form
{
public Form1()
{
InitializeComponent();
}

private void button1_Click(object sender, EventArgs e)
{
if (textBox1.Text == "")
{
MessageBox.Show("Please Give a name for Excel");
textBox1.Focus();
}
else
{
Excel.Application xlapp;
Excel.Workbook xlworkbook;
Excel.Worksheet xlworksheet;
object misvalue = System.Reflection.Missing.Value;
//xlapp = new Excel.ApplicationClass();
xlapp = new Excel.Application();
xlworkbook = xlapp.Workbooks.Add(misvalue);
xlworksheet = (Excel.Worksheet)xlworkbook.Worksheets.get_Item(1);
xlworksheet.Cells[1, 1] = " New Work sheet";
xlworkbook.SaveAs(textBox1.Text + ".xls", Excel.XlFileFormat.xlWorkbookNormal, misvalue, misvalue, misvalue, misvalue,
Excel.XlSaveAsAccessMode.xlExclusive, misvalue, misvalue, misvalue, misvalue, misvalue);
xlworkbook.Close(true, misvalue, misvalue);
xlapp.Quit();
releaseObject(xlworksheet);
releaseObject(xlworkbook);
releaseObject(xlapp);
MessageBox.Show("Excel file created , you can find the file in Documents");
}
}
private void releaseObject(object obj)
{
try
{
System.Runtime.InteropServices.Marshal.ReleaseComObject(obj);
obj = null;
}
catch (Exception ex)
{
obj = null;
MessageBox.Show("Exception occured while releasing object"+ex.ToString());
}
finally
{
GC.Collect();
}
}

Note : You have to add Microsoft.Office.Interop.Excel to your source code.
using Excel = Microsoft.Office.Interop.Excel;
When you execute this program , it will create an excel file in you c:\Documents

ASP.NET MVC - Internet Application

2014-04-02T01:30:00.001-07:00

To learn ASP.NET MVC, we will Build an Internet Application

Part I: Creating the Application

What We Will Build

We will build an Internet application that supports adding, editing, deleting, and listing of information stored in a database.

What We Will Do

Visual Web Developer offers different templates for building web applications.

We will use Visual Web Developer to create an empty MVC Internet application with HTML5 markup.

When the empty Internet application is created, we will gradually add code to the application until it is fully finished. We will use C# as the programming language, and the newest Razor server code markup.

Along the way we will explain the content, the code, and all the components of the application.

Creating the Web Application

If you have Visual Web Developer installed, start Visual Web Developer and select New Project. Otherwise just read and learn.

In the New Project dialog box:

Open the Visual C# templates
Select the template ASP.NET MVC 3 Web Application
Set the project name to MvcDemo
Set the disk location to something like c:\w3schools_demo
Click OK

When the New Project Dialog Box opens:

Select the Internet Application template
Select the Razor Engine
Select HTML5 Markup
Click OK

Visual Studio Express will create a project much like this:

We will explore the content of the files and folders in the next chapter of this tutorial.

ASP.NET MVC Introduction

2014-04-02T01:26:00.004-07:00

The MVC Programming Model

MVC is one of three ASP.NET programming models.

MVC is a framework for building web applications using a MVC (Model View Controller) design:

The Model represents the application core (for instance a list of database records).
The View displays the data (the database records).
The Controller handles the input (to the database records).

The MVC model also provides full control over HTML, CSS, and JavaScript.

The MVC model defines web
applications with 3 logic layers:

The business layer (Model logic)

The display layer (View logic)

The input control (Controller logic)

The Model is the part of the application that handles the logic for the application data.
Often model objects retrieve data (and store data) from a database.

The View is the parts of the application that handles the display of the data.
Most often the views are created from the model data.

The Controller is the part of the application that handles user interaction.
Typically controllers read data from a view, control user input, and send input data to the model.

The MVC separation helps you manage complex applications, because you can focus on one aspect a time. For example, you can focus on the view without depending on the business logic. It also makes it easier to test an application.

The MVC separation also simplifies group development. Different developers can work on the view, the controller logic, and the business logic in parallel.

Web Forms vs MVC

The MVC programming model is a lighter alternative to traditional ASP.NET (Web Forms). It is a lightweight, highly testable framework, integrated with all existing ASP.NET features, such as Master Pages, Security, and Authentication.

Visual Studio Express 2012/2010

Visual Studio Express is a free version of Microsoft Visual Studio.

Visual Studio Express is a development tool tailor made for MVC (and Web Forms).

Visual Studio Express contains:

MVC and Web Forms
Drag-and-drop web controls and web components
A web server language (Razor using VB or C#)
A web server (IIS Express)
A database server (SQL Server Compact)
A full web development framework (ASP.NET)

If you install Visual Studio Express, you will get more benefits from this tutorial.

If you want to install Visual Studio Express, click on one of these links:

Visual Web Developer 2012 (If you have Windows 7 or Windows 8)

Visual Web Developer 2010 (If you have Windows Vista or XP)

	After you have installed Visual Studio Express the first time, it pays to run the installation one more time, to install fixes and service packs. Just click on the link once more.

ASP.NET MVC References

At the end of this tutorial you will find a complete ASP.NET MVC reference.

ASP.NET MVC Top 10 Interview Questions

2014-03-31T19:09:00.000-07:00

1. Explain MVC (Model-View-Controller) in general?

MVC (Model-View-Controller) is an architectural software pattern that basically decouples various components of a web application. By using MVC pattern, we can develop applications that are more flexible to changes without affecting the other components of our application.

"Model" is basically domain data.
"View" is user interface to render domain data.
"Controller" translates user actions into appropriate operations performed on model.

2. What is ASP.NET MVC?

ASP.NET MVC is a web development framework from Microsoft that is based on MVC (Model-View-Controller) architectural design pattern. Microsoft has streamlined the development of MVC based applications using ASP.NET MVC framework.

3. Difference between ASP.NET MVC and ASP.NET WebForms?

ASP.NET Web Forms uses Page controller pattern approach for rendering layout, whereas ASP.NET MVC uses Front controller approach. In case of Page controller approach, every page has its own controller, i.e., code-behind file that processes the request. On the other hand, in ASP.NET MVC, a common controller for all pages processes the requests.
Follow the link for the difference between the ASP.NET MVC and ASP.NET WebForms.

4. What are the Core features of ASP.NET MVC?

Core features of ASP.NET MVC framework are:

Clear separation of application concerns (Presentation and Business Logic)
An extensible and pluggable framework
Extensive support for ASP.NET Routing
Support for existing ASP.NET features

Follow for detailed understanding of the above mentioned core features.

5. Can you please explain the request flow in ASP.NET MVC framework?

Request flow for ASP.NET MVC framework is as follows:

Request hits the controller coming from client. Controller plays its role and decides which model to use in order to serve the request further passing that model to view which then transforms the model and generates an appropriate response that is rendered to the client.

6. What is Routing in ASP.NET MVC?

In case of a typical ASP.NET application, incoming requests are mapped to physical files such as .aspx file. ASP.NET MVC framework uses friendly URLs that more easily describe user’s action but are not mapped to physical files.

ASP.NET MVC framework uses a routing engine, that maps URLs to controller classes. We can define routing rules for the engine, so that it can map incoming request URLs to appropriate controller.

Practically, when a user types a URL in a browser window for an ASP.NET MVC application and presses “go” button, routing engine uses routing rules that are defined in Global.asax file in order to parse the URL and find out the path of corresponding controller.

7. What is the difference between ViewData, ViewBag and TempData?

In order to pass data from controller to view and in next subsequent request, ASP.NET MVC framework provides different options i.e., ViewData, ViewBag and TempData.

Both ViewBag and ViewData are used to communicate between controller and corresponding view. But this communication is only for server call, it becomes null if redirect occurs. So, in short, it's a mechanism to maintain state between controller and corresponding view.

ViewData is a dictionary object while ViewBag is a dynamic property (a new C# 4.0 feature). ViewData being adictionary object is accessible using strings as keys and also requires typecasting for complex types. On the other hand, ViewBag doesn't have typecasting and null checks.

TempData is also a dictionary object that stays for the time of an HTTP Request. So, Tempdata can be used to maintain data between redirects, i.e., from one controller to the other controller.

8. What are Action Methods in ASP.NET MVC?

I already explained about request flow in ASP.NET MVC framework that request coming from client hits controller first. Actually MVC application determines the corresponding controller by using routing rules defined in Global.asax. And controllers have specific methods for each user actions. Each request coming to controller is for a specific ActionMethod. The following code example, “ShowBooks” is an example of an Action method.

Collapse | Copy Code

public ViewResult ShowBooks(int id)
{
  var computerBook = db.Books.Where(p => P.BookID == id).First(); 
  return View(computerBook);
}

9. Explain the role of Model in ASP.NET MVC?

One of the core features of ASP.NET MVC is that it separates the input and UI logic from business logic. Role of Model in ASP.NET MVC is to contain all application logic including validation, business and data access logic except view, i.e., input and controller, i.e., UI logic.

Model is normally responsible for accessing data from some persistent medium like database and manipulate it.

10. What are Action Filters in ASP.NET MVC?

If we need to apply some specific logic before or after action methods, we use action filters. We can apply these action filters to a controller or a specific controller action. Action filters are basically custom classes that provide a means for adding pre-action or post-action behavior to controller actions.

For example:

Authorize filter can be used to restrict access to a specific user or a role.
OutputCache filter can cache the output of a controller action for a specific duration.

How to fix “Cannot connect to the configuration database.” for Sharepoint

2014-03-27T03:21:00.001-07:00

Most of the people facing the problem to open Central Administration or WebApplications after successfully created.
Then they finding the error message "Cannot connect to the configuration database"

I am also facing this problem so many times, at firstly i just restarted the system, but this is not the correct process, so i tried to find solution finally i got some solutions

1. Verify that the SQL database is running or not:

Start --> SqlServerManagement Studio ---> Server name [choose sharepoint]

Click ok. check is open or giving any error.
If it is not opening then Goto
Start ---> Run ---> Type : "Services.msc" ---> OK

There you can check SqlServer(SHAREPOINT) started or not, if not you can start manually.

Creating Simple Event Receivers in SharePoint 2013

2014-03-05T00:24:00.000-08:00

Create an empty SharePoint 2013 project in Visual Studio 2012. In the project, select add new item and select Event Receiver

Select the type of event receiver you need to add, and select the events you need to handle.

In this sample I'm trying to update a SharePoint list based on file changes happening to a separate SharePoint library. Basically, the list will act like a log. So we need to create the library and a list. Here, I have created the Department library to add and maintain documents and also created DocumentLog list to log the changes happening to the library.

In the list I have three columns, Title, Action & DateAndTime in order to catalog the changes happening to the library.

Back to the SharePoint project. Now go to the event receiver .cs file and you'll get a bunch of methods base on your selection during event receiver creation. Edit the code as below to implement the logic. Note that the ItemAdded method is used instead of the ItemAdding method.

public override void ItemAdded(SPItemEventProperties properties)
{
//base.ItemAdded(properties);
using (SPWeb web = properties.OpenWeb())
{
try
{
SPList list = web.Lists["DocumentLog"];
SPListItem newItem = list.Items.Add();
newItem["Title"] = properties.ListItem.Name;
newItem["DateAndTime"] = System.DateTime.Now;
newItem["Action"] = "Item Added";
newItem.Update();
}
catch (Exception ex)
{
throw ex;
}
}
}

public override void ItemUpdating(SPItemEventProperties properties)
{
//base.ItemUpdating(properties);
using (SPWeb web = properties.OpenWeb())
{
try
{
SPList list = web.Lists["DocumentLog"];
SPListItem newItem = list.Items.Add();
newItem["Title"] = properties.ListItem.Name;
newItem["DateAndTime"] = System.DateTime.Now;
newItem["Action"] = "Item Updated";
newItem.Update();
}
catch (Exception ex)
{
throw ex;
}
}
}

public override void ItemDeleting(SPItemEventProperties properties)
{
//base.ItemDeleting(properties);
using (SPWeb web = properties.OpenWeb())
{
try
{
SPList list = web.Lists["DocumentLog"];
SPListItem newItem = list.Items.Add();
newItem["Title"] = properties.ListItem.Name;
newItem["DateAndTime"] = System.DateTime.Now;
newItem["Action"] = "Item Deleted";
newItem.Update();
}
catch (Exception ex)
{
throw ex;
}
}
}

As I am targeting to add the event receiver only to the Department document library, the Elements.xml file requires a change.

Note that I have commented out the setting which points to all document libraries, instead pointed to Departmentdocument library. The edited Elements.xml file is as below:

<?xml version="1.0" encoding="utf-8"?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">

<Receivers ListUrl="Department">

<Receiver>
<Name>DepartmentEventReceiverItemAdded</Name>
<Type>ItemAdded</Type>
<Assembly>$SharePoint.Project.AssemblyFullName$</Assembly>
<Class>MySharePointProject.ListEventReceiver.DepartmentEventReceiver</Class>
<SequenceNumber>10000</SequenceNumber>
</Receiver>

<Receiver>
<Name>ListEventReceiverItemUpdating</Name>
<Type>ItemUpdating</Type>
<Assembly>$SharePoint.Project.AssemblyFullName$</Assembly>
<Class>MySharePointProject.ListEventReceiver.DepartmentEventReceiver</Class>
<SequenceNumber>10000</SequenceNumber>
</Receiver>
<Receiver>
<Name>ListEventReceiverItemDeleting</Name>
<Type>ItemDeleting</Type>
<Assembly>$SharePoint.Project.AssemblyFullName$</Assembly>
<Class>MySharePointProject.ListEventReceiver.DepartmentEventReceiver</Class>
<SequenceNumber>10000</SequenceNumber>
</Receiver>
</Receivers>
</Elements>

Compile and deploy the solution to your site. Now you may play around with the library and observe the changes happening to the list.... :)

I have added a document, uploaded, added, modified the 3 docs and then deleted one of the docs respectively.

And here's what I get in the DocumentLog list.

n-Tier Architecture

2014-02-21T09:36:00.000-08:00

What is n-Tier Architecture?

This is a very important topic to consider when developing an application. Many elements need to be considered when deciding on the architecture of the application, such as performance, scalability and future development issues. When you are deciding on which architecture to use, first decide on which of the three aforementioned elements you think is most valuable -- as some choices you make will impact on others. For example, some choices that boost performance will impact on the scalability or future development of your design, etc.

Here we will talk generally about what n-Tier architecture is, and then we will have a look at different n-Tier architectures you can use to develop ASP.NET applications and issues that arise relating to performance, scalability and future development issues for each one.

Firstly, what is n-Tier architecture? N-Tier architecture refers to the architecture of an application that has at least 3 "logical" layers -- or parts -- that are separate. Each layer interacts with only the layer directly below, and has specific function that it is responsible for.

Why use n-Tier architecture? Because each layer can be located on physically different servers with only minor code changes, hence they scale out and handle more server load. Also, what each layer does internally is completely hidden to other layers and this makes it possible to change or update one layer without recompiling or modifying other layers.

This is a very powerful feature of n-Tier architecture, as additional features or change to a layer can be done without redeploying the whole application. For example, by separating data access code from the business logic code, when the database servers change you only needs to change the data access code. Because business logic code stays the same, the business logic code does not need to be modified or recompiled.

[Note] tier and layer mean the same thing [End Note]

An n-Tier application usually has three tiers, and they are called the presentation tier, the business tier and the data tier. Let's have a look at what each tier is responsible for.

Presentation Layer
Presentation Layer is the layer responsible for displaying user interface and "driving" that interface using business tier classes and objects. In ASP.NET it includes ASPX pages, user controls, server controls and sometimes security related classes and objects.

Business Tier
Business Tier is the layer responsible for accessing the data tier to retrieve, modify and delete data to and from the data tier and send the results to the presentation tier. This layer is also responsible for processing the data retrieved and sent to the presentation layer.

In ASP.NET it includes using SqlClient or OleDb objects to retrieve, update and delete data from SQL Server or Access databases, and also passing the data retrieved to the presentation layer in a DataReader or DataSet object, or a custom collection object. It might also include the sending of just an integer, but the integer would have been calculated using the data in the data tier such as the number of records a table has.

BLL and DAL
Often this layer is divided into two sub layers: the Business Logic Layer (BLL), and the Data Access Layers (DAL). Business Logic Layers are above Data Access Layers, meaning BLL uses DAL classes and objects. DAL is responsible for accessing data and forwarding it to BLL.

In ASP.NET it might be using SqlClient or OleDb to retrieve the data and sending it to BLL in the form of a DataSet or DataReader. BLL is responsible for preparing or processing the data retrieved and sends it to the presentation layer. In ASP.NET it might be using the DataSet and DataReader objects to fill up a custom collection or process it to come up with a value, and then sending it to Presentation Layer. BLL sometimes works as just transparent layer. For example, if you want to pass a DataSet or DataReader object directly to the presentation layer.

Data Tier
Data tier is the database or the source of the data itself. Often in .NET it's an SQL Server or Access database, however it's not limited to just those. It could also be Oracle, mySQL or even XML. In this article we will focus on SQL Server, as it has been proven to be the fastest database within a .NET Application.

Logical Layers vs. Physical Layers (Distributed)
Logical Layers and Physical Layers are the ones that confuse people. Firstly, a logical layer means that layers are separate in terms of assembly or sets of classes, but are still hosted on the same server. Physical layer means that those assemblies or sets of classes are hosted on different servers with some additional code to handle the communication between the layers. E.g. remoting and web services.

Deciding to separate the layers physically or not is very important. It really depends on the load your application expects to get. I think it's worth mentioning some of the facts that might affect your decision.

Please DO note that separating the layers physically WILL slow your application down due to the delay in communicating between the servers throughout the network, so if you are using the physical layer approach, make sure the performance gain is worth the performance loss from this.

Hopefully you would have designed your application using the n-Tier approach. If this is the case, then note that you can separate the layers in the future.

Cost for deploying and maintaining physically separated applications is much greater. First of all, you will need more servers. You also need network hardware connecting them. At this point, deploying the application becomes more complex too! So decide if these things will be worth it or not.

Another fact that might affect your decision is how each of the tiers in the application are going to be used. You will probably want to host a tier on a separate server if more than 1 service is dependent on it, e.g. You might want to host business logic somewhere else if you have multiple presentation layers for different clients. You might also want a separate SQL server if you have other applications using the same data.

MVC Routes

2014-02-21T09:33:00.002-08:00

MVC3 gives you great control over how URLs are mapped to your controllers. It gives you the ability to define your URLs in a human readable SEO (Search Engine Optimization) friendly fashion, to remap old URLs to new functionality and side-by-side utilize classic ASP.NET sites inside of MVC3. It also results in hiding what kind of page user is calling and what environment we are working in. Most of the new websites are following this and it is important to understand that routing is not URL rewriting as routing will have customizations and many attachments towards request/response.
When we create any type of MVC application by default GLOBAL.ASAX file is created becoz ASP.NET implements MVC using this global application class mainly. Routes defined in the Global.asax.cs file of our MVC3 web application/site. In this global.asax file most important element relative to our work is RegisterRoutes method. By default, there is only one route defined in the RegisterRoutes method that looks like the line below.
routes.MapRoute(
"Default", // Route name
"{controller}/{action}/{id}", // URL with parameters
new { controller = "Home", action = "Index", id = UrlParameter.Optional } // Parameter defaults
);
This route defines the route name, which can be anything as long as it is unique, the URL template, and the parameter defaults. The default route that is pre-defined for you maps to Controller/Action/id. You can add additional routes by copying the same line and adjusting the URL parameters and the related default values. Remember when we add additional routes the order is important.
Custom MVC3 Routes
One of the many factors frequently considered by search engines to determine the relevance of a particular page to a particular search term is whether or not the URL link itself includes a particular term. In a classic ASP.NET site for a magazine, you might have a URL that looks like www.internet.com/ViewArticle.aspx?id=123. This URL passes the ID number of the article to view, but the URL itself doesn't describe the content in any human readable way. If the URL instead was www.internet.com/MVC3_Routing/123 a human-or a web crawler-could read that and know that the article is about MVC3 Routing.
Another frequent use of custom routing is to allow multiple sites to link to the same location while providing additional data about where they came from. For example, if you had a link to a product page and you wanted to provide custom co-branding based on which one of your partners linked in to a page, you could do so by including a "partner name" variable in the link. A link like this could be to www.internet.com/PartnerA/Article/123 or www.internet.com/PartnerB/Article/123 for example. This would allow two different sites to link to the same article while providing their own information in the process.
The code block below defines a new route called ArticleRoute that defines a new parameter called article in addition to the standard controller and action.
routes.MapRoute(
"ArticleRoute",
"{article}/{controller}/{action}",
new { article="Unknown", controller = "Home", action = "Index" } );
You can access this custom article part of the route in your controller by accessing the RouteData object.
RouteData.Values["article"]
To access the RouteData object in your Razor views, use the @Url.RequestContext.RouteData object.
When you are constructing URLs that use string data such as article titles or author's names, you will need to use some form of URL-friendly encoding. The easiest method is to use HttpUtility.UrlEncode("Your String") which will replace all of the URL unfriendly characters with the appropriate HTML escapes.B This method is web spider friendly but not necessarily human readable URL friendly.
It is very important to remember that any data in a URL is easily user manipulated and shouldn't be trusted. It is not an appropriate place to pass application variables between pages unless they are of a nature that it would be acceptable if the user manipulated them.
Re-mapping Routes
From time to time it is necessary to re-route an old URL to a new location. Traditionally you would use a redirect page to let users know to update their bookmarks and include a link to the new location. Sometimes it is impractical or even impossible to change URLs as is the case when you have 3rd party software systems set up to access and scrape particular URLs.
If you wanted to route MyRazor.cshtml page to your MVC3 Home/Index controller, you can do so by defining a route like the one below.
routes.MapRoute("RT", " MyRazor.cshtml ",
new { controller = "OtherController", action = "Packed" });
Including Classic ASP.NET as a Sub-directory in an MVC3 Web Application
If you have a large classic ASP.NET web site that you need to incrementally transition to MVC3 you can put the entire classic ASP.NET web site in your MVC3 web site as a sub-directory. You can then call the IgnoreRoute method seen in the code block below to tell MVC3 to not handle that particular URL path.
routes.IgnoreRoute("OldClassicASP/");
Constraints
You can define additional constraints to your defined routes to insure that the values passed for particular parts of your route are valid. This is useful not only for general security related needs but is also useful for scenarios where you might want to have additional routing logic in place for particular routes.
routes.MapRoute(
"ColorPath", // Route name
"{color}/{controller}/{action}/{id}", // URL with parameters
new { controller = "Home", action = "Index", id = UrlParameter.Optional } // Parameter defaults
, new { color="blue" }
);
In the example route above, a new anonymous object is added to the MapRoute path call that adds a constraint to this path. The route will only be used if the color is blue.
Namespaces
In large ASP.NET MVC3 applications you can potentially have hundreds of controllers. This can become problematic because the .NET Framework looks in the Controllers folder and all sub-folders looking for controllers to match up with the defined routes.
To help you organize your code, you can add namespaces to your routes to constrain the controllers the route will match to particular namespaces. The route below will only use controllers defined in the Home.Guru namespace.
routes.MapRoute("NamespacedRoute", "Cool/{controller}/{action}",
new { controller = "Home", action = "Index", id = UrlParameter.Optional } , null,
, new string[] { "Home.Guru" });
Global Filters
If you want to define code that runs before or after your routing calls, you can define a global filter. Global filters are registered in the Global.asax.cs file by adding a line to the RegisterGlobalFilters method. This method, by default, registers the HandleErrorAttribute that is used to handle error conditions in ASP.NET MVC3 applications.
If you wanted to add a copyright notice at the bottom of all of your pages, you could add a global filter attribute that overrides the OnResultExecuted method which is run after your page has run.
public class CopyrightNoticeAttribute : ActionFilterAttribute
{
public override void OnResultExecuted(ResultExecutedContext filterContext)
{
filterContext.HttpContext.Response.Write(String.Format("<h1>Copyright {0}</h1>",DateTime.Now.Year));
}
}
Once your custom attribute has been written you can add it to the global.asax.cs file.
public static void RegisterGlobalFilters(GlobalFilterCollection filters)
{
filters.Add(new CopyrightNoticeAttribute());
filters.Add(new HandleErrorAttribute());//Default in MVC3
}

------------------*--------------------------*-----------------------------------*-------------------------