Vince365

    • 30/6/2014

    Migrating Team Foundation Server 2010 to Visual Studio Online: difference of process model

    Context

    In my company (www.negotium.com ) we are trying to achieve a significant migration for us people of development: TFS 2010 to visual studio online (ex tfs online).

    This will bring many new opportunities and tools to our way of developing and it will allow our IT Department to decommission a (several in fact) machine. I'm preparing a more complete article on the benefits of the solution online from the online edition.

    Between TFS 2010 and VS Online we had:

    • TFS 2012

    • TFS 2013

    Tools

    We are talking about a migration of 3 versions (it depends on how we count there). I would like to say that we use this free migration tool http://www.opshub.com/main/index.php/products/vsomigrationutility

    Other information to be taken into account, we are interested by the migration of the work items (tasks, bugs...), security and source control (including notes, links etc). Build plans will have to be redone anyway and deployments/test agents will be managed by VSO / Azure.

    Differences between models

    We however had difficulties during our migration tests: differences between models of organizational processes (the thing you choose at the beginning of the creation of a project) between the version on prem and online.

    The solution is pretty simple, but it took us time to find it so I post here in case that makes you save some. I would like to thank Jérémie who is working with me on this migration project.

    We only had to rename existing fields so that they match the naming convention used on VSO before migrating. Info: TFS power tools have a feature for it but because it was system fields, we had to do it in command line. (you must of course be the tfs server admin)

    witadmin changefield / collection: http://negotiumtfs:8080/tfs/DefaultCollection / n: System.HyperLinkCount/name: "Hyperlink Count"

     

    more information here

    http://msdn.Microsoft.com/en-us/library/dd236909.aspx

     

    Once this done on faulting fields we could go on our tests.

    I will keep you informed if we ever meet other difficulties.

    • 27/6/2014

    Availability of office 365 Samples and SDK on Github

    For those who have not seen it yet Microsoft teams who work on Office 365 have created a hub on GitHub.

    https://github.com/officedev

     

    What are you going to find there?

    • Examples of code made by Microsoft and the community

    • Demonstrations presented during the sessions from Microsoft and the community

    • Part of the 'documents' sources for the MSDN documentation

    • SDK for 'third' platforms (IOS, android...)

     

    The message behind that is Microsoft is investing in the community and wants to create a single place where developers (from any platform) can meet to participate in the projects together and share content. Therefore do not hesitate to have a look and to submit content / patches / projects.

    Check out http://dev.office.com too!

    • 23/6/2014

    The roadmap for Office 365 is available

    For those who are interested in knowing what's upcoming on office 365, Microsoft recently shared publicly the roadma.

    You can see what Microsoft's teams are developing directly from this page, which will be updated on regular basis http://office.microsoft.com/en-us/products/office-365-roadmap-FX104343353.aspx

    screen roadmap

    • 6/6/2014

    Selected for SharePoint Saturday New York City

    Hi Everybody!

    I’m pleased to announce you that I’ll be speaking at SharePoint Saturday New York City.

    The event is free and will occur at Microsoft New York City’s office, on time square.

    Check it out, is a very good opportunity to learn plenty of things if you can be there.

    http://www.spsevents.org/city/NYC/NYC2014/sessions

    See you soon!