Tag

deployment Archives ⋆ Imaginet

Mastering Your Deployment Pipeline (Part 1)

By Agile, All Posts, Application Lifecycle Management No Comments

  Imaginet Blog Series — Part 1 Mastering Your Deployment Pipeline     Most users of your application will never see the requirements or read notes from your sprint retrospectives. But something they will appreciate – or condemn – is your team’s ability to deploy an update to the mission critical software they use on a daily basis. Can you initiate and finalize a deployment in a small window of time? Can you do it…

Read More

MinRole Creates Simpler Deployments for SharePoint 2016 Administrators

By All Posts, Featured, SharePoint, Tutorials, Videos, Webinars No Comments

MinRole Creates Simpler Deployments for SharePoint 2016 Administrators! In previous versions of SharePoint, there weren’t any roles.  It was up to Administrators to configure which services would run where, and this would sometimes lead to small misconfigurations. Check out this video to learn all about MinRole and how Administrators can now define each server’s role in the farm topology. 0:52 – What is MinRole? 1:25 – SharePoint Server Roles 2:54 – How Does it Work…

Read More

Deploying a Provider Hosted SharePoint App to Azure and SharePoint Online

By All Posts, Application Development, Cloud, SharePoint, Tutorials No Comments

In this post, we are going to walk you through the process of deploying a provider hosted SharePoint app to Microsoft Azure and Microsoft SharePoint Online. We assume that the app has been created, and the app permissions are configured correctly for what the app is supposed to do. I should note that this article will only be about apps that are being deployed to a local app catalog. Also, I’m assuming that you have…

Read More

Mastering Your Deployment Pipeline (Part 5) 

By All Posts, Application Lifecycle Management, Productivity No Comments

  Imaginet Blog Series — Part 5 Mastering Your Deployment Pipeline     Timeline Impacts Perhaps one of the greatest opponents of automated deployment is the perceived impact on timelines that many developers and managers have of the process.  Indeed, stopping the project to learn new software or changing the way you approach deployment can seem daunting in the face of the unknown. But let’s not discount the positive impacts that this can have as…

Read More

Mastering Your Deployment Pipeline (Part 4) 

By All Posts, Application Lifecycle Management, Productivity No Comments

  Imaginet Blog Series — Part 4 Mastering Your Deployment Pipeline     An experienced development team would never forego security measures, architecture considerations, or database design on even a short-running project, but the ability to remain agile in deployment is often the first thing to go. Let’s have another look at some of the points we presented in Part 1 that were listed as challenges for teams on smaller projects to overcome. Counter Points…

Read More

Mastering Your Deployment Pipeline (Part 3)

By All Posts, Application Lifecycle Management, Visual Studio No Comments

  Imaginet Blog Series — Part 3 Mastering Your Deployment Pipeline     We can mitigate a lot of the problems we face in deployment if we just approach things a little differently from the start. We can’t turn back the time on already-running development teams, but we can work to introduce new measures to help reduce costs and improve deployment times. Let’s next look at those points we presented in Part 1 and try…

Read More

Mastering Your Deployment Pipeline (Part 2)

By Agile, All Posts, Application Lifecycle Management No Comments

  Imaginet Blog Series — Part 2 Mastering Your Deployment Pipeline     The Real Cost of Deployment In the Part 1 in the series, we looked at some of the reasons why we might neglect the opportunity to nurture the build process and create an automated solution for deployment. To really see why we should consider our build and deployment system as first class citizens on our development team, perhaps we should start by…

Read More
Let‘s Talk.
  • Let's Talk

  • This field is for validation purposes and should be left unchanged.