I dislike MVC, because it is unnecessarily complicated, and will take (me) longer to develop and maintain. But if you start today, MVC with Razor is the way to go. Everything else is just outdated. MVC razor is the most recent standard for working with asp.net. (at least it was two months ago, gosh things change rapidly) Leo

I love the KISS (Keep it Stupid Simple) approach. I find that for each hour of new development, in the two years after that, it will generate at least another 8 hours of maintenance: changes, additions, optimization, troubleshooting and bug fixes. Of course I don't know your case specific scenario, and replacing 20 lines with one line that can be much better and easier to maintain than the 20 lines. But if you can fall on many aspects: - Is it easy to understand for someone else than the author? (or even for yourself 3 months later?) - does it require - yet another technology - that may disappear or get replaced by something better in 6 months? You don't want to get to a project that before someone can start to work on it they have to understand seven different components, techniques, conventions or technologies. But then again, kiss is subjective.

This is an interesting topic, seeing that I interview a lot of candidates. Obviously asking annoying questions will mark you as being a troublesome characters which most developer teams prefer to avoid. But beyond being polite, and beyond checking if the candidate took actual interest into our workplace, this question does come up, and I am wondering what I would ask if I was to be interviewed myself. I think I would ask: "Can I spend a few minutes with one of the developers who is working now, to see what kind of environment you are working in"? This would give you a chance to look at the work environment (hardware), and to ask some 'none formal' questions (QA, testing, dev software, procedures, etc), and of course check out the people where you may find yourself spending an incredible amount of time with in the near future.

Thanks, that piece of information is usefull to hear, because ininitally I was resistant to that approach, but if that is what really works it is just about getting to the idea of working a bit differently.

excellent link thatraja, thanks!

The full edition is $499 per user, (visual studio itself is only about $510), I am looking for something simpler and much cheaper. I also want something that I can still use when I upgrade to my next visual studio version.

I am planning to upgrade our visual studio editions from 2010 to 2013 professional (without MSDN). Our current 2010 solution still works with visual source safe 2005 (!!!), it works beautifully, but I find it too old to continue with it. What is the best practice, free or low cost solution for source control of a development team these days? - About 12 programmers - Visual studio 2013 only. Previously I was put off by team foundation because of cost, and complicity. I only have to keep versions, and make sure that two people wouldn't work on the same file at the same time. Hope someone can shorten my learning process by sharing his/her own experience.

For my department, I choose 2 x 4:3 screens, default 1280x1024 resolution. It works fantastic for development, and a second screen is a must. Whenever I work with a 'widescreen' I curse it, the space just seems to big use effiently: too much eye movement horizontally, too little space vertically. It is great for movies, but not for working. It is also too small to split into two.