Forum Discussion
Is it possible to develop in No-Code Sandbox Solution style with Sharepoint PnP?
Hi Joel!
Thanks a lot for the prompt reply!
In this case, I assume you are referring to provisioning, so in short, I would suggest that you stop investing your time in WSP solutions and start using PnP as soon as possible.
I would be happy to, but wouldn't that mean that I would loose access to all the Visual Studio tooling for making content types, list definitions, workflows etc.? This is actually my biggest concern so far, as going backwards to a plain text editor sounds scary especially given the amount of cross-dependencies and the complexity of CAML (not even mentioning workflows which I've always designed only visually).
I understand there's an XSD schema for the provisioning file itself that I can use for validation, but it won't help me much with all the CAML, elements.xml etc.
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 😀
Hi Joel Rodrigues and Steve Johnson ,
In retrospective, you both are totally right. We are using PnP for our current internal SharePoint project, and I have also started using PnP for applying updates to an originally SharePoint Designer-authored web, which turned out to work quite good.
As for workflows, we've found a way to design them in Visual Studio and then compile into a form that could be provisioned via PnP.
Thanks a lot for the inspiration!
- 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.
