I studied the following stuff at my free time, hope it would be useful for you too..
Project Management - Roles & Responsibilites, etc
Agile Project Mangement
shallow copy vs deep copy
MVC vs MVP
.NET, WCF, AZURE interview questions
Design patterns, IOC, Aggregation vs Composition, etc.
Guide to understanding your Form-16
SQL Server - Shortcut Keys
Transactions, Nested Transactions, Exception handling - SET XACT_ABORT OFF
Windows Azure Videos from Channel9
ASP.NET Dynamic controls data persisting
Health monitoring for ASP.NET applications
20 Subjects Every Software Engineer Should Know
LINQ - variable type inference, object initializers, anonymous types and lambda expressions
Six Considerations in moving your application to Cloud
Good example (using Music) to explain about cloud computing.
Multi-Tenancy Architecture Models
Agile - Kanban board
7 Reasons Why Your Team Does not Get to Done
Twisting the MVC Triad - Model View Presenter (MVP) Design Pattern
MVC - For beginner
MVC - Good explanation
C#.net Framework 4
- Using Tuple we can return multiple values from a method.
- Similarly Tuple we can pass multiple values to a method through a single parameter.
- Joins (Inner Join, Outer Join, self join) definition with examples
Microsoft Press EBooks downloadable from
Singleton design pattern - 5 ways of implementation
WCF - Singleton WCF Proxy
WCF - Security
ASP.NET 2.0 PAGE LIFE CYCLE - Events order - page, master page, user control, nested user control.
ASP.NET 2.0 Interview questions
The MVC pattern is a UI presentation pattern that focuses on separating the UI (View) from its business layer (Model). The pattern separates responsibilities across three components:
1. The view is responsible for rending UI elements,
2. The controller is responsible for responding to UI actions, and
3. The model is responsible for business behaviors and state management.
In most implementation all three components can directly interact with each other and in some implementations the controller is responsible for determining which view to display (Front Controller Pattern),
The MVP pattern is a UI presentation pattern based on the concepts of the MVC pattern. The pattern separates responsibilities across four components:
1. the view is responsible for rending UI elements,
2. the view interface is used to loosely couple the presenter from its view,
3. the presenter is responsible for interacting between the view/model, and
4. the model is responsible for business behaviors and state management.
In some implementations the presenter interacts with a service (controller) layer to retrieve/persist the model.
The view interface and service layer are commonly used to make writing unit tests for the presenter and the model easier.
Rhino Mocks - Mock Object Framework tools when performing Test-Driven Development
A stub acts as a stand-in for a normal object. There are multiple reasons that you might create a stub. For example, as discussed above, the actual object might access an external resource such as a database or the file system causing the actual object to be too slow to use in a unit test. The stub enables you to perform a test in a reasonable amount of time without requiring any configuration.
IMP- When performing state-based verification, the final statement in your unit test is typically an assert statement that asserts that some condition is true.
When performing behavior verification, your test typically does not end with an assert statement. Instead, the interaction of the objects being tested is verified. Rhino Mocks throws an exception automatically when mock expectations do not meet reality.
TDD - Test Driven Development