Latest / Microsoft Cloud IT Pro Podcast / Episode 355 – SharePoint Framework On-premises is a Moving Target (with Andrew Connell)
Transcript
- 0:03Welcome to episode 355 of the Microsoft Cloud IT Pro
- 0:08Podcast recorded live on September 29th, 2023.
- 0:12This is a show about Microsoft 365 and Azure from the perspective of IT pros and
- 0:17end users where we discuss the topic or recent news and how it relates to you
- 0:21after only a short time since having him on the show the last time,
- 0:25we welcome Andrew Connell back to discuss some discoveries he made in the
- 0:3023 H two update for SharePoint server subscription edition
- 0:34related to S P F X, while he's a developer.
- 0:38And S P F X is the SharePoint dev platform.
- 0:41This discovery could also have a big impact on IT.
- 0:44Pros that have deployed or purchased custom S P F X solutions to their
- 0:49on-prem environment. We have a voice that joined us. Again,
- 0:54we have Andrew Connell back on the podcast with us
- 0:59to have an interesting conversation. Before that though, ac,
- 1:03do you want to introduce yourself? If people are new,
- 1:05I would imagine you've been on the show enough that most people have heard you
- 1:10and know of you, but just in case this is their first time, hey, it's always.
- 1:13Good to reach out and find new people that I haven't talked to before or
- 1:17haven't, haven't engaged with. Yeah, so thanks for having me. Again,
- 1:21I'm Andrew Connell. I am primarily a developer.
- 1:26I am a developer, I should say not primarily . I am a developer,
- 1:29specifically like a full stack developer focusing on the Microsoft 365 and Azure
- 1:33side. So long history with SharePoint teams development,
- 1:38Microsoft teams development, Azure development, all that kind of stuff.
- 1:41I've been doing SharePoint for 20 some odd years. So that's my song and dance.
- 1:46And I guess you'll have like my contact info,
- 1:48easy to find me in the easy to find me online.
- 1:51You search for Andrew Connell and SharePoint,
- 1:52you'll have no problem finding me or just go to andrew connell.com or Andrew
- 1:56Connell on Twitter or on LinkedIn or whatever. I'm, I'm everywhere.
- 1:59Yes, you are everywhere. But that SharePoint development,
- 2:03so this kind of all came about, I think it was like a week ago or so,
- 2:07two weeks ago as a developer,
- 2:09you were paying attention to some release notes on
- 2:14SharePoint,
- 2:15on premises and saw something that popped up at you and
- 2:20you sent me a message and said, Hey Ben, do you know anything about this?
- 2:24And through a bunch of dialogues,
- 2:27this whole topic came up that you discovered it from a developer perspective.
- 2:32And I was like, you know, from an admin perspective,
- 2:34this is probably kind of important for admins to know as well,
- 2:38which is kind of how this show came to be.
- 2:41And Scott is completely in the dark because you and I colluded to completely
- 2:45catch Scott off guard on our topic for today.
- 2:49Can I just say though, like I'm really prepared. So I brought my ice tea today,
- 2:53, it's in my SharePoint Saturday Cleveland Glass. So I'm already,
- 2:57I have a pint of iced tea and I'm ready to sit back and just listen to the two
- 3:01of you. I don't know, talk about SharePoint garbage.
- 3:04I should be way out of my element here because this is gonna be not only
- 3:08on-prem, which I don't touch. Mm-hmm. .
- 3:11And it also has something to do that I, like you said, Ben, I think it's got,
- 3:15it's going to impact people who manage on-prem SharePoint
- 3:20farms, specifically SharePoint subscription edition farms,
- 3:23because an update shipped about two weeks ago.
- 3:26And if you don't know what's going on with this,
- 3:28you very well do not want to install it right now. ,
- 3:30you wanna wait and find out how one,
- 3:32once Microsoft figures out what the heck they're gonna do about this,
- 3:34because yeah, I mean I looked at it from a developer's point of view and we'll,
- 3:37I mean, we'll dive into it. It's gonna be a little hard.
- 3:40There's a lot of version numbers gonna be thrown around here,
- 3:43but I will do my best. I will tell you that if you're sit,
- 3:46if you're not driving and you can get out a piece of paper and a pencil,
- 3:51I will give you the timeline and you'll be able to see why,
- 3:53how things are all kind of jacked up. But if you don't, don't worry.
- 3:56I'm gonna have a,
- 3:57I am gonna have an article on my site on my company site tonno.io,
- 4:01and I'm planning on doing a YouTube video for it as well that I'll publish.
- 4:06I guess this will, when the, when will this go out? Early October.
- 4:08When will this.
- 4:09I don't know, how's that for a horrible answer? Good.
- 4:12I think it'll go out like a week and a half from today.
- 4:15October 12th. There.
- 4:16You go. Ask Scott. He knows what's going on.
- 4:18So this,
- 4:19I will have an article in a video that will be live by the time this goes out.
- 4:23So you'll, so yeah, so if you,
- 4:25if you're having trouble like tracking and all that kind of stuff and
- 4:27everything, you just, you get the big piece.
- 4:28But I'll also have an article that'll, I reference all these things as well.
- 4:32So got my notes out of the article I have to write and that's what I was gonna
- 4:34talk about today.
- 4:35Alright, so yeah, this all started about, I'm trying,
- 4:40I'm looking back through our messages of when you first asked me,
- 4:42and I can't find it right now. It's like.
- 4:44Mid-September.
- 4:44Yeah. Was this really the very first? Oh yeah.
- 4:49So you sent me a message, this was on September 15th,
- 4:52so it was like two weeks ago. You said you, you sent me a message and said,
- 4:56have you been picking through the SharePoint subscription edition 23 H two
- 5:00update? And I was like, no. Do I need to, and you said, well,
- 5:04there's a mention in the announcements and docs about bumping support
- 5:09for S P F X to, do you want me to start giving some version numbers?
- 5:15Okay, so you start here. So then you said it was an S P F X,
- 5:19some changes to S P F X and you started throwing out a whole bunch of version
- 5:22numbers to me.
- 5:23So let me set some context first and because I think it helps to understand
- 5:28why this is a, well,
- 5:30this is potentially a B F D for for enterprises.
- 5:33So a really big deal because you could install this if you're in a certain
- 5:38state, you very well meaning that like we are fully patched,
- 5:42we're fully updated,
- 5:42and we have either bought some stuff from a vendor that installed that we've
- 5:47installed into our,
- 5:48our SharePoint server subscription edition tenant and or we've
- 5:52also got custom stuff that we've deployed. If you're in that scenario,
- 5:56this very well could, if you install this update,
- 6:00it could very well just break your form or break all of those components.
- 6:04And so that's why this is important. So yeah, like you said,
- 6:07I have a couple alerts and stuff that I track to see like, you know,
- 6:10any news that goes on like classic Google alerts for a bunch of different
- 6:13phrases that I watch. And I saw this one pop up that there was a h,
- 6:17there was a second half update in 2023 for SharePoint server subscription
- 6:21edition. Well go back and think like when SharePoint ser,
- 6:26first of all, today in SharePoint online, all of this kind of goes down,
- 6:29goes is centers around the SharePoint framework,
- 6:31which is what we use to build custom solutions for SharePoint today is the
- 6:36recommended way of doing it. While we have a bunch of other ways we could do it,
- 6:39this is the recommended approach and this is the way it's been also recommended
- 6:42on SharePoint on-prem for a couple years as well.
- 6:46And what Microsoft today,
- 6:48what we have in like SharePoint online is we're all the way up to version one
- 6:52point 18 of the SharePoint framework. But on-prem versions are way behind this.
- 6:57So like SharePoint Server 2019 and SharePoint server subscription edition,
- 7:01they're on version 1.4 0.1.
- 7:04And earlier this year when Microsoft shipped the first half update for
- 7:09S P S E, so that I'm going to, instead of saying the whole thing out,
- 7:12I'll just do the shorthand way. So SharePoint server subscription edition,
- 7:16SS P S E, they ship the first update out for this year.
- 7:19So it's referred to as 23 for 2023 and then H one.
- 7:23So for the first half of 2023. And that update,
- 7:25they kind of surprised people where they said previously they'd said,
- 7:28we're never gonna update the SharePoint framework on on-prem deployments.
- 7:32And in the update they ran, they did earlier this year,
- 7:34I think it was like March or April or May,
- 7:37they said we are updating the SharePoint framework to version 1.5 0.1.
- 7:42Okay. So that's a little number to write down there.
- 7:44So 2023 H one is SharePoint framework, 1.5 0.1.
- 7:48And SharePoint Online you said was 1.8, right?
- 7:5118 1.8.
- 7:52One point 18. All right. I'm throwing some of this,
- 7:55I'm throwing some of this in the chat too. Yeah.
- 7:56I'll actually, I mean, I meant to put the chat up, that's where we were like,
- 7:59say August. Oh, well, okay. But just say that's where we,
- 8:03that's where we are because one point 18 just came out,
- 8:05so it's really like one 17, but whatever. So when I saw this new,
- 8:09when I saw the update drop for the blog posts from Microsoft saying that they
- 8:13released H 2 20 23, that update for S P S E,
- 8:18they said that they had updated the SharePoint framework,
- 8:20or specifically what they said was they added support for a new version of React
- 8:25and a new version of Office UI fabric allowing developers to utilize these newer
- 8:29components in their SharePoint framework solutions.
- 8:32So that's really all they said in terms of what they did. Now,
- 8:35they did give a specific version of React and I'll come to in a minute,
- 8:38and a specific version of Office UI fabric that I'll come to in a minute.
- 8:41But they didn't mention what version of the SharePoint framework.
- 8:43And so the first thing that I went to, I was like,
- 8:46which version did you guys do? I'm surprised you didn't even,
- 8:48you didn't say this last time you did.
- 8:50So I started like poking around and I start, you know,
- 8:53trying to figure it out on my own. I've kept, so I'm a,
- 8:55I'm a SharePoint framework guy as like my primary business or has been for the
- 8:59last couple years. And so what I did is I went back and I looked at the,
- 9:04the spreadsheet that I keep for every release of the SharePoint framework and
- 9:08what's new, what's changed, what's deprecated version dependencies, blah,
- 9:11blah blah. And I saw that when, so one of the things that that,
- 9:15that this update did, is it update? They said that they had,
- 9:18they had updated the support for React Up to React version
- 9:2216. Well,
- 9:24the SharePoint framework started to support React 16 in version
- 9:281.7 0.1 of the SharePoint framework, sorry, 1.7 0.0.
- 9:33So I'm like, okay,
- 9:35so at least the SharePoint framework probably got bumped up to 1.7 0.0,
- 9:39but then went back and looked at, well, that's okay,
- 9:41so I saw you put in the chat,
- 9:42it's not totally right because that's not what Office Fabric,
- 9:45so just delete the office share fabric piece. And then I went and they said,
- 9:48well,
- 9:48the other part of their release was we also updated the office UI fabric to
- 9:53react version to Office UI fabric, react to version seven. Well,
- 9:58the SharePoint framework version that got that support,
- 10:01that version supported was the SharePoint framework, one point 12.1.
- 10:05So I looked at this and I'm like, well, that's interesting.
- 10:07So we're in this range of,
- 10:10probably they've updated the SharePoint framework to one point 12.1 so that they
- 10:13could support both of these versions.
- 10:16But that's a big jump from like 1.4 0.1 to the first half update
- 10:21was 1.5 0.1, and then the next, and then saying like,
- 10:24then they jumped all the way to one point 12.1. I'm like, holy crap,
- 10:27people are gonna love this. That's a, that's a pretty big jump. So I went,
- 10:30and I'm still trying to pick it apart. couldn't figure it out.
- 10:33So I sent a message to some friends over on the SharePoint framework engineering
- 10:38team, and I was like, Hey, so you guys know anything about this? What's up?
- 10:41And they came back and they're like, what? ,
- 10:43we've never heard of that , that's paraphrasing.
- 10:45That's exactly what they said. , do it again. They're like, how did you,
- 10:49how did this happen?
- 10:50So I'm gonna be a little careful on what I say because I don't think that some
- 10:52stuff is kind of public. So I'm gonna be, I don't know,
- 10:54I don't wanna throw too many people under the bus here.
- 10:56And the story is still kind of evolving, evolving. So I'm thinking like, okay,
- 11:00well this might make sense actually. The, the,
- 11:02when we create new SharePoint framework projects,
- 11:05use a thing called the yeoman generator to do that.
- 11:07And the last version of the yeoman generator that supported creating on-prem
- 11:10projects was one point 12.1. So I'm thinking, okay, this tracks,
- 11:13so it probably is, this is probably one point 12.1.
- 11:17So when I asked the people on the engineering team about this,
- 11:20they weren't sure what I was talking about. And they,
- 11:22they were not familiar with this. And so I was like, okay,
- 11:25well I actually wor I worked with the guy that did the documentation,
- 11:30the,
- 11:31the SharePoint development documentation for the H one update earlier
- 11:35this year. And so I reached back out to him. So he's on a team,
- 11:39I think he's on a team in China, I might be wrong with that, but I think he's,
- 11:42I, I believe he's from China. He's in China,
- 11:44or he worked some really terrible hours in in the United States, .
- 11:48And he, so he came back, he, he responded to me and he's like, yeah,
- 11:51so here's what we did, and I'm a little late on getting the PR to you,
- 11:55but let me get the PR done. And so I was like, okay,
- 11:58because one of the things I do on, and it's part of my, my work for Microsoft,
- 12:01so I don't work for Microsoft, but I do some contract work for 'em.
- 12:04And one of those is that I review all of the updates to the developer docs and
- 12:08for SharePoint development, and I also write a lot of the docs.
- 12:13And so he's like, well, I didn't get you the pr. And I was like, well, okay.
- 12:15So I go back and I look at the PR when the PR comes out, when he,
- 12:18he tells me it's, it's up there now.
- 12:20And suffice to say it didn't answer any questions and it created
- 12:26a lot more. So the PR is still public out there today. It's pub,
- 12:31it's pr uh, 92 15. It's in the SP dash dev docs.
- 12:36I'll grab a link to it and drop it in the chat for you guys. All right.
- 12:39This PR is, is still, it's live today. And it was,
- 12:43there's so much stuff in it that is like, gives you, like,
- 12:47you basically drop a lot of WFS as a SharePoint framework developer when you
- 12:51read the details of this pr that it was so much so that I went to the guy who
- 12:55actually wrote the PR and I cloned his forked repo so that when this PR was
- 12:58deleted, I had a copy of it on my machine . He,
- 13:01I figured that this is gonna be, this is gonna be deleted at some point.
- 13:03So the more I, the more I poked through it and the more I I,
- 13:07I saw what was going on, there's a lot of things that scares the heck outta you.
- 13:11Okay? And I'll, I'll get to what the, the,
- 13:13what my guidance would be for people today until Microsoft kind of steps up and
- 13:18clarifies what's going on.
- 13:20But I'll also tell you like what the implications are, uh,
- 13:23at least if things stay the way they are today.
- 13:25And the problem is that this isn't like a release candidate.
- 13:27This is like ga out in the wild. People have already started to apply this.
- 13:31So one of the things that this does is that what they talked about,
- 13:35that they changed the version of the SharePoint framework that's included in
- 13:3923 H two to version 1.5 0.0.
- 13:44Now, if you're keeping, if you're keeping score at home,
- 13:47I didn't say upgrade because that's actually a rollback .
- 13:50Yeah, it's, it's interesting like even the public docs today,
- 13:55'cause some of this stuff is out there and already floating.
- 13:58It's not like we're into a calendar year, 2024, any of that stuff yet.
- 14:04So they're very explicit that they come back down to things like
- 14:09V 1.5 or lower 1.5 0.1 to 1.5 0.0 or
- 14:14lower, which that's weird, doesn't comport, it's.
- 14:17Not only weird,
- 14:18but that the thing that scared the heck outta me with that one right off the
- 14:21bat, when I saw that, I was like, well, hold on a minute,
- 14:23what about customers who have upgraded their projects or rolled out 1.5 0.1
- 14:28projects and up, you know, upgraded new projects, whatever,
- 14:31that they did that off the H one update this year for S P S E that are now
- 14:36running a newer version of the SharePoint framework than what is even existing
- 14:40on the on in H two, right?
- 14:43'Cause for the last six, six months,
- 14:44they could have been writing stuff against 1.5 0.1, right? Ever since that.
- 14:48They could have been writing stuff for it, updating it,
- 14:50they could updated their projects, they could have bought a project,
- 14:53they could have bought a solution from one of those intranet in a box companies
- 14:56like, uh, Velo or somebody, I'm not saying Velo did this,
- 14:58I'm just using them as example , right?
- 15:00But they could have bought something and deployed it to their environment.
- 15:02Here's the thing, when you do this, 1.5 0.1 is no longer on the SharePoint, uh,
- 15:07S P S E. So without you changing your project,
- 15:10you have a reference in there in the, in the dependencies that say,
- 15:14go tells the SharePoint framework runtime on the page to go load this.
- 15:17And it goes out to go fetch that and pull it down from the on-prem server.
- 15:21If it doesn't exist, it's going to break, right? There's no way, there's,
- 15:25there's no bones about it. So that's a, that right there,
- 15:28that's a huge concern right off the bat.
- 15:31And so kinda the moral to that piece right there that is really
- 15:36confusing why they did this or what's going on is that if
- 15:40you just want, I wanted, like what I, I guess what I would tell admins on this,
- 15:43or it pros who are who are managing these farms,
- 15:46is if you have any customizations,
- 15:49if you have any custom SharePoint framework components,
- 15:51and that's not just the ones that you've built or you've contracted somebody
- 15:54else to build. If you've bought a product that has any UX to it,
- 15:58SharePoint framework is the way to implement the UX changes
- 16:03inside, uh, SharePoint today.
- 16:06And so there's a pretty good chance that those tools are using the SharePoint
- 16:10framework and they may have been upgraded to 1.5 0.1, and if they did,
- 16:15and you do, you upgrade to one point, well, if you upgraded H two two,
- 16:19then you're kind of screwed, right? So that's one,
- 16:23but that's not the part that like,
- 16:25that already raised like enough of like going what in the world? It's like,
- 16:27okay, you know, earthquake, everyone stop.
- 16:29Let's figure out what the heck's going on here, .
- 16:31But there's a couple other things that make this earthquake that make like the
- 16:33ca ca, California slide into the ocean that we're like, holy God,
- 16:36what in the world just happened?
- 16:38So when you dig a little bit deeper in that pr it walks through some details
- 16:42about, now here's how you, we, well, oh, sorry,
- 16:46this raised the flag with me after,
- 16:47after you saw this and you kinda like took stock of it.
- 16:49I remember walking away from my,
- 16:50from my desk after like sending the message to some people over,
- 16:53over the engineering team, like, what's up with this? So I walked downstairs,
- 16:57go to get some more, go to let the dogs out, get some water.
- 16:59And as I'm standing outside, while the dogs were, you know,
- 17:01walking in the grass for bed, it dawns on me. I'm like, wait a minute.
- 17:04They said that they upgraded to React 16 and to office UI fabric version,
- 17:07not version seven. They went backwards. How did they do this?
- 17:10Because the SharePoint framework, ,
- 17:12you couldn't upgrade version of React.
- 17:14You couldn't upgrade the fluent UI in your projects because of these dependency
- 17:17trees that they had. So I was like, how's that supposed to work? So of course,
- 17:21get the dogs back in.
- 17:21They were pretty ticked at me because they were only out for like two or three
- 17:24minutes, ran back upstairs, start digging into it.
- 17:27And I read more about the PR and the PR says,
- 17:29walks you through all of these steps,
- 17:31how to surgically go in and to add new packages in for the office UI fabric
- 17:36into your SharePoint framework project to be able to use the newer version of
- 17:40the office UI fabric and on how you can manually go through and upgrade to use a
- 17:45newer version of React. Now, those two things,
- 17:47they're already kind of like as a,
- 17:49a SharePoint F as a SharePoint framework person,
- 17:50I've known for a while and I've had the reaction when someone says they're doing
- 17:53that, I'm going, you're way off on the reservation and your mileage may vary.
- 17:56, Microsoft doesn't support this, so good luck.
- 17:59The fact that they're giving us guidance with this is like,
- 18:01are you guys aware that you're giving us guidance?
- 18:03But the part that really shocked me and shocked other people is that then
- 18:08they walk you through the way that they did this was that they have you, okay,
- 18:12so let me take a really small tangent. In a all SharePoint framework,
- 18:16projects are, well really any kinda development project you do,
- 18:19you have two different kinds of dependencies.
- 18:21You've got dependencies you only use in development. So stuff like unit testing,
- 18:24build performance, whatever.
- 18:28And then you got dependencies that run in production,
- 18:29which is we need this stuff to be able to run that, run our app.
- 18:32So we have the same thing as SharePoint framework. Well, what they did is they,
- 18:36in the production dependencies, those SharePoint framework packages were up,
- 18:39were not updated, changed to version 1.5 0.0.
- 18:43So they walk you through, here's all the steps you do to go to 1.5 0.0.
- 18:47So that's like, okay, that's what you said in the docs.
- 18:50But then over in the dev over in the develop the development dependencies they
- 18:54have,
- 18:54you go modify a handful of those SharePoint framework packages to SharePoint
- 18:59framework version 1.9 0.1.
- 19:02So not only have they changed the version of React and the version of the office
- 19:06UI fabric that are, that is,
- 19:08that's being supported by 1.5 0.0 to a version that did that SharePoint
- 19:13framework was never tested to be able to work with.
- 19:16But they've also gone in and they've mixed two versions of the SharePoint
- 19:20framework in the same project,
- 19:22which I can guarantee you has never been tested ,
- 19:26it's never been designed to ever do this.
- 19:28I'm surprised that it even got projects working in this, in this scenario,
- 19:32much less all of the other potential effects that this could have.
- 19:36This was like.
- 19:38I mean, one question's how well they work in this area. Like I'm,
- 19:42I'm just reading through this PR and it's a mess.
- 19:46Like you are completely, like you said, uh,
- 19:49outside the bounds of normal world.
- 19:52Like let's take SharePoint framework outta the equation, right? Like,
- 19:54like and just getting into all the linkers, the yeomen generator,
- 19:59like all that stuff.
- 20:00Like you're effectively telling customers to go down the path of like, Hey,
- 20:03we have this supported way for you to get onboard the platform and by the way,
- 20:08go make a bunch of human-driven crappy decisions that are probably going to
- 20:12break you. And like, let's forget about like just typos and you know, you're,
- 20:17you're s and you know,
- 20:17your your dependencies and your configuration let alone like,
- 20:21does this stuff run? How does it work?
- 20:23And then what does supportability look like and whose responsibility is
- 20:27supportability? Like that's always very, very hard. Like I don't,
- 20:31I'm not as familiar with the way it works in SharePoint land,
- 20:33but I know just doing like storage SDKs for Azure,
- 20:36like we walk a very fine line between like, oh,
- 20:39that's an S D K problem or that's a your code problem and we really can't help
- 20:44you with your code kind of thing. And you see things like this and it's like,
- 20:48ooh, , that's rough.
- 20:49This is just customer reported incidents in whatever flavor they are.
- 20:52It could be GitHub issues, could be support requests,
- 20:56could be incidents that are bubbled up to engineering teams from a support
- 20:59request. Like you don't want to do stuff like this that causes confusion and
- 21:05just becomes a C R I generator.
- 21:07, I completely agree with you and it's, I, you know, you,
- 21:09if you poke through, when you look at the PR and if you look at like the files,
- 21:13there's a section there where you, where you, if you look through the pr,
- 21:15you can see where I've commented to the,
- 21:17the author of the PR where it's like going, this is, look,
- 21:19if this is what you want people to do, this is not the way to do it. It like,
- 21:22there's so many little pieces about the PR that are wrong with it.
- 21:25Like he's saying to go,
- 21:26they're saying to go in and make changes to the package json file and change
- 21:30specific version numbers. Unfortunately, that's not going to,
- 21:32that's not gonna do everything because if you have an existing project,
- 21:35if you've already run MPM install on it, what what it does is it download,
- 21:39it creates a giant dependency tree based on the version numbers that are in
- 21:42package J ss o and it saves a snapshot of that dependency tree in a separate
- 21:47file called a package lock file. And that's parallel to the package J ss o file.
- 21:52I think it's package lock, package dash lock J ss o.
- 21:55And every future time someone goes through an N P M install it checks to see is
- 21:59there a lock file because that's what I'm gonna use.
- 22:01Otherwise I'm gonna generate one based off package JSS O and that way I can do
- 22:05it on my pro, on my machine,
- 22:07give you a copy of my project and I can know that you're getting all the same
- 22:10dependencies that I, that I had. The problem is,
- 22:13is that if you go do those things manually,
- 22:14all you're doing is changing the package j s o file and not the lock file.
- 22:18So the next time you're do an NPM install,
- 22:19you're gonna get all the stuff that you had before you did the package JSON
- 22:23updates. So it's, it's a moot point.
- 22:24Like the one way to fix that is just delete the lock file and regenerate it,
- 22:28but he's doing it the wrong way. You should be doing it using like a script,
- 22:31which is what I had in the, in the PR release.
- 22:33But the other thing is is like Scott write to your point that you said now you
- 22:37know, cards on the table, this PR has not been merged,
- 22:39so it's still just a PR and it's not official docs yet, but it,
- 22:44it's a doc is so far as the stance on how do you deal with these changes for
- 22:49a product that's already out in, in GA and is released.
- 22:51So it's kind of like straddling the line of like, is it done or not?
- 22:56The thing about it though that really got me with this PR is that it doesn't
- 23:00read like the changes they're having you do.
- 23:02This isn't the kind of thing that you would find in a poll,
- 23:04a poll request for official docs from a company like this.
- 23:08This is what you would find buried in a comment on Stack Overflow or in some
- 23:11YouTube video or like in some discord thing and saying,
- 23:15I figured out how to do it using this. And it's like,
- 23:17you gave our c drive everyone right? Access. No,
- 23:20that's not how you fix your security problems, right?
- 23:22When I see these,
- 23:23these are things that live in like the GitHub wikis
- 23:28for this stuff and then occasionally you come across it or somebody does
- 23:32customer support person, they go, Hey,
- 23:34I followed this thing on this random wiki and you go like, oh yeah,
- 23:37that was wrong.
- 23:37We'll fix it and we'll delete it and we'll bring it over here and it'll be the
- 23:41the right thing and, and and the right manifestation.
- 23:45I wasn't even thinking about like the whole like just M B M flow and
- 23:49package locks and I mean really like at that point you're again just
- 23:54down a weird path like you are modifying the, what, what is it?
- 23:59Package locks are considered the manifestation of the manifest I think is the
- 24:03way M p M documents them, which is like a good way to do it.
- 24:06Like that's what it is.
- 24:06It's a semi durable record of all the things that were point in time generated
- 24:10for this project and,
- 24:12and all the various node modules and everything that came into it.
- 24:15And now you're just gonna go and trounce it and like you said,
- 24:18the next time you, you, you,
- 24:19you go and and do your M P M install and build it and push it out,
- 24:23it's different Again, good luck.
- 24:24That's the thing is like I, as I went back when I saw this,
- 24:27I was picking through it more and more and I, I ra so I,
- 24:30I asked questions back to the guy that sent me the original stuff.
- 24:32I went asked questions back to Microsoft and well I guess it's both Microsoft
- 24:35and I,
- 24:36the way I believe it works is all of SharePoint and SharePoint framework
- 24:41engineering is based out of Redmond.
- 24:43So it's based outta corporate and I believe the sustained engineering for
- 24:47on-prem is based on from a out of a team that's run,
- 24:51I don't know if it's really managed,
- 24:52but it's really run out of a team outside of Redmond. I believe it's in China,
- 24:57but this has nothing to do with the fact that something's in China,
- 24:59not in China, just it's like, I'm just saying it's two different,
- 25:02it looks like yep, they may be part of the same two different teams,
- 25:05but I can see that they're not Yeah, lowercase T not uppercase. Yes. Lowercase.
- 25:08Teams.
- 25:09Team . We already have two different teams,
- 25:10capital T we all need to . But yeah, so it just,
- 25:14it's a little weird and when I ask a couple more questions,
- 25:18kind of was told we're working on it,
- 25:21don't merge this pr and so that's why you saw it all of a sudden got the flag,
- 25:25like the in the end review and got it flipped over to the label of don't merge
- 25:30and everybody just kind of went quiet on me and it's like that's when you just
- 25:34kind like, oh, I think I might have just, the thing that surprised me,
- 25:37my impression is, is that they, the eng,
- 25:39the SharePoint framework engineering team learned about all this from me asking
- 25:43the questions. Like they didn't know what this was going on beforehand.
- 25:45At least that's the reactions I got.
- 25:47So that's the part that was really surprising to me.
- 25:49So like what I'm telling people today that are doing SharePoint framework stuff
- 25:53is first of all,
- 25:54this is a mess and you really don't want to follow any of this guidance
- 26:00until Microsoft makes a statement about it.
- 26:03Or at least like follow that pr what I would suggest you do if you really want
- 26:07to get on the latest and greatest stuff,
- 26:09subscribe to the PR and just wait for changes to happen because that's gonna end
- 26:13up being either,
- 26:14it's either gonna get closed and a new one's gonna take its place or there's
- 26:18gonna be some other guidance that comes along with it.
- 26:20But that's probably gonna be like the best like change log to kind of track
- 26:24where things are happening with it.
- 26:25What I'm telling people now is that unless if you do any customizations with the
- 26:30SharePoint framework in your environment, or if you have,
- 26:34if you purchase any third party products that you're gonna put in your
- 26:38environment and you're on SharePoint service subscription edition, be very,
- 26:42very either don't or be very,
- 26:44very careful in considering to install H 2 20 23 H
- 26:48two for SharePoint server subscription edition because I mean,
- 26:52as I've just gone through, you could totally wreck your, those customizations.
- 26:56It probably won't like make the, the farm isn't gonna go like belly up,
- 27:00but those customizations, that stuff isn't gonna work. It's.
- 27:03Just not gonna work. What do you do? 'cause like you said,
- 27:05this is already in 23 H two,
- 27:08if you've already installed 23 H two and you have a bunch of stuff that broke,
- 27:13are there any fixes at this point in time? Right.
- 27:16Now there's nothing official for Microsoft. They basically just,
- 27:19everything kind of went quiet. And so it's usually like when stuff goes quiet,
- 27:22it usually means that we don't have a, we don't have any guidance yet.
- 27:25We're trying to figure out what the heck's going on and where and what the state
- 27:28is. At least that's my interpretation.
- 27:30They haven't said anything publicly about this.
- 27:33There is another PR that uh, I think what yeah,
- 27:37what someone just put in the chat that they,
- 27:38someone messed up and they're trying to figure it out.
- 27:40That's kind of what my perception is on it. In fact,
- 27:43there's another PR like a two or three prs after this one that came in or that's
- 27:48still listed as open and it's flagged also as do Not merge where someone else
- 27:52was updating the docs around the h the 2023 H
- 27:56one update to put a version number in there and there.
- 27:59And it looks like Microsoft has just said,
- 28:02we're not making any changes to any developer docs about SS P S E for H
- 28:06one or H 2 20 23 while we're trying to figure this out. That's what,
- 28:11that's how I'm interpreting this and I'm being conservative when I say that
- 28:15there's some other stuff, but I don't feel like it's really fair to, you know,
- 28:18if you don't know what's going on, don't, don't hypothesize too much.
- 28:21So the only thing I would say is that if, if I, if,
- 28:25if a customer came to me and said, oh crap,
- 28:28we did update our projects to 1.5 0.1, we,
- 28:32and we had H 1 20 23 installed, sorry, 2020, say it again.
- 28:3723 H one H. Yep.
- 28:39And we did upgrade everything to 1.5 0.1 and we did install 23
- 28:44H two. What would you do? And unfortunately there's no way,
- 28:48there's never been a scenario where we've looked at downgrading a project and
- 28:53for the SharePoint framework, I've never heard of someone doing that.
- 28:56It's always moving forward, not backwards, right?
- 28:59So one of the things that I would consider is, I mean,
- 29:02you could try and go back to like a good state of 1.5 0.0
- 29:07at least for now, because technically every version of the SharePoint framework,
- 29:11like when they did 1.5 0.1,
- 29:14it should have installed all prior versions.
- 29:16Like that's the way it works in SharePoint online,
- 29:18like every version of the SharePoint frame has ever been released is is all in
- 29:21SharePoint online. So you can run any version of the SharePoint framework,
- 29:24you can build something with any version of the SharePoint framework and deploy
- 29:28it to SharePoint online and it works just fine. I believe it works. This,
- 29:31I I believe the same thing is true in SharePoint on-prem, it's just the,
- 29:35the upper limit is, is much lower.
- 29:37So I would think that if you get it down to 1.5 0.0, you should be good.
- 29:41Even if you know you're running in, well, yeah, you should be good.
- 29:45The worst case scenario is that you've gotta rebuild it as a 1.5 0.0 project.
- 29:51I absolutely would not do any of the stuff that they're talking about right now
- 29:54about here's how you can use React 16 and here's how you can use Office UI
- 29:57fabric version seven. I'm like, look,
- 29:59modern day stuff we're on React 18 and in fluent UI is all the way up to version
- 30:04nine. SharePoint framework just started supporting version eight of Fluent ui.
- 30:08So I wouldn't, which is the, the successors of the office UI fabric.
- 30:12I wouldn't do any of the stuff that that PR says about mixing and matching
- 30:16versions and all that kind of stuff. I would just,
- 30:18let me do exactly kinda like what we did the H two H one update,
- 30:23except we're gonna try and like standardize on SharePoint framework 1.5 0.0
- 30:29and then any I S V that's out there,
- 30:32I mean if I were them I'd be leaning hard on Microsoft and being like,
- 30:35what the heck man,
- 30:37you guys gotta tell us what to do with this because I wouldn't upgrade my,
- 30:41I would not want any of my customers to do it. And they,
- 30:43I mean they would be looking at an absolute nightmare to go back and to roll
- 30:46back all their stuff.
- 30:50Do you feel overwhelmed by trying to manage your Office 365 environment?
- 30:54Are you facing unexpected issues that disrupt your company's productivity?
- 30:58Intelligent is here to help much like you take your car to the mechanic that has
- 31:02specialized knowledge on how to best keep your car running Intelligent helps you
- 31:06with your Microsoft Cloud environment because that's their expertise.
- 31:10Intelligent keeps up with the latest updates in the Microsoft Cloud to help keep
- 31:14your business running smoothly and ahead of the curve.
- 31:16Whether you are a small organization with just a few users up to an organization
- 31:21of several thousand employees,
- 31:22they want to partner with you to implement and administer your Microsoft Cloud
- 31:27technology, visit them at intelligent.com/podcast.
- 31:32That's I N T E L L I G I N
- 31:36k.com/podcast for more information or to schedule a 30 minute
- 31:41call to get started with them today.
- 31:44Remember intelligent focuses on the Microsoft cloud so you can focus on your
- 31:48business.
- 31:51You're in, what's theoretically a,
- 31:54I'll put it in air quotes 'cause you know, documentation ,
- 31:57but you are in a, you are in a supported state like, hey,
- 31:59at a point in time documents said go do this thing,
- 32:02you went and did the right thing. As you said,
- 32:05generally the principle is go forward,
- 32:07not go backward and even go forward is go forward without
- 32:12breaking changes. Like, I don't know how it works over in E M P and,
- 32:17and everything they, they do like with SharePoint and Windows,
- 32:19but I can tell you like in Azure land, like I I,
- 32:22it's not upon impossible for me to introduce a breaking change in an S D K
- 32:25without like bending over backwards and doing the right thing to make it move
- 32:29forward. Like it really has to be the one and only path forward to get there.
- 32:34So I imagine there's also like the internal politicking of that of just how do
- 32:37you corral like, oops, and then another oops behind it .
- 32:42Yeah. How do two oopses make a, oh yeah,
- 32:45you should go do this and be happy about it and, and,
- 32:47and feel good with that decision.
- 32:49I don't if if I was an ISV or a customer I'd be sitting back and going,
- 32:52oh I did the right thing. Like it's your problem Microsoft.
- 32:56Like figure it out.
- 32:57That's the way I would And.
- 32:58Then once you figure it out,
- 32:59tell me Yeah and tell me better not involve me going backwards 'cause
- 33:03that's not acceptable.
- 33:04Well yeah,
- 33:05I mean if anything I would think that we're gonna see a 23 H two part D, right?
- 33:09It's like , right?
- 33:10Yep. H 2 22 do one three .
- 33:15There there's the problem with our updates now, right? It's like it is a,
- 33:18it is a 2023 second half update.
- 33:20We can't have like a third half update , right?
- 33:25Right. So is there any indication,
- 33:27I don't know that if we talked about this why they went back from 1.5 0.1 to
- 33:321.5 0.0,
- 33:33like is there things in h So let's say a customer's
- 33:38hasn't upgraded to 1.5 0.1,
- 33:40they still have all their solutions on 1.5 0.0 and they're on
- 33:4423 H one,
- 33:46they're obviously safe to upgrade to 23 H two because they're on 1.5
- 33:510.0. But why did they regress?
- 33:54Are there issues with 1.5 0.1 in 23 H one
- 33:59that are corrected in H three or 23 H
- 34:04two by going back to 1.5 0.0 if that all made sense. .
- 34:09This is the part where like this gets to be, this is, this is hard.
- 34:13I get if you're driving and you're trying to focus on like directions and the
- 34:16numbers we're gonna start throwing around here this,
- 34:18you're gonna get lost quick or at least I would get lost pretty quick.
- 34:23So there's, so one, let me,
- 34:25before I answer that question and the spirit of politics,
- 34:28let me answer a different question that I feel more comfortable answering.
- 34:30.
- 34:31.
- 34:32You must've been on a big debate stage this week. .
- 34:35? No, if I was, I'd be screaming at you , first of all,
- 34:39no one would've upgraded their for let's just think just about one,
- 34:44about H one. About H one, okay. Okay. Yep.
- 34:47No one would've upgraded their projects to 1.5 0.0 because prior
- 34:52to that it was 1.4 0.1. So that was the highest we could go to is 1.4 0.1.
- 34:57And then they, when they shipped H one, we jumped all the way to 1.5 0.0.
- 35:01So you skipped 1.5 0.0 Yes. When you went from between those updates. Got it.
- 35:06Okay. And.
- 35:07In fact, the SharePoint release like chronology,
- 35:10it went from 1.4 0.1 to 1.5 0.0 to 1.5 0.1
- 35:15on-prem.
- 35:16There was never a 1.5 0.0 until until the last month.
- 35:21So there was never a state where someone already had a 1.5 point project on it.
- 35:25They either had a 1.4 0.1 or earlier.
- 35:29Or a 1.5 0.1.
- 35:30Or they would've had a 1.5 0.1. So that was, that was one thing.
- 35:34What was your other question?
- 35:35So it was kind of that,
- 35:36and it was was like why did they go back to 1.5 0.0 from 1.5 0.1?
- 35:40Are there issues in 1.5 0.1 that they should actually,
- 35:44and that was the one you said in the spirit of politics.
- 35:47We can forego that one if we need to.
- 35:49I've seen some stuff on a thread, but I really,
- 35:51and it's was not technically they didn't tell me it was under N D A,
- 35:55I don't feel comfortable saying it because I'm not entirely sure if it was or
- 35:59was not. That's fine. And so I'm not gonna say it. However,
- 36:01what I can say is that I went back and I looked and my gut said there wasn't
- 36:06much in 1.5 0.1 compared to 1.5 0.0 back when this whole happened. And again,
- 36:10like I have this Google sheet where I keep a list of all, like this giant list,
- 36:14it's a, it's a terrible work worksheet to try and like consume,
- 36:19but I went back and looked at it to try and see what the differences were
- 36:21between the two. And they're very,
- 36:23very small things and the things that were different were very cloud
- 36:28specific like Microsoft Graph or Azure AD or something like that.
- 36:31So they're really is nothing that was different between the
- 36:36two versions that you're gonna feel like, oh we had a loss of this. Got it.
- 36:41The only thing you're gonna feel like if you had a loss of is if you updated 1.5
- 36:430.1, then you updated to H two and you're like, where did the whole framework,
- 36:46not that it works is it's not there anymore.
- 36:48.
- 36:49The one thing that I would say to it though is that we always assume that they
- 36:53would never go through and update the SharePoint framework on-prem.
- 36:56We always assume that they've told us that for, what was it,
- 37:002017 is when it shipped and then it was 2017,
- 37:04February, 2017 is when the SharePoint framework V one shipped late that year
- 37:09is when a feature pack was released to let us to be able to install a SharePoint
- 37:14framework on SharePoint server 2016. So that would've been late 2017.
- 37:19And so all the way from late 2017 all the way up to March or April
- 37:24of this year, so what, six, seven years we've always been under,
- 37:28we've always been told there will be no updates to on-prem when they came out on
- 37:31on-prem and they said we're gonna start updating the SharePoint framework and
- 37:34we're gonna do this small release first. And it's like, well that's a surprise.
- 37:37That's, that's some good news. But with this one I get the impression,
- 37:42so I'm not, I'm gonna kind of paraphrase, kind of read between the lines.
- 37:44So this could be right, this could be wrong,
- 37:46but it's like kind of like based on what I know, I think,
- 37:49I think it's along the, the rights,
- 37:50the spirit of what's going on is that they realize that this is gonna be harder
- 37:55to do than they thought it was.
- 37:57And there's something about 1.5 0.1 that I think that
- 38:02they thought, hey,
- 38:03let's give people a newer version of React and a newer version of Office UI
- 38:07fabric and we can't do that with 1.5 0.1,
- 38:10but we can do it with 1.5 0.0 and I think that's why they did it.
- 38:14Or at least that's kind of what my hunch is because everything in 1.5 0.1
- 38:19compared to 1.5 0.0, there's nothing there. There's not much there.
- 38:22When you look at the release notes, there really isn't a whole lot there. There.
- 38:26Wasn't. Got.
- 38:26It. So it's just a, it's really confusing. In fact,
- 38:30I'll pull the release notes up for 1.5 0.1. Wait, no, that's the wrong one.
- 38:33And while you put up,
- 38:34the other other thing that you and I had kind of talked about too is even with
- 38:38this pr, we talked about how they gave all the,
- 38:41that guidance for updating React and the UI fabric,
- 38:45but then the other thing you would have to be careful about is if you're on
- 38:48SharePoint subscription edition and you built a solution on 1.5 0.0,
- 38:531.5 0.1 and tried to upgrade and leverage React and
- 38:58Office UI and then tried to deploy that same solution into SharePoint online,
- 39:02you could have massive mismatches because now the version of the SharePoint
- 39:07framework and the version of React and Office UI don't line up between what's
- 39:11on-prem and what's online. So you, you really,
- 39:15even if there comes out a workaround to kind of shove these
- 39:19into the on-prem 1.5 0.0, 1.5 0.1, whatever,
- 39:23it may mean vastly different experiences if you tried to deploy the same
- 39:27solution, if you ever did go through a migration to SharePoint online. Yeah.
- 39:30I don't, and that's one of the big reasons why I tell people just don't,
- 39:32don't do this. Like if you've got customizations right now,
- 39:35don't rush to install H two because you don't know what this is gonna do to you
- 39:39going forward. And it's, I don't think, I mean if there's,
- 39:43if there's any kind of a silver lining that's good about this,
- 39:45it's not like it's a destructive change.
- 39:48And what I mean by that is that it's not like it's a feature pack or something
- 39:51or a service pack that you install that has changed like something in the
- 39:55registry or some database thing, right? This is just like,
- 39:57it is a non-persistent kind of a thing.
- 40:00It's just that stuff is broken and when they release an update,
- 40:02all of a sudden stuff will start working again. It's kinda like,
- 40:05like earlier this week we had issues with teams where guest users were losing,
- 40:09couldn't see channels and couldn't,
- 40:11were losing access to posting in in different teams and they finally fixed it.
- 40:15But the fix was all done on the team's client.
- 40:17So it's like once you shut down the team's client and restart it and it updates,
- 40:22you'll have all the fixes and it's like nothing ever happened.
- 40:25So it's kind of a thing like that. Like when they get this sorted,
- 40:28we'll be in better shape for it. My guess is that I've got to,
- 40:32I assume that we're gonna see another release of the H two, the H two, yeah.
- 40:37That's going to address these things because I don't see,
- 40:41even if you just told people don't upgrade React and,
- 40:43and obviously I fabric and we just deleted that part of the pr,
- 40:46that doesn't fix the problem that you're still doing a rollback.
- 40:49And if you're doing the rollback,
- 40:51I would just say like why can't you guys just go back to exactly the way it was
- 40:53in with uh, H one, right? Well I'll keep it clean, but it's a,
- 40:57it's a poop show .
- 40:59Well, and it's not like they haven't done that before. Like I,
- 41:02we've all been SharePoint guys forever.
- 41:04I remember versions of 2013 and some of those cumulative updates where they
- 41:08would push an update and like a month later they'd pull it and rerelease it
- 41:12because of stuff similar to this. Not the exact same thing,
- 41:16but inevitably something went out that should have been done differently or
- 41:20caused some issues and they have, they at least have a history of doing that,
- 41:24pulling an update and re-releasing it. They.
- 41:26Really do. I mean it's,
- 41:27it's really disappointing but it's like I get that it happens that you make an
- 41:31you, you introduce a regression. No, all good.
- 41:33Number one to recommend people to downgrade projects in order to go through and
- 41:37move forward. I've never seen that. Yeah, . Yeah, that's totally.
- 41:40Wrong. It is an anti-pattern on top of another anti-pattern,
- 41:43on top of another anti-pattern and it should not be there.
- 41:46That part's not right. And I, I think really what you face here is,
- 41:50and it's a little bit like how the sausage is made for these products,
- 41:55but you kind of alluded to it earlier, there's SharePoint online, the platform,
- 42:00there's this thing SharePoint framework which has a dependency on SharePoint
- 42:04online, but actually like, is it SharePoint? Well no,
- 42:07it's a SharePoint framework. It's this disconnected thing. Different team.
- 42:10And then there's this thing called SharePoint server subscription edition,
- 42:15which is, well you think it's all SharePoint, right?
- 42:17It's the same team that builds it kinda sorta of organizationally, sure.
- 42:21But really not so much. Like it's got a different roadmap,
- 42:23it's got a different set of priorities and it's got a different set of folks
- 42:26that are building it.
- 42:27And now you've got the whole SharePoint framework in the middle.
- 42:29Like how does the actual team that maintains the SharePoint framework,
- 42:32like is their priority SharePoint server subscription edition,
- 42:35I would hazard to guess and say no, they probably don't care.
- 42:39And mostly considered an on rails experience, right? Like, hey,
- 42:41we told on-prem customers that it was gonna be in this state for a long time.
- 42:44Like, oops, S P S E folks, you broke that promise.
- 42:48Go fix it and figure it out.
- 42:50And making customers bear the brunt of that.
- 42:54Like that's not right. Like somebody's gotta come up with an answer there, what,
- 42:57whatever that answer is, but it can't be downgrade.
- 43:00I completely agree with everything you said, Scott. I mean it was like,
- 43:03we started off as like number one,
- 43:04the big red flag here was a downgrade of a project. That's really bad.
- 43:08Number two. Then there was the whole thing of just the reaction that I got,
- 43:12the reaction I had that was thankfully I was, I felt, you know when you,
- 43:16you hear something and you're like going, the sky is not red, the sky's not red,
- 43:20but someone tells you and you're like, should I go check? I'm gonna go check.
- 43:23I'm gonna go check. And so it was like when I saw this whole thing of like,
- 43:26hey look,
- 43:26there's two different versions of the SharePoint framework that you can put in
- 43:28the same project. One for building and one for actually running stuff.
- 43:30And I'm like, I've been doing this like seven years. I'd never seen that.
- 43:34I'm like, I always thought that, like I've seen some of my students like say,
- 43:37Hey I'm, here's my, here's my package that j ss o file. I'm like,
- 43:39well I found the problem. Let's get this part fixed. No,
- 43:41I'm not having a problem with that. I'm like, well I don't care, but this is,
- 43:44this is very, very wrong and this could be the problem. Your car won't start.
- 43:48Well let's make sure you have wheels on it and like the gas is full and that may
- 43:51not be the problem, but you're gonna need that.
- 43:53So let's take care of that and make sure that that's not the problem first
- 43:55. Because that one's pretty obvious. So I,
- 43:57when I asked the the product group that, and they were like, what?
- 44:00And I was like, okay, yeah, okay,
- 44:02so I apparently I brought this to y'all's attention. So , somebody,
- 44:04lemme know what's going on. .
- 44:06That's part of it, right? Like, like the disconnected things team.
- 44:09The disconnected teams thing. It, it is hard.
- 44:12I take a lot of flack in my role for not knowing like the way every other Azure
- 44:15service consumes us. And I'm like, I can't, like that's not my job. .
- 44:20So there's all these dependent consumer things out there.
- 44:23The best is when other folks, and,
- 44:25and it sounds like it's a little bit like this in in SharePoint land as well,
- 44:29when other folks don't own your A P I and they kind of ape it
- 44:34and copy it and try their best,
- 44:36but they can never keep up with the service and the actual like service owner
- 44:41side of it. And that's where you end up in these like sticky situations.
- 44:45'cause somebody went down a path at some point and
- 44:48now they wanna pivot and change direction. It's like too late.
- 44:51Like that's not the way to do it.
- 44:53A new release or a new product is the way to do it.
- 44:55Don't mess and break with all this stuff that's already there.
- 45:00It's an interesting thing,
- 45:01like somebody should write a book about like the politics of multi service
- 45:05development, multi-product development at Microsoft. Like,
- 45:09like a good like tell all someday. 'cause it is kind of crazy,
- 45:12like the internal politicking of it. And I imagine other,
- 45:14other companies probably have the same constraints, but Oh sure.
- 45:17Microsoft is fairly unique from my experience at other companies with the way we
- 45:21build and release software. .
- 45:22I would love to see, like you read the book, the Phoenix project. Mm-hmm.
- 45:26. Mm-hmm . Yeah.
- 45:27So I would love to have see someone like write, you know, that's more or less,
- 45:31it's a novel, but it's really based on like, as you're reading as a dev,
- 45:34you're like, oh my God, this is so true. I'm glad it's written in like this.
- 45:37And it's not written like a documentary, but like, this is such a good story.
- 45:40This isn't like watching a movie about hackers.
- 45:42Like this is really like the real stuff. So I agree with you.
- 45:46I'd love to see someone write something about, you know,
- 45:49rolling out Platform Cloud, you know,
- 45:51enterprise Public clouds at scale,
- 45:54places like G C P A W SS, Azure and then, or like even a company,
- 45:59like let's see what meta,
- 46:00how meta does it and let's see how like what all the stuff that OpenAI is trying
- 46:04to manage as well. Like let's, I love to see all that,
- 46:06the behind the scenes of it.
- 46:07Mm-hmm. , I've said that for a long time.
- 46:08Like especially from an IT pro perspective,
- 46:10like to see the behind the scenes of any of these companies.
- 46:15The data centers, the networking, the rolling out different versions,
- 46:18the updating, the patching. I remember one session like,
- 46:23and this just gave me a glimpse at it. There was one session at Ignite,
- 46:27like years ago that I was sitting in and it was the exchange online team.
- 46:31And they were like, yeah, we never patch an exchange server. And I'm like, huh,
- 46:36you never patch an exchange server? And they're like, no.
- 46:39Like every two weeks we deploy brand new ones and rip out the old ones.
- 46:43We don't actually make any changes to existing servers.
- 46:47We just get rid of them and put in new ones. And the type of stuff that, I mean,
- 46:52you would never do that at a small company.
- 46:54I've never worked for a client that's like, no,
- 46:56we don't patch our shirt servers, we just deploy new ones,
- 47:00add 'em to the farm and kill off the old ones.
- 47:04That transition from like, I mean,
- 47:06even enterprise to like these massive clouds
- 47:11is, it is and it would, I'm with you.
- 47:14I would love to see a book or a documentary that gives a really good
- 47:19behind the scenes look, which we'll never get 'cause it's all proprietary ip.
- 47:24Or come work with me for a year, just come.
- 47:26Work with you.
- 47:26. Yeah, just sign an em, sign an employment recruitment at N D A .
- 47:29We'll, like we will chat, but come, come work with me for a year. .
- 47:33Uh, even the, even the, even the stories that I hear, like the public stories,
- 47:37but then the ones that are also under N D A, like one of my favorite ones,
- 47:42I'm not disclosing anything, but like when Markovich does this,
- 47:46one of his N D A talks like at M V P summit stuff that he'll share and like,
- 47:51even though it's in under N D A, there's stuff that's shared that I'm just like,
- 47:54wow, if this ever got out,
- 47:56like I can understand why you would not want this to get out.
- 47:58But the stuff that,
- 47:59just seeing the way that he talks about stuff and you're just like,
- 48:02I don't care what it's about,
- 48:03I'm gonna tune into one of his talks because it's always gonna be something
- 48:06where he's like kinda sharing the thinking and I'm like,
- 48:08I know that this is just the tip of the iceberg, but man, I would love to,
- 48:12I'd love to just sit in the back in the corner of your office during a couple
- 48:15meetings just to kind of just to, just to listen in and just be like,
- 48:18wow.
- 48:18I think you can bid on that as part of the gift campaign. So yeah, again,
- 48:22come on, come, come on. We'll, we'll,
- 48:23we'll give you the opportunity to spend some money to try and win that
- 48:26opportunity. And.
- 48:27, I'm sorry, I can't afford it. I'm, look, I'm trying,
- 48:29I'm saving up for copilot licenses.
- 48:31Same. I can't do it either. .
- 48:32, I appreciate you guys letting me, you know, having,
- 48:35let me join you guys. I thought that this would be a,
- 48:37even though it affects developers, it impacts developers,
- 48:40but I thought it would really affect it pros and more your audience,
- 48:44specifically people who are working on managing on on-Prem farms and SharePoint
- 48:48subscription, SharePoint server subscription edition,
- 48:51because this could really wreck somebody's weekend, month, whatever.
- 48:55So Yeah. Well,
- 48:56and even hearing the version numbers and all of it from a dev perspective too,
- 48:59like there's,
- 49:00there's too many times I don't think the IT pros and the devs talk to each other
- 49:04about this type of stuff. The IT pros are like,
- 49:07how are we gonna go patch the server and something breaks they don't think to go
- 49:10ask the dev about, Hey,
- 49:13what's going on with these SharePoint framework web parts? And yeah, it's,
- 49:17it's one of those times where it's a fascinating overlap kind of between the two
- 49:21and how one can have a big impact on another one. Do.
- 49:24You guys mind if I throw like a little plug in there real quick? No.
- 49:27No, go for.
- 49:28It. So I have like, I have a hourly coaching that I do as well.
- 49:31So if you're an admin and you're looking like, oh my God,
- 49:34is this gonna affect us? You can go to vos.ao, scroll to the bottom.
- 49:37There's one-on-one book, a one-on-one call. I can,
- 49:39we can talk through it and I can kinda be like, yeah, don't do it. Wait.
- 49:42You give folks free consulting sometimes.
- 49:44So I would actually recommend that you were on a couple weeks ago, months ago.
- 49:49I, I, I forget the timelines for how we publish things,
- 49:51but I'll put a link in the show notes.
- 49:52So everybody should go back and listen to episode 3 44 where we had a C on and
- 49:57we talked through and tried to rationalize the right way to
- 50:02approach development in the cloud around some of these Microsoft properties.
- 50:06And one of the fundamental questions we were kind of toying with was,
- 50:09should you be building SharePoint framework or teams apps or M 360 fives apps in
- 50:14the first place? So maybe go back and listen to that.
- 50:17Like if you've gotta go through this rationalization exercise anyway,
- 50:20and then once you've answered that question,
- 50:22come back and see if you need some more time with ac.
- 50:25It's interesting. We do, we're, I'm,
- 50:26I'm teaching a class right now on teams Zap dev and, and it's like,
- 50:30do I build a web app or do I build a teams app? And I'm like, well,
- 50:33it's a big topic. We, we haven't,
- 50:34it's an eight week long class and we've been tackling it every single week that
- 50:38someone's like, , but what if? And I'm like, okay,
- 50:40we're gonna just dedicate a whole week to this one time. But yeah, it.
- 50:42Depends, you know, if you go this way, this.
- 50:44, oh, it totally does. It totally does.
- 50:46That's why everybody's usually this comes up in like a normal like workshop or
- 50:50something that I'll do and I'm just glad that I've got like two months to go
- 50:53through with this, with this group of students. And so it's like, don't worry,
- 50:56we'll get to that one again. Just keep, you know,
- 50:58put a feather in it by the end of the eight weeks.
- 50:59We should have a good idea of what we're gonna do. And they're like,
- 51:01so what's the easy answer? I'm like, oh, it's, it depends. I mean, yeah.
- 51:04That's always the easy answer.
- 51:06I answered a question today with that completely non dev related,
- 51:10but I was like, ask a question. Well, the easy answer is it depends.
- 51:14The consultants always say that depends. It's.
- 51:17Never, well so many times it seems like a cap out, a cop out, but it's not.
- 51:20It's like it really does. It's like I can talk about stuff.
- 51:23Mm-hmm and you're like, oh I didn't think about this.
- 51:24And it's like, yep, sorry, I'm just like everything else.
- 51:27I feel like a lawyer sometimes, but the more you uncover it's like oh,
- 51:30we got deeper into that onion like, oh look, that's on now I'm crying. .
- 51:35Yes. Well thanks, thanks for joining us again.
- 51:38That was fascinating.
- 51:40And we'll put all the links to a whole bunch of stuff we referenced to in the
- 51:44show notes.
- 51:45And if you do need to listen to it a couple times to keep all your version
- 51:48numbers straight, we understand.
- 51:50,
- 51:50I'll make sure I get you guys the link to the YouTube video and the YouTube and
- 51:54we'll put the article that'll really like detail and stuff.
- 51:56I'll put that in there as well and for you guys putting the show notes as well.
- 51:59So I appreciate you having me and I hope your listeners got a lot out of this.
- 52:03Anytime it's a pleasure. Well thanks and hope you all enjoy your weekend.
- 52:07Thanks.
- 52:07A lot man.
- 52:10If you enjoyed the podcast, go leave us a five star rating in iTunes.
- 52:14It helps to get the word out so more it pros can learn about Office 365 and
- 52:18Azure.
- 52:20If you have any questions you want us to address on the show or feedback about
- 52:23the show, feel free to reach out via our website, Twitter, or Facebook.
- 52:28Thanks again for listening and have a great day.