Following are some of the questions which I faced during interviews (don't remember all of them).
- Difference between WCF and Web API
- ASP.NET Page Life Cycle (5)
- Session-State Modes
- How to find out whether it is a post back in the web form
- IIS version you are using
- Query the second most salary from a table of salaries using SQL
- Write a simple Angular 5 app which list data from a REST API. Include some action on the list like delete row.
Noticed the count/* beside some questions? It indicates that the question was asked on multiple occasions.
No matter what kind of interview you are going to attend, prepare for this question.
- WCF enables building services that support multiple transport protocols (HTTP, TCP, UDP, and custom transports) and allows switching between them.
- Web API is HTTP only. The first-class programming model for HTTP. More suitable for access from various browsers, mobile devices etc enabling wide reach.
- WCF enables building services that support multiple encodings (Text, MTOM, and Binary) of the same message type and allows switching between them.
- Web API supports a wide variety of media types including XML, JSON etc.
- WCF supports building services with WS-* standards like Reliable Messaging, Transactions, Message Security.
- Web API uses basic protocol and formats such as HTTP, WebSockets, SSL, JSON, and XML. There is no support for higher level protocols such as Reliable Messaging or Transactions.
- WCF supports Request-Reply, One Way, and Duplex message exchange patterns.
- HTTP is request/response but additional patterns can be supported through SignalR and WebSockets integration with Web API.
- WCF SOAP services can be described in WSDL allowing automated tools to generate client proxies even for services with complex schemas.
- There is a variety of ways to describe a Web API ranging from auto-generated HTML help page (eg. Swagger) describing snippets to structured metadata for OData integrated APIs.
- WCF ships with the .NET framework.
- Web API ships with the .NET framework but is open-source and is also available out-of-band as an independent download.
A delegate is a type that represents references to methods with a particular parameter list and return type.
- Delegates allow methods to be passed as parameters.
- Delegates can be used to define callback methods.
- Delegates can be chained together.
When an ASP.NET page runs, the page goes through a life cycle in which it performs a series of processing steps. These include initialization, instantiating controls, restoring and maintaining state, running event handler code, and rendering. It is important for you to understand the page life cycle so that you can write code at the appropriate life-cycle stage for the effect you intend.
In general terms, the page goes through the stages outlined in the following table.
|Page request||The page request occurs before the page life cycle begins. When the page is requested by a user, ASP.NET determines whether the page needs to be parsed and compiled (therefore beginning the life of a page), or whether a cached version of the page can be sent in response without running the page.|
|Start||In the start stage, page properties such as Request and Response are set. At this stage, the page also determines whether the request is a postback or a new request and sets the IsPostBack property. The page also sets the UICulture property.|
|Initialization||During page initialization, controls on the page are available and each control's UniqueID property is set. A master page and themes are also applied to the page if applicable. If the current request is a postback, the postback data has not yet been loaded and control property values have not been restored to the values from view state.|
|Load||During load, if the current request is a postback, control properties are loaded with information recovered from view state and control state.|
|Postback event handling||If the request is a postback, control event handlers are called. After that, the Validate method of all validator controls is called, which sets the IsValid property of individual validator controls and of the page. (There is an exception to this sequence: the handler for the event that caused validation is called after validation.)|
|Rendering||Before rendering, view state is saved for the page and all controls. During the rendering stage, the page calls the Render method for each control, providing a text writer that writes its output to the OutputStream object of the page's Response property.|
|Unload||The Unload event is raised after the page has been fully rendered, sent to the client, and is ready to be discarded. At this point, page properties such as Response and Request are unloaded and cleanup is performed.|
Within each stage of the life cycle of a page, the page raises events that you can handle to run your own code.
|Page Event||Typical Use|
|PreInit||Raised after the start stage is complete and before the initialization stage begins. Use this event for Checking the IsPostBack property to determine whether this is the first time the page is being processed, The IsCallback and IsCrossPagePostBack properties have also been set at this time, Create or re-create dynamic controls, Set a master page dynamically, Set the Theme property dynamically and Read or set profile property values.|
|Init||Raised after all controls have been initialized and any skin settings have been applied. The Init event of individual controls occurs before the Init event of the page. Use this event to read or initialize control properties.|
|InitComplete||Raised at the end of the page's initialization stage. Only one operation takes place between the Init and InitComplete events: tracking of view state changes is turned on. View state tracking enables controls to persist any values that are programmatically added to the ViewState collection. Until view state tracking is turned on, any values added to view state are lost across postbacks. Controls typically turn on view state tracking immediately after they raise their Init event. Use this event to make changes to view state that you want to make sure are persisted after the next postback.|
|PreLoad||Raised after the page loads view state for itself and all controls, and after it processes postback data that is included with the Request instance.|
|Load||The Page object calls the OnLoad method on the Page object, and then recursively does the same for each child control until the page and all controls are loaded. The Load event of individual controls occurs after the Load event of the page. Use the OnLoad event method to set properties in controls and to establish database connections.|
|Control events||Use these events to handle specific control events, such as a Button control's Click event or a TextBox control's TextChanged event.|
|LoadComplete||Raised at the end of the event-handling stage. Use this event for tasks that require that all other controls on the page be loaded.|
|PreRender||Raised after the Page object has created all controls that are required in order to render the page, including child controls of composite controls. (To do this, the Page object calls EnsureChildControls for each control and for the page.) The Page object raises the PreRender event on the Page object, and then recursively does the same for each child control. The PreRender event of individual controls occurs after the PreRender event of the page. Use the event to make final changes to the contents of the page or its controls before the rendering stage begins.|
|PreRenderComplete||Raised after each data bound control whose DataSourceID property is set calls its DataBind method. For more information, see Data Binding Events for Data-Bound Controls later in this topic.|
|SaveStateComplete||Raised after view state and control state have been saved for the page and for all controls. Any changes to the page or controls at this point affect rendering, but the changes will not be retrieved on the next postback.|
|Render||This is not an event; instead, at this stage of processing, the Page object calls this method on each control. All ASP.NET Web server controls have a Render method that writes out the control's markup to send to the browser. If you create a custom control, you typically override this method to output the control's markup. However, if your custom control incorporates only standard ASP.NET Web server controls and no custom markup, you do not need to override the Render method. For more information, see Developing Custom ASP.NET Server Controls. A user control (an .ascx file) automatically incorporates rendering, so you do not need to explicitly render the control in code.|
|Unload||Raised for each control and then for the page. In controls, use this event to do final cleanup for specific controls, such as closing control-specific database connections. For the page itself, use this event to do final cleanup work, such as closing open files and database connections, or finishing up logging or other request-specific tasks.|
ASP.NET session state supports several different storage options for session data.
|InProc||which stores session state in memory on the Web server. This is the default.|
|StateServer||which stores session state in a separate process called the ASP.NET state service. This ensures that session state is preserved if the Web application is restarted and also makes session state available to multiple Web servers in a Web farm.|
|SQLServer||stores session state in a SQL Server database. This ensures that session state is preserved if the Web application is restarted and also makes session state available to multiple Web servers in a Web farm.|
|Custom||which enables you to specify a custom storage provider.|
|Off||which disables session state.|
By checking Page.IsPostBack Property, Gets a value that indicates whether the page is being rendered for the first time or is being loaded in response to a postback.
SELECT TOP 1 * FROM TABLENAME WHERE SALARY < (SELECT MAX(SALARY) FROM TABLENAME) ORDER BY SALARY DESC
Of course there is another better solution, which is using SQL OFFSET-FETCH clause, which is
SELECT * FROM TABLENAME ORDER BY SALARY DESC OFFSET 1 ROWS FETCH NEXT 1 ROWS ONLY
- Types of action result in MVC (2)
- Filters in MVC (3)
- Can we define multiple actions with same name in a MVC controller?
- Areas in MVC
- Mvc request life cycle
- Difference between tempdata viewdata and viewbag
- Why leaving current organization (3)
- Difficult people you have been in touch with during work (Manager, Stakeholder or Colleagues) and how you dealt with them
- How you responded when a drastic change is requested by the client after all the work done
- Which project you think that doesn't achieved its reach and why that happened
- Explain entire lifecycle of a project that you handle (2)
- Did your Umbraco sites backoffice is publicly accessible?
- What is the alternative for Archetype ?
- Packages you have worked with
- Custom Data Type
- How to show custom error for media upload if file size exceeds the limit ?
- Experience with Umbraco Forms
- Difference between surface controller and a normal mvc controller?
- API Controller
- Built authorized pages?
- Boxing and Unboxing
- Serialization & Deserialization
- by reference vs. by value
- C# supports multi-inheritance?
- How to stop inheritance?
- For Ajax calls, what is the lifecycle of a WebForm
- Can we return view from Web api? - NO
- getElementsByName, getElementById
- by reference vs. by value
- How can we access a WCF
- Modules (2)
- Why chosen Angular over ReactJS
- What is Polyfills.js
- Pure/Impure Pipes
- Template driven forms
- NgOnChanges, NgDirty
- What is @Input and @Output
- How to deploy Angular project and what is dist folder
- How Angular works in browser
- What is AOT
- How to write Custom Pipes and how will name
- How to reduce apk size
- Why using Xamarin forms over native application?
- Architecture of xamarin forms project
- Server side paging via entity framework
- Entity framework approaches
- Entity framework versions you have worked with?
- How PCL compiled
- Difference between PCL and shared projects (Xamarin)
- What is MVC
- How model is validated MVC?
- Some components annotations
- How to differentiate Web API controllers from MVC controllers if they have same name
- What can be done in wcf which cannot done in Web API?
- Oath flow
- Session in MVC
- What's inside app data folder
- Cache advantages
- How can we define Cache expiry
- How an old SQL project can be moved to entity framework in less time
- Mvc project architecture (2)
- What's inside MVC areas folder
- Routing in MVC (2)
- Attribute routing in MVC (2)
- Routing priority
- Tag helpers in MVC
- Tag helpers or html helpers you use and why
- Dependency injection
- Advantages of Razor
- How to retrieve data posted in MVC controller
- Override method in a class
- Worker types in azure
- Iaas Azure
- Difference between MVC 5 and 6
- CRUD in entity framework
- Lazy loading in EF
- IEnumerable vs List
- Polymorphism in OOP
- Interface vs Abstract classes
- Is there abstract methods
- Reporting tools you have used
- How to reuse a certain view section in multiple places
- Why you choose Angular over KnockoutJs
- Oracle DB Experience (3)
- What is the purpose of Global.Ascx
- In Web forms, in which page lifecycle method we can toggle element visibility
- REST vs SOAP
- Mobile API security guidelines (Sensitive data handling techniques)
- Complex system deployment automation tools and techniques
- DML and DDL in SQL
- Transactions in SQL
- Process vs Task
- What is SPA
- How can we convert WCF to a REST service
As you can see, this a long list so will take time to format the questions as well as include answers. Consider this as a draft for now.