I am speaking at Gravitas’s Tech Talk #3 - “TFS & Visual Studio 2013 vs The Rest” on Tuesday march the 4th about “Microsoft’s Application Lifecycle product has had a lot of changes in the past couple of years. In this session will look at how it can be used provide a complete solution from project inception through development, testing and deployment for project both using Microsoft and other vendor technologies” ...
The GDR3 update for my Nokia 820 has at last arrived. As my phone is a developer unit it is at the end of the automated update list. I suppose I could have pulled it down by hand, but I was not in a major rush as I am not doing WP8 development at present. The update seems to have gone on OK. Only strange thing was I was getting low space warnings prior to the upgrade. I suspect this was the fact the new patch had been download onto the phones main storage, but this was a bit full of content from iPodcast (the otherwise excellent app I use for podcasts can’t store to my SD card). Just to be on the safe side I uninstalled iPodcast, did the GDR3 update and then reinstalled iPodcast. As I have the premium version I could easily restore my podcast lists, including what I had and had not listened to, from the cloud. ...
All has been going well since our upgrade from TFS 2012 to 2013, no nasty surprises. As I had a bit of time I thought it a good idea to start the updates of our build and lab/test systems. We had only upgraded our TFS 2012.3 server to 2013. We had not touched our build system (one 2012 controller and 7 agents on various VMs) and our Lab Management/test controller. Our plan, after a bit of thought, was to so a slow migration putting in new 2013 generation build and test controllers in addition to our 2012 ones. We would then decide on an individual build agent VM basis what to do, probably upgrading the build agents and connecting them to the new controller. There seems to be no good reason to rebuild the whole build agent VMs with the specific SDKs and tools they each need. ...
We are testing the ‘social publish’ plugin for BlogEngine. Rik’s post has the details on what needs to be done to get it working with the current Twitter APIs
Update 27 Jun 2013 See update version of post with more data I seem to be involved with a number of TFS 2010 to 2013 upgrades at present. I suppose people are looking at TFS 2013 in the same way as they have historically looked at the first service pack for a product i.e: the time to upgrade when most of the main issues are addressed. That said TFS 2013 is not TFS 2012 SP1! ...
We have eventually got around to the 2013 upgrade of our production TFS server. It had been put off due to some tight delivery deadlines around Christmas. The upgrade went fine, unlike out some previous ones we have had. The upgrading of our team process templates, to add the new features, was greatly eased by using Feature4Tfs tool on CodePlex. This meant one command line call and all the projects were done (we had no significant process customisation) as opposed to visiting in team project in the admin console. ...
I am upgrade an internal system from .NET 4.0 to 4.5 so that I can use the Team API features in TFS. The system is based around a WCF web service that links our customer help desk system to TFS to keep bug reports in sync. It uses Entity Framework to access our help desk SQL DB. When I changed the targeted .NET framework for the WCF project, I started to get warning to update the Nuget managed references for EF, which I did. ...
Just had a problem with a TFS 2012 Lab Management deployment build. It was working this morning, deploying two web sites via MSDeploy and a DB via a DacPac, then running some CodedUI tests. However, when I tried a new deployment this afternoon it kept failing with the error: The deployment task was aborted because there was a connection failure between the test controller and the test agent. If you watched the build deployment via MTM you could see it start OK, then the agent went off line after a few seconds. ...
I posted yesterday that we had upgraded to the current version of BE 2.9. We, as you might expect, had a few minor issues, but I must say the support on the discussion forums has been excellent. This included the problems I had that were down to missing files and web.config issues (basically my copy errors when moving content from our BE 2.8 instance to the new BE 2.9 on) and a genuine bug in the new CustomFields code (fixed in 2.9.0.3). All discussion posts were responded to, and in the case of the bug fix, within a very short period of time. ...
I have just upgrade our Blog Server from BlogEngine.NET 2.8 to 2.9, all seems to have gone well, as before basically it is just copies files and adds s table to the DB schema, so… backup your blogs folder and SQL DB in case of problems delete the contents of the blogs folder copy in the the new release from the zip run the SQL upgrade script on your DB fix the SQL connection string in the web.config copy in the theme and extension files you were using as detailed in the release notes, but I found using updater utility did a great job for me As many of our sites were using the standard theme, it picked up the new bootstrap based version. Anyone with the other themes just see what they saw before ...