There’s an update of the beloved TFS Build Status Screen tool. And the most frequently asked feature is now built-in: Scaleability.
You can scale the status screen now to fut even on the smallest screens…hurray!
Source: http://raquila.com/software/team-foundation-server-build-notification-screen/
Oh dear. Another hyped protocol/platform from Google… oh wait. It’s not from Google. It’ all started in Xerox PARC…
There are several papers that describe what Google now claims to have developed…
left: Xerox PARC Paper; right: Google Wave
Conclusion: Go and read old Papers. As it turns out almost all newly hyped things have been described in papers from years ago.
Source 1: http://www.waveprotocol.org/whitepapers/operational-transform
Source 2: http://doi.acm.org/10.1145/215585.215706
We’re currently running several build processes. So each time someone checks new code in one of the build machines gets the whole package and builds it, runs tests on it and stores the result of this whole process on the Team Foundation Server. Great stuff so far.
Until you start to do things like automated WCF Testing. We’re using the selfhosting capabilities of the WCF to start a ServiceHost and then run tests against it. This works great locally. It does not on the build machines. Even if you promote the Build-Service User to Administrator you won’t get the love.
The error you might get would look something like this:
The exception contains an URL which tells you to add the Service URL to the machines URL Access Control List. On Windows XP and 2003 you have to install the Windows Support Tools and use the httpcfg command. On Windows Vista and 2008 you should use the already installed netsh commandline tool.
Since we need to get this to work on all current and future build servers I decided to add the netsh call to the build script, which looks like this:
Add this Target before any tests in the .proj file and you’re set.
Source 1: http://go.microsoft.com/fwlink/?LinkId=70353
I had to transfer some data the last days and I wanted to do it fast, encrypted and using only one tcp port. SFTP is one of those protocols that come in handy in these cases.
Since the machine that would host the SFTP service is a Windows machine I reached out to find a free, reliable and easy to install and use SFTP Server.
I found Core FTP mini-sftp-server. It’s a small download of just one .exe file. When you start it up it’ll show the dialog above. You can configure username, password, port and path. Click “Start” and off you go. Works as advertised.
Source: http://www.coreftp.com/server/
” border=”0″ alt=”