Day 79 – Driven to Distraction

I did some programming tonight. I got so absorbed in what I was doing that I completely lost track of time. *yawn*

I was actually playing around with some JavaScript for the first time, and it was an educational and frustrating experience. I really need to have a bit more of a play with Visual Studio to figure out what tooling is available for debugging.

Biggest frustration so far: Razor looks great for ASP.NET, but it was completely baffling how to get my JavaScript to come through. Sorted it out in the end, but then decided that using an MVC project was overkill to play with JS, so nuked it all. I’m sure there is an easy way to do it all, but I’ll have to look at a few MSDN tutorials to get the gist of the recommended approach here.

I definitely went in the deep end there.

And now I need to sleep.
One more day, and then a nice long weekend… to play more with this?

PS: Sorry, no header picture today. I just don’t have the energy to think of something.

4 thoughts on “Day 79 – Driven to Distraction”

  1. VS2012 has JavaSript intellisense that apparently works, so it might be worth using an express version. Also (although I suspect you know this) the Chrome debugging dev tools are wonderful.

    1. The Intellisense was pretty decent in VS2012, but apparently it’s better in 2013. Why Express, when I can just install the full edition from MSDN? 🙂

  2. Sorry, I meant VS2013, of which I think only the RC is available. I found the intellisense in VS2012 for JavaScript pretty useless and rather irritating. The sentence should have read “VS2013 has JavaScript intellisense that apparently actually works…”. I just need to untangle my fingers! Express, just because it’s a release candidate, and you may not want everything, just to try the webbie stuff.

    1. I have an install of VS2013 Ultimate RC on my machine to play with. Just refreshed the key as well. I was sticking to VS2012 for my little project for compatibility reasons.

Comments are closed.