Anything older than five minutes? I've been a Silverlight developer for 5ish years. Something I've noticed in Perth (there never was a big demand for it, it was there but not like Melb/Syd) now that Silverlight is abandoned (the perception of abandonment in any case) is that the roles being advertised is all web/MVC stuff in the .Net world. Heck today I even saw an ad where the project is to migrate their GIS project from Silverlight to HTML5.
My comments were directed (and I'm so glad you are on the list, some of you listen) at Microsoft company, not Microsoft people. Someone there makes decisions and what we see out here is often weird when we don't see the why. Often too, the dissatisfaction comes not from what Microsoft are doing, but what they aren't doing when compared with others. (The Googles and Apples of the world). Perhaps its just grass is greener. Now I'm sat here thinking, geeze man, don't make me justify/validate my comments. lol Maybe its a rant. Getting back to the actual original issue, migrating from TFS server to TFS server is not trivial. It's not like its someone elses product being dealt with either. There, rant justified! ;) On Wed, Feb 12, 2014 at 1:11 PM, David Kean <david.k...@microsoft.com>wrote: > (We code a lot J) > > > > As a matter of interest, by "old" stuff what are we referring to? > Stephen/Grant what technologies/versions are you working with? > > > > *From:* ozdotnet-boun...@ozdotnet.com [mailto: > ozdotnet-boun...@ozdotnet.com] *On Behalf Of *Stephen Price > *Sent:* Tuesday, February 11, 2014 8:50 PM > > *To:* ozDotNet > *Subject:* Re: Migrating TFS > > > > Unfortunately, I agree. > > > > I do see some work done on things like ASP.Net (in an MVC focused world). > It would be nice if they did focus on the old stuff as much as the new but > I guess they have to balance things. No point in supporting old things that > no one uses any more. > > Software moves so fast, they invent things faster than anyone can learn > it. The bleeding edge hurts, always having to solve problems no one has hit > before. The old stuff is boring and has been done to death. > > That said its the boring stuff that makes up 80% of the code so you can't > ignore it. > > > > Microsoft, if you are listening, you have some damaged reputation that > needs repairing. Do you even code? (hehe. I was going to write do you even > lift?) > > > > They need to speak with Greg K, I'm sure he has a few things to say about > the matter. ;) > > > > > > On Wed, Feb 12, 2014 at 12:42 PM, Grant Maw <grant....@gmail.com> wrote: > > Update : the TFS Integration tool has proven to be completely useless. > It just doesn't do what it says on the tin, not in this case anyway. Even > when I could get it "sort of" working it kept throwing inexplicable > exceptions. > > I'm migrating the current cut of the source code manually and recreating > my branches. We'll lose our history, but better that than wasting days on > end fighting with these 2nd rate tools. > > If Visual Studio itself wasn't the best IDE out there, we would migrate > away to other platforms I think. Developer support in general just isn't > good enough within Microsoft any longer, and unless you are working with > the latest shiny new thing they don't seem to care. > > > > On 12 February 2014 09:18, Grant Maw <grant....@gmail.com> wrote: > > Thanks all for the responses. Ran a test yesterday and it failed due to > a one file in our project which it kept getting stuck on, trying over and > over again to process this file but it kept on failing. > > I removed this file from the project (it was non-essential and we can > re-add it again later if we need to), and tried again. This time it ran > through without errors and told me that it had finished, after about 10 > seconds! Needless to say that nothing was transferred. > > It seems I have more reading to do on this. But yes, I am also a bit > mystified at why they don't make it easier to migrate to the cloud > environment. Surely that would have to have been one of these first things > they considered. Wouldn't it? > > > > > > On 12 February 2014 05:31, Paul Glavich <subscripti...@theglavs.com> > wrote: > > We moved from a 3rd party hosted full TFS instance to TFS Online however > we only use the work items, not source control(I prefer mercurial/git). > > > > It was a little painfull as we had used some customisation to > fields/templates. > > > > However, it was **mostly** ok (if a little time consuming). I just got > the entire backlog into Excel. Did the same the TFS online, copy common > fields from one excel sheet to another, publish to TFS online. This got us > an easy 80-85% there. Other stuff was customised or had some other > weirdness we had to look into but not too bad. We kept the old instance > going while we did some sanity checks and ensured all was ok. > > > > BTW, TFSOnline is great. Love the web interface and use it instead of the > VS integration. > > > > - Glav > > > > *From:* ozdotnet-boun...@ozdotnet.com [mailto: > ozdotnet-boun...@ozdotnet.com] *On Behalf Of *Stephen Price > *Sent:* 11 February 2014 6:57 PM > *To:* ozDotNet > *Subject:* Re: Migrating TFS > > > > Grant, > > I did a migration from a one TFS server to another and it was a horrible > experience. I don't recall the tool I used but I had the added complication > of using a different Template on the destination server and it was trying > to migrate loads of mismatching fields. The source control was ok and > history seemed to work. The work items were sketchy with lots not migrated. > We ended up keeping the old TFS server about in read only for reference. > > > > Good job going to the cloud, I use Visual Studio online for my own stuff > and its brilliant. Shame they don't make it easier to migrate into. > > > > cheers, > > Stephen > > p.s. if you need help with it let me know ;) > > > > On Tue, Feb 11, 2014 at 1:48 PM, Grant Maw <grant....@gmail.com> wrote: > > Thanks Anthony. We're not worried about work items, just source code and > history at this point, including branches. The TFS Integration Platform is > beavering away as I write this (trying it out on a test copy of the > project), telling me that 176 of 335 change groups have been migrated. > > I guess I'll just let it run and see where it lands me. > > > > On 11 February 2014 15:40, Anthony Borton <antho...@enhancealm.com.au> > wrote: > > Hi Grant, > > > > I moved a client with around 35 team projects from an on-premises TFS up > to Visual Studio Online using the TFS Integration Platform. I was pretty > lucky in that they only needed the source to go up and didn't have work > items to work about. The process was quite a bit more time consuming than I > had planned and it was a seemingly never-ending exercise in massaging > settings to get the source (with history) from each TP up to the cloud. A > future TFS 2013 update should include a feature to help move data from VSO > down to TFS but I haven't heard if there is anything there to help go the > other way. > > > > Cheers > > > > Anthony Borton > > Senior ALM Trainer/Consultant > > Visual Studio ALM MVP > > Enhance ALM Pty Ltd > > > > *From:* ozdotnet-boun...@ozdotnet.com [mailto: > ozdotnet-boun...@ozdotnet.com] *On Behalf Of *Grant Maw > *Sent:* Tuesday, 11 February 2014 3:07 PM > *To:* ozDotNet > *Subject:* Migrating TFS > > > > Hi All > > Has anyone moved from on-premises TFS to visual studio online? We have a > large solution, including branches, that needs to be pushed into the cloud > as soon as possible and I'd love to hear any war stories before I start. > > I'm thinking about using the tool at http://tfsintegration.codeplex.com/. > > Cheers > > Grant > > > > > > > > > > >
