There's just one week left for MVPDays Community Roadshow in Toronto!
We would love to see you there!
Please use the Promo Code "CDNMVP" to register for FREE !
Make Web Not War brings together Canadian web dev experts to talk about modern web standards, Open Source, and Open Data innovations. Learn about the latest IETF & ECMA web standards, how to run and contribute to open source projects, the importance of open data in the world of journalism, open government, and more. Live online Feb 5, 2016. Participation is free. Register to receive exclusive content to accompany the live presentation.
Awesome apps are built a certain way – that way may be different for each and every one of us. On February 10, Microsoft DX is coming to Toronto with Let's Dev this Tour to help you learn how to build awesome apps for web, cloud and Windows 10 using latest standards and tools. The day will be full of great workshops, hands-on-labs and consultations with experts.
1 DAY. 1 VENUE. 3 DEEP DIVE WORKSHOPS – WEB. CLOUD. WINDOWS 10.
Pick a primary workshop, then pop in and out of all three based on the topics that interest you the most.
The boundless web
Build across browsers, devices, and the cloud.
Sessions and hands-on labs on the latest dev standards and tools‚ Web Apps with Node.JS‚ and Azure.
The fusion of apps and the Cloud
Magic happens when the technologies that you love live on Azure.
Sessions and hands-on labs on App and Data Services‚ VMs, and networks.
One app fits all
One app can fit them all
– mobile, tablet, and PC
– with Windows 10.
Sessions and hands-on labs on Adaptive UX‚ the Universal Windows Platform‚ speech recognition, data binding‚ and Azure.
SPACE IS LIMITED per workshop so please reserve you seat now.
Getting Azure Automation runbooks to shut down your virtual machines (or turn them on) automatically is not new. There are a lot of scripts out there that could do it for you. You can also write one yourself. It's not that complicated. I did it J Just kidding…
There are a couple of ways my PowerShell scripts are different:
- First, the scripts that automatically start/stop Azure virtual machines take the weekend into account. Scripts will not turn your machines on or off on the weekends. After all, you probably do not want to automatically turn on your virtual machines in Azure early in the morning on the weekend, just so that you can turn them off at the end of the day on the weekend. Seems like a waste, right? Anyways, this small change should save you a few bucks.
- Second, the scripts adjust the schedule from UTC to the time zone you need. It looks like when the scripts that are part of Azure Automation runbooks run, they use UTC time. So, if you're in Toronto, script will think that the weekend starts 5 hours earlier. It's not bad, I guess. But, it also means that the weekend will end 5 hours earlier, and that just not right and need to be fixed.
Below is a code snippet that makes the above mentioned happen:
$UTCTime = (Get-Date).ToUniversalTime()
$TZ = [System.TimeZoneInfo]::FindSystemTimeZoneById("Eastern Standard Time")
$LocalTime = [System.TimeZoneInfo]::ConvertTimeFromUtc($UTCTime, $TZ)
$day = $LocalTime.DayOfWeek
if ($day -eq 'Saturday' -or $day -eq 'Sunday')
Write-Output ("It is " + $day + ". Cannot use a runbook to start VMs on a weekend.")
The complete scripts that start or stop Azure virtual machines can be downloaded from OneDrive. Enjoy.
So, you have installed Git client and trying to connect to Git server (on Visual Studio Team Services, Github, or whatever), but you're getting "fatal: unable to connect a socket (Invalid argument)" error. One of the reasons could is that you're behind the proxy. For example, you're at work and your employer requires all internet traffic to go through the proxy. ~/.gitconfig global config file is the key here. In this case, to get Git client to work with the proxy, you need to configure http.proxy key in git config using one of the following commands:
git config --global http.proxy http://proxyuser:firstname.lastname@example.org:8080
git config --global https.proxy https://proxyuser:email@example.com:8080
- change proxyuser to your proxy user
- change proxypwd to your proxy password
- change proxy.server.com to the URL of your proxy server.
- change 8080 to the proxy port configured on your proxy server
If you do not need to authenticate to proxy, then just specify proxy server name and port number and skip proxy user and password.
If you decide at any time to reset this proxy and work without (no proxy), use one of the the following commands:
git config --global --unset http.proxy
git config --global --unset https.proxy
Finally, to check the currently set proxy, use one of the following commands:
git config --global --get http.proxy
git config --global --get https.proxy
By the way, to retrieve the proxy settings you're using, you can use one of the following commands:
reg query "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings" | find /i "proxyserver"
netsh winhttp show proxy
That's all I got to say about Git and proxy server.
I was recently having trouble generating some Release Notes for a current project that is using
Visual Studio Online Visual Studio Team Services. With Git as our backing source control system there didn’t seem to be an easy way to see what Work Items were going into a release. Thankfully we are associating Work Items with commits which makes the following Powershell script work.
Passing in our current release branch, and our previous release branch we can isolate the new commits and then parse their commit messages looking for the “Related Work Items:” text that Visual Studio appends to commits. Once we have those WorkItem ids we can use the TFS api to get some info about them and create some release notes.
You can find the script on GitHub.
MVPDays is a series of one day events that focuses on content for IT and Dev Professionals sharing their knowledge allowing local communities to learn more and advance their skills based on real world experiences. The majority of the sessions are Content will focus on the following topics:
- IT PRO
- SharePoint / Office 365
It will be held in the following cities:
I recently had an interesting experiencing writing post build PowerShell script for a client. The client wanted to check in certain files into source control after the build is finished. Sounds easy, right? You can use either good old tf.exe command line utility from Visual Studio command tools. Or, you can use something more current like PowerShell to write a simple script that will check in pending changes for you. The problem is that the client also wanted to associate work items with the check in. Not a big deal, right? Well, apparently it is a big deal. You cannot associate work item with the check in using tf.exe command tool. And, what's even stranger, I could not find a way to associate work item with the check in using PowerShell. I got stuck with figuring out how to make WorkItemCheckinInfo parameter in Workspace.Checkin method to work properly.
This is how I learned that apparently you can associate work item with TFS check in, but you have to use tf.exe command from Team Explorer Everywhere. Apparently, even though the names are the same, those are very different command line utilities. When you use tf.exe from Team Explorer Everywhere, you can associate work item with the check in using a simple command:
tf checkin ItemSpec -associate:WorkItemIds
It's that easy. I just wish –associate option was available in common tf.exe command from Visual Studio command tools. I would also wish that those two seemingly identical tf.exe commands would actually do the same thing (the same way), or at least that those commands would have different names to avoid the confusion. By the way, there are also other differences between those two commands with the same names. You can get them form the links provided in the post. I'm too upset to list myself L