|
I've been playing with ANTS and like it. I'll grep google dotTrace to see what it's like. Thanks!
|
|
|
|
|
Definitely have a look at MiniProfiler[^] and Glimpse[^].
If you're using Entity Framework, EFProf[^]
Jon Sagara
Some see the glass as half-empty, some see the glass as half-full. I see the glass as too big.
-- George Carlin
Blog | Twitter | Articles
|
|
|
|
|
I didn't want IE 11, but at some point (must have been inebriated) the Windows Update options got set to install automatically and treat recommended updates like important updates. The WU settings have now been corrected, but here I am with IE 11...surprise, surprise. Annoyed? Yes, if for nothing else, it will most certainly create some work, like IE 10 did. 
I would rather have given it a go in a VM first, but here it is,...just roll with it. Visually, it looks the same as IE 10. Press F12, and now the differences become apparent. I really like the way the element highlighter works. It's too bad I got click happy...clicking on the Network tab threw IE into a tailspin. Task manager showed a few dozen iexplore.exe processes, with more being spawned as I watched.  The only way out was a reboot. Has anybody else had issues with the dev tools in IE 11?
Edit: I just duplicated the problem with the Network button/tab in the IE 11 dev tools. Also, it was not IE spawning new procs. I think it must have been explorer.exe due to something unrelated. Clicking the Network button just freezes IE. I'm not sure what it is supposed to do, but I won't be clicking on it again.
"Go forth into the source" - Neal Morse
modified 27-Nov-13 12:56pm.
|
|
|
|
|
IE 10 broke our ASP.NET websites because it was not in the .NET browser definition files and so little things like __dopostback quit working. MS has a hotfix out, which we installed Monday. Problem solved.
Tuesday, I get a call from one of my users that he got auto updated to 11 and our site doesn't work. Exact same problem - this time, without the MS hotfix. Fortunately, I found a way to add app local browser definitions and got it working again.
I truly dislike automatic updates.
|
|
|
|
|
|
In the new versions of IE, they have hidden the setting to automatically update to new versions.
It's in the "About" box. Go see.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
How to get back on track ? I know C#( worked for a year ), I was really good in C during student life (Computer science and engineering grad) as well.
Now want to do MVC, very little knowledge of HTML and CSS. Can anyone give me some idea how to make myself fit for a job by Jan'2014 ?? its not a joke.
(I am jobless at the moment ). by the way I am in UK.
|
|
|
|
|
Well start by assembling a resume and account for all your programming experience. Brush up on material and start applying for open positions around your area. Good luck!
|
|
|
|
|
Thank you , for your reply.
|
|
|
|
|
Get up to speed with .NET (the latest you can run), buy a couple of O'Reily books on MVC (they seem good) get back to doing some C, look up a bit of HTML/CSS (a little knowledge can be a dangerous thing)
Don't lie on the CV, just be a little shady with dates. Oh yeah master the "I will look at that" expression, and you are good to go!
|
|
|
|
|
If I were you, based on your description here, I'd apply for junior level development positions. However, as you have very little knowledge of HTML and CSS, I would recommend that you buy some good books and spend a lot of time catching up on MVC, HTML and CSS, as well as C#.
|
|
|
|
|
This is good advice, even low level computer jobs pay good compared to other options.
Also, after you have a year or 2 under your belt with a new 'junior' job, don't stay satisfied at that position, start moving up, or move to another company. In just a few short years, everyone will forget about that 'missing' time period when your career had a false start.
Edit: I learn the most new skills when I start a new job. Just getting the job is 90% of the work. At the new job, always ask to work on the project that uses the technology you most want to learn for your career.
|
|
|
|
|
In addition to what Richard (and others) said, I recommend building a non-trivial (start simple, then add complexity) web app that you can host at a cheap ASP .NET host in order to be able to demo to a potential employer. Nothing says "I can code" like demonstratable running code.
Good luck! 
/ravi
|
|
|
|
|
That does help and also articles on here. Helped me land me my last job before retiring.
|
|
|
|
|
|
thank you , seems so much realistic. 
|
|
|
|
|
My dear brother, this could be the best advice. This is where software has more advantage. The ability for a beginner to start a project with minimal resources (laptop and internet) and then improve it.
Project
Project
Project
Fortēs fortūna adjuvat.
|
|
|
|
|
Ravi Bhavnani wrote: Nothing says "I can code" like demonstratable running code.
I couldn't agree more!
When I interview, I always ask for code to look at. First thing I check is if it has that "classroom assignment" or "copied from a book" smell to it. I expect you to be able to give a tour so I can also smell whether it is borrowed code and not your own. I want to see how you code, format your code, and most importantly comment your code. I don't look for any rigid "standard du jour", just if it is easy on the eyes, I may have to debug your code at some future date and I want to see if I'll be able to find my way around. Or better yet, what I can learn from it.
Most important to me is interacting to develop a sense of your understanding of the concepts. Again, I don't go for 'gotcha' syntax, those things change too fast (although I've met too many interviewers who delight in seeing if you know some obscure syntax they think is important), I want to see if you understand what you need to learn if you don't know it.
I look for passion, not a checklist.
Psychosis at 10
Film at 11
Those who do not remember the past, are doomed to repeat it.
Those who do not remember the past, cannot build upon it.
modified 2-Dec-13 16:43pm.
|
|
|
|
|
Where I work, we ask candidates who pass our phone screens and are invited for an in-person interview to write a small piece of code. We give them a small programming problem and see how they talk out their design and implement the algorithm. It's amazing what you can learn from this.
/ravi
|
|
|
|
|
|
It's very difficult to get caught up you have to work twice as hard and be very devoted. As OP has said take a junior position and work hard.
I took a 10 year hiatus and have partially caught up but it took me a couple of years and there's still a lot I didn't have time for.
Good luck
|
|
|
|
|
|
have seen it , though need some more ideas.
|
|
|
|
|
|
seems really for me , reference artical. thank you.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
