Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
If you want to impress, these are the things that for some reason always crop up in informal c# technical tests:
Access modifiers &c - they are a bit different from Java.
try/catch/finally - specifically the difference between throw; and throw(e);
Dispose() versus destructor
why/how to put assemblies in the GAC
It's a good job I don't contract anymore. I've been using C# for a couple of years now and I couldn't give a sensible answer to any of those.
How did this happen? Who's to blame? Well certainly there are those more responsible than others, and they will be held accountable, but again truth be told, if you're looking for the guilty, you need only look into a mirror.
Express versions are quite capable, many companies use them commercially.
I wouldn't go into WPF if you are starting from scratch this weekend, but reading an overview (e.g wikipedia) of WPF, WCF, WWF would be good for your waffling skills... in fact generally reading around will maybe be better in an interview other than the obvious questions about "how is Java different from C#" you can probably find on a website and memorise.
If he knows Java well then I would hope so. The language itself is easy enough, it's the vast .NET libraries which must take ages to master.
Agreed. What I would say though is that with the .Net Framework, once you become familiar with the most used namespaces, finding what you need becomes much easier.
Had a contractor a while back who'd just been made redundant from his permie post. To be fair to the guy, he was c++, not c#, but he did enough to get past the client interview. What was telling however was that after the first week with myself and the other established contractors, his knowledge was just not upto scratch. After a couple of weeks, he walked out of the contract and we had to pick up the slack.
A few days after he left, we noticed he'd left a couple of things behind in a bag, the funniest of which was an ASP.Net for dummies book.
The morale of the story is, if your going to blag your way into an interview, make sure you do the homework and get yourself upto scratch quick, less there be other contractors ready to rip it out of you.
Comment