Visual Studio Live Azure DevOps Hyper 365 .NET
-
- Visual Studio Online
- Visual Studio Team Services
- Azure DevOps
- Work is now Boards
- Build and Release is now Pipelines (with Artifacts tossed in)
- Code is now Repos
- Team Foundation Server is now Azure DevOps Server
- None of these are in any way related to Azure, and Azure DevOps Server is not actually in the Azure cloud.
-
Just wait until we get to AzureHub.
-
It took far too long after the initial announcement for me to find that Repos will in fact still support TFVC. They were all so happy about Git that they seemed to be ignoring those of us who actually need to keep our source control history.
(In addition to our current collection going back to 2012, we have two read-only historical collections due to botched "upgrades" where they started fresh instead, plus a read-only VSS instance that really needs to be converted at some point. There's at least ten years of history in there, probably closer to fifteen or more. And they think that converting only 180 days of history to Git is sufficient?)
-
Is this really GA or "Microsoft" GA?
-
@Unperverted-Vixen said in Visual Studio Live Azure DevOps Hyper 365 .NET:
And they think that converting only 180 days of history to Git is sufficient?
I sense surprise in your tone.
-
"Visual Studio Live Azure DevOps Hyper 365 .NET"
Where can I get this? This looks like it would solve all my problems forever.
-
@stillwater said in Visual Studio Live Azure DevOps Hyper 365 .NET:
I sense surprise in your tone.
Given all their efforts to keep Windows bug-compatible with decades-old applications, I don’t understand why they think users don’t care about decades-old data. (Or even year-old data.)
-
@Parody said in Visual Studio Live Azure DevOps Hyper 365 .NET:
Just wait until we get to AzureHub.
Would that be a site for sharing code or for sharing videos?
-
@Unperverted-Vixen said in Visual Studio Live Azure DevOps Hyper 365 .NET:
@stillwater said in Visual Studio Live Azure DevOps Hyper 365 .NET:
I sense surprise in your tone.
Given all their efforts to keep Windows bug-compatible with decades-old applications, I don’t understand why they think users don’t care about decades-old data. (Or even year-old data.)
Microsoft knows users do care about decades old data. They just dont give a fuck about what users want. They just wanna move fast and break things all the fucking time. Microsoft is the new Angular! SMH!
Oh, Also let's all enjoy broken links in the documentation everywhere along with the new documentation constantly changing with github issues logged against each page.
I hope to god you don't get to work with anything the new microsoft comes up with. The old MS was supposedly evil but atleast they did not fuckup things this bad.
-
@ben_lubar said in Visual Studio Live Azure DevOps Hyper 365 .NET:
Would that be a site for sharing code or for sharing videos?
You've got a lot to catch up on when it comes to MS. AzureHub is for putting IOT Container deployments in a online collaborative code repo that runs on a kubernetes cluster inside Azure AppFabric across multiple AZs.
INB4 someone tells me the verbal diarrhea above is actually possible.
-
@stillwater said in Visual Studio Live Azure DevOps Hyper 365 .NET:
INB4 someone tells me the verbal diarrhea above is actually possible.
Apart from the IOT part, I'm pretty sure I've seen that exact sentence advertised somewhere.
-
You forgot 'Core'.
-
@TwelveBaud said in Visual Studio Live Azure DevOps Hyper 365 .NET:
Azure DevOps Server is not actually in the Azure cloud.
Uh what? Did you not notice the day long
VSTSAzure DevOps outage last week when Azure US South Central went down?
-
I'm not sure what's cloud and what's not anymore.
-
@TwelveBaud If I have to re-do my build and release configurations I'm going to be very angry. I JUST got them working and correct.
-
@stillwater said in Visual Studio Live Azure DevOps Hyper 365 .NET:
"365"
Where can I get this? This looks like it would solve all my problems forever.
Except on leap years.
Oh wait...
Yes, Microsoft Azure Was Downed By Leap-Year Bug
Microsoft has confirmed that Wednesday's Windows Azure outage that left some customers in the dark for more than 12 hours was the result of a software bug triggered by the Feb. 29 leap-year date that prevented systems from calculating the correct time.
-
@TwelveBaud said in Visual Studio Live Azure DevOps Hyper 365 .NET:
Work is now Boards
Build and Release is now Pipelines (with Artifacts tossed in)
Code is now ReposThat sounds on fleek, radical
-
@stillwater said in Visual Studio Live Azure DevOps Hyper 365 .NET:
This looks like it would solve all my problems forever.
But it doesn't have blockchain!
-
@izzion
TFSAzure DevOps Server isn'tVSTSAzure DevOps. (LOL, ADO).
-
@lolwhat said in Visual Studio Live Azure DevOps Hyper 365 .NET:
@stillwater said in Visual Studio Live Azure DevOps Hyper 365 .NET:
This looks like it would solve all my problems forever.
But it doesn't have blockchain!
Isn't "no blockchain" a good thing?
-
@lolwhat said in Visual Studio Live Azure DevOps Hyper 365 .NET:
@stillwater said in Visual Studio Live Azure DevOps Hyper 365 .NET:
This looks like it would solve all my problems forever.
But it doesn't have blockchain!
He wrote "solve", not "create" problems
-
Microsoft changing product names constantly for no reason? Shocking.
Can't wait to sign in with my .NET passport.
-
@lolwhat
I missed that.
-
@Unperverted-Vixen said in Visual Studio Live Azure DevOps Hyper 365 .NET:
I don’t understand why they think users don’t care about decades-old data. (Or even year-old data.)
You silly billy! Everyone knows developers aren't users. Their brains work differently. That's why development tools don't have to follow any of the "user experience" rules, like discoverability or stability. Developers will just figure it out.
-
@stillwater said in Visual Studio Live Azure DevOps Hyper 365 .NET:
Oh, Also let's all enjoy broken links in the documentation everywhere
At least some things never change.
-
@marcodave Welcome back!
-
@blakeyrat said in Visual Studio Live Azure DevOps Hyper 365 .NET:
If I have to re-do my build and release configurations I'm going to be very angry. I JUST got them working and correct.
If it's a "vNext" build, you're fine. They're adding some stuff to on-premises that's been in VSTS for a while (YAML import/export), but they aren't moving on to build system #4 yet.
I haven't seen confirmation on whether XAML is still in or not. (TFS 2018 removed support, but one of the service packs added it back in.)
