[Questpond Dvd Free Download Shared
Hanne Rylaarsdam
The interview was scheduled at 11 AM there where around 40 people had applied and 12 positions where vacant for SSE( Senior software enginner). First HR told me to fill a form where I needed to fill information like salary , my current company , location preference , contact phone number etc.
One question which I was not able to answer was around Entity framework. I would suggest you to read Entity framework interview questions from codeproject -NET-Entity-Framework-Interview-Questions, I think now a days people surely ask questions around entity framework as ADO.NET is becoming obselete.
He then went in to ASP.NET interview questions like page life cycle , view state , sessions , caching etc. One ASP.NET interview question where he really took me for a ride is viewstate versus session.
Later he went in to WCF and Web service. Thanks to .NET interview questions videos of www.questpond.com I was able to answer most of them. The only place I got stuck was in a WCF question where he asked can we overload WCF. I was not sure of it. Below is a video which answers the same in detail.
The final minutes of my interview were completely around SQL Server. Interviewer told me to write a query to find third highest , luckily I had seen the below video , I used the same logic and I think interviewer was pretty happy.
Interviewer then told me to sit outside. After a hour I was called by HR , she congratulated me for my position. I had asked for higher salary which the company was reluctant. I think capgemini has fixed salary bracket salary as per experience. They do not too overboard to higher people even if you are good. I took the offer as I had already made my mind up to leave the current company.
We are Questpond an educational platform running since 2002 by Mr. ShivPrasad Koirala and his team. Questpond is focused only on IT sectors and covers all It topics like .NET, C#, SQL Server, MSBI, Sharepoint, MVC, Silverlight, Design Pattern, Object Oriented Programming, Angular 2.0 and 4.0, azure and many more open source and Microsoft technologies.
Our teaching is simple and fun to learn complex topics, we are very active on social media channels like Youtube, Facebook, stack overflow, twitter, linkedin. To know more about us and our style of teaching you can check our Youtube videos where we have shared knowledge.
For our subscribers or customer we do provide complete end-to-end support via skype, call and email. every weekend evening 1 hour we do take live training sessions which includes angular and other new topics.
Apart from self-training materials our core strength we offer online based and offline based trainings. Online based trainings open for everyone across any region or country. Offline based trainings currently going on in our Andheri, Mumbai - India office only.
This article talks about 6 ways of doing locking in .NET. It starts with concurrency problems and then discusses about 3 ways of doing optimistic locking. As optimistic locking does not solve the concurrency issues from roots, it introduces pessimistic locking. It then moves ahead to explain how isolation levels can help us implement pessimistic locking. Each isolation level is explained with sample demonstration to make concepts clearer.>
Many times we would like to check concurrency on only certain fields and omit fields like identity etc. For those kind of scenarios
we can check the old value and the new value of the updated fields as shown in the below code snippet.
Yes, you said right. By using optimistic locking you only detect the concurrency problem. To solve concurrency issues from the roots
itself we need to use pessimistic locking. Optimistic is like prevention while pessimistic locking is actually the cure.
The other locks are pretty straight forward; the update lock is confusing because of its hybrid nature. Many times before we update we read the record. So during read the lock is shared and while actually updating we would like to have an exclusive lock. Update locks are more of transient locks.
Isolation levels are features of RDBMS software, in other words they fundamental really belong to SQL Server and not to Ado.NET, EF or LINQ. Said and done that you can always set the transaction isolation level from any of these components.