Posts

I’m always excited when I earn a certification, but some are more special than others. I have been working for over a year to learn all the skills needed to earn the Microsoft 365 Developer Associate certification. While I have been working as a SharePoint developer for almost 15 years, most of my work has been in very specific areas, like webparts or apps. Certifications normally require more skills than one person would have experience in, even someone doing this as long as I have. MS-600, which is the only exam needed for the certification, covers several areas that I just don’t operate in every day. It has taken a while for me to get comfortable in those areas.

I recently took my first vacation since the Covid-19 pandemic began. We travelled to Puerto Vallarta, Mexico, and to be completely candid, I was nervous. For the last 10 years, I have travelled often for work and pleasure, but this is the first time in over a year that we have been on an airplane. While I think my health is pretty good, I fall into the high-risk category for Covid-19 based on the official guidelines. The thought of going through an airport, getting on an airplane, and staying in a hotel for 9 days was daunting.

As 2020 ends (finally!), I realized that I neglected to post about an acheivement that I am very proud of. Last month, I was confirmed as a Microsoft Certified Trainer (MCT) for 2021. This is my 5th MCT certification and I even received a nice polo shirt for the 5-year acheivement. I am very proud to be counted among professional instructors in Microsoft technologies and look forward to more opportunities to use my certification help educate others.

Recently, I built a web part for a client, which led to a discussion about why the web part background was static white, which did not reflect the branding on the page. My quick fix was to just change the color manually, but now I wanted to know more about how I could build webparts that are aware of the area that they are in. It turns out, there are several options, depending on the capabilities needed and the web part framework.

Microsoft warned us! The Document Object Model (DOM) on web pages was a common target in my pre-SPFx solutions, especially the ones that used jQuery. When SPFx came along, Microsoft was very clear that the classes and element ids on the modern page were not an API. By that, they meant that there was no contract with developers that those values would not change in the future. The future is here!

I recently ran into a situation where building and debugging a SPFx web part seemed to go off the rails. Then I figured out that my normal pattern of skipping the ‘gulp clean’ command during project deployment had cause what I thought was bizarre behavior in Site Collection Features and toolbox.

I was working for a client that does not have a dedicated development or QA environment due primarily to political reasons. They also block access to all non-company tenants. Fortunately, I am able to do my development “off network” and once everything is ready, I move the code inside the firewall. Since this was an update to an existing web part, I knew deploying it to the same tenant as the existing web part was going to be tricky. The existing web part is on the company intranet home page, so getting into a site for testing without affecting the original web part meant deploying into a “QA” site app catalog. I thought this would work and there shouldn’t be any conflict. Famous last words …