What components make up enterprise .NET development

Question

I'm looking at applying for a new job as an Enterprise .NET programmer. It says I need to have Enterprise programming experience.

I have a lot of .NET experience, but I moved to a different role a few years ago which is very much Enterprise, just not .NET enterprise.

What .NET components should I be familiar with? Remoting, LINQ, WCF, Workflow Foundation - anything else?

Answer 1

I would expect a good, versatile enterprise .NET developer to at least have knowledge of (in random order):

• A database engine, such as MS SQL Server
• An object/relational mapper, such as Entity Framework
• Communication technologies, products, and frameworks, such as HTTP/SOAP/REST, BizTalk/NServiceBus, WCF/OpenRasta
• User experience, user interface design, and user interface development using WPF, WinForms, ASP.NET, and similar
• Enterprise application patterns and integration patterns, general design patterns (read and understand books from Fowler et. al, Gamma et. al)
• Knowledge of systems engineering
• Knowledge of and ability to work with at least one common source control system
• Knowledge of continuous integration
• Preferably knowledge of continuous deployment

I've almost certainly forgotten things here, but this is at least a minimal skill set.