Forum Discussion
Is it possible to develop in No-Code Sandbox Solution style with Sharepoint PnP?
Hi there, Hopefully someone will be able to address my confusion regarding SharePoint PnP and sandboxed solutions. My understanding so far: PnP can deploy practically all the same artifacts ...
It may not sound like that at the start and when you are comfortable with the tools you currently use, but once you get into it, you will be a lot more productive. Also look at the PnP PowerShell for provisioning scenarios as sometimes it's a lot simpler than a full C# application.
The PnP provisioning engine is just amazing! The option to save a site as a XML template is pure gold 😉
And you can use any code editor of your choice, including Visual Studio.
The documentation is very good, and you have lots and lots of videos on the PnP channel with tutorials.
The SharePoint development sorry was never so strong 😀
The PnP provisioning engine is just amazing! The option to save a site as a XML template is pure gold 😉
And you can use any code editor of your choice, including Visual Studio.
The documentation is very good, and you have lots and lots of videos on the PnP channel with tutorials.
The SharePoint development sorry was never so strong 😀
Chalk another one up who loves using PnP!
You can do more with less in PnP, we’ve a number of site provisioning scripts written purely using PnP, some even writing to SP lists which is then firing off a Flow notification. It’s incredibly flexible and powerful.
We’ve ditched our WSP model mainly because it simply doesn’t scale in a large organisation. Makes adding new SP artefacts more difficult. For example, adding new views to all document libraries is a couple lines of PnP and CAML.
Similarly, if the CTH isn’t being used to deploy content types, then PnP can do a similar role.
You can do more with less in PnP, we’ve a number of site provisioning scripts written purely using PnP, some even writing to SP lists which is then firing off a Flow notification. It’s incredibly flexible and powerful.
We’ve ditched our WSP model mainly because it simply doesn’t scale in a large organisation. Makes adding new SP artefacts more difficult. For example, adding new views to all document libraries is a couple lines of PnP and CAML.
Similarly, if the CTH isn’t being used to deploy content types, then PnP can do a similar role.