So after installing the new version of ASP.NET Core I wanted to try out the new CLI so I started a command prompt ran "yo aspnet" made all the simple choices and then I got a template setup and a list of instructions on what to do next. All good!!!

But something caught my eye a little message stating that bower is not recognized as an internal or external command....weird but everything else was looking good so I looked around some and discovered that well ... bower was not installed on my machine. So a quick "npm install -g bower" and then re-did that whole "yo aspnet" ...no more errors...great !!

Still can't figure out how come Bower was not installed on that machine, but anyways not it works and all the dotnet command also, which by the wat I think make more sense than what was previously available.

If you were like me and did not upgrade to the latest bits of ASP.NET Core (lack of time...), and we're still on RC2 you will be sorry when October 31st comes around. Following this annoucement on their github repo, as of October 31st if you did not upgrade to at least RTM, DNX will no longer be supported so you can expect build failures of all kind.

No worries !!!

On September 13th the team released a minor patch to version 1.0 so now the current version is 1.0.1.

As always the easiest way to update is to make sure you have the latest from getasp.net. By following the instructions in step you are sure to be on latest versions


Alright so today I needed to do some debugging on a website that was deployed on Azure since I could not reproduce the bug locally. Using Visual Studio I was able to get my debug session running in seconds. Here's how I did it:

  • Using the Server Explorer view I connected to my Azure Subscription
  • Right-click on the website that needs debugging and chose Attache Debugger
  • VS got to work........... for some time then it started telling me that my DLLs would not disassembly since they were not PDBs found (side note...when deploying a website with Azure CD it always use Release environment)
  • Went back to the portal and added this app settings: SCM_BUILD_ARGS => /p:Configuration=Debug
  • Went to the deployment blade and from the active deployment I clicked redeploy
After the re-deployment was finished I attached the debugger the same way I did before and that was it.... I could see exactly that thing I forgot to write a unit test for :(. Gotta go fix it now

until then




I know this subject has been covered extensively, but I wanted to do a simple how to, for the fact that it is … simple.


New Azure Website

In Azure when creating a new CUSTOM website, you will find a checkbox at the bottom "Publish from source control"…check it. This will give you the option of choosing your source control provider, after choosing your provider depending, on which on it is (in my case Github or Bitbucket), then select the repository and then you must select which branch you want this website to be on.

That's it!

If by mistake you chose the quick create …no worries goto Existing website.

Existing Website

From the dashboard of an existing website look for "Set up deployment from source control", click it. You will then have to choose which one is your provider, depending on which it is (in my case Github or Bitbucket), then select the repository and then you must select which branch you want this website to be on.

That's it!

Once your website is setup for source control deployment, ANY commit that you do in this repositor/branch will now trigger a deployment of your website.

For the last few weeks I've been feeling a bit nervous with my laptop, the one I use for work and conferences, something was off, sluggier, bloated. Why worry, we have each others back, I'm not going to wipe 4 years of beautiful memories just to get a slimmed down versions (I'm a loyal guy!). The cherry on top happened last Monday at MSDEVMTL, I wanted to show something on the big screen to the audience, so I went to plug the HDMI cable in (the same way I always do) and bang! it happened....blue screen of death (the new one from windows 8...less scary) with a smiley face...ARE YOU KIDDING ME...smiley face in a time of national crisis (ok I admit, I may overreact sometimes). From there everything got more and more awkward between us. After a reboot, Skype for business would stay stuck on the "Starting...." screen and some programs would all of a sudden crash big time.
So I decided that I had no choice but to wipe it and start fresh :(.

A new day

After re-installing Windows 8.1 and EVERYTHING (all the updates and all the apps I use) I tried to start Skype for business... same thing, stuck on "Starting ... " open up sourcetree...crash after less than a minutes, I could not even get Visual Studio 2013 to get past the splash screen without crashing and burning. I was kinda of stuck, but I had a big desktop computer at work...so at least I could still work with this one and get a new laptop soon. I did try a few more times to re-install Windows 8.1 with the bare minimum and nothing would work every app would end up crashing.

A new day .... again

After a few tries I just decided to give up, but then it came to me ... Windows 10 is officially out, might as well give it a go it really can't get worse than that. So I went ahead and installed it, everything went smooth and all of a sudden my dead laptop was snappy and shiny !! But since I was a week of BSOD hell ..... my work desktop (which as only a few months of work done) just went ahead and decided to crash and burn majestically, I mean like a champion ... it took the IT tech more than an hour to get it back up... I'm guessing I had bad karma this week.

Going forward

I really like how snappy the new Windows 10 is, it actually feels like my old computer on Windows 10 is faster than when it was on a brand new Windows 8.1. I t takes a bit of getting used to with the interface and the damn "Start button", but other than that I love it! I'm running VS2013 and VS2015 and I don't feel like I'm asking to much to my computer when I run multiple instances of each...good things. So all in all it looks like I will be on Windows 10 from now on... don't worry if things start to crash, I'll let you guys know :)