How can we possibly "suggest me any selected interview question of dot net which I can study in 24 hour and get selected for the job"?
We have no idea what the interviewer will ask - if they all asked the same questions, then we would all pass the interview every time, and they could not select anybody!
Instead, research the company. Find out what they do, how they do it, what their competitors do, and how. Then try to learn around that.
No-one can give you "the answer" to an interview - particularly if we have no idea what the company is looking for!
Good luck - I hope you won't need it.
BTW: Don't say "it's urgent" - it is for you, but not for us, na dit annoys some people to the point where they will not answer your question on principle...
I have found that if you are honest on your resume, you won't find yourself in this predicament. Typically, it is hard to get an interview for an area of programming, unless you have previously stated that you know it.
My answer, and my advice, is to be honest with the interviewer regarding your experience in ASP.NET. Do you really want to get this position, to which you will have not be able to contribute and likely leave? And where your manager may end up resenting you if you are hired, for having only crammed for the interview?
Practice, practice, practice.
It is about the only way you are going to improve professionly and eventually it will show through in an interview. Especially in those areas you are not so strong at.
Incidently, my from experience, I am extremely cynical of technical interviews and their value. Don't be too hard on yourself if you get burned in a technical interview. It atill happens to developers with many years experience, like me (20+)
ahahh we have a "ive got 3 years experience on my cv but in reality i have 3 months" person here... In reality I suspect you will be found out in your interview, i personally would not employ you after finding out.
You might want to focus on proving that you have the "programmer" mind-set, if you lack the experience. You know, show that you have the potential. And in this case, you need to know general principles, like protected vs. private vs. internal, what is the difference between an abstract class and an interface, what does virtual mean, what is a sealed class, how can you add an extension method, how does the garbage collector work, things like that. Because if you have a solid understanding of the base stuff, the rest is really reading about it when you run into it. No programmer knows everything, and with the little time that you have you can't start studying design patterns or specific libraries. Of course, if you're shaky on the base stuff, maybe you're not ready to start interviewing for such a position, maybe you need to study and practice some more.
Anyway, good luck, and if you have the potential, I wish you that the interviewer sees it!
This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)
Submit an article or tip