My Elements.xml looked like this:
<?xmlversion=“1.0“encoding=“utf-8“?>
<Elementsxmlns=“http://schemas.microsoft.com/sharepoint/“>
<WebTemplate Name=“General” Title=“General site” Description=“General web template for sites” BaseTemplateID=“1” BaseTemplateName=“BLANKINTRANET” BaseConfigurationID=“0” DisplayCategory=“My Category“ />
</Elements>
In my Visual Studio 203 project I created a onext.xml in a folder MyGeneralTemplate and now I’m getting a deployment exception 0x8107026E.
When I checked that the onet.xml was deployed to the right location all seemed to be fine.
Failed to open the file ‘C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\Template\Features\MyProject_WebTemplates\MyGeneralGeneral\onet.xml’.
I then updated my elements.xml from <WebTemplate Name=”General to <WebTemplate Name=”MyGeneralTemplate so that the template name and the folder name match.
And my project is now deploying fine
Pieter Veenstra
Is your business still running on paper trails, sprawling Excel files, or ageing Access databases? There's a better way — and I can show you exactly what it looks like. I'm the Technical Director of Vantage 365, a Microsoft solutions consultancy working with clients across the UK, the Netherlands, and worldwide. For over 30 years I've been turning messy, manual business processes into clean, automated systems that save time, reduce errors, and give teams the visibility they need to make better decisions. SharePains is not just any blog run by a Microsoft MVP. Have you ever used Try-Catch in Power Automate? The original post about Try-Catch in Power Automate can still be found on this site, https://sharepains.com/2018/02/07/try-catch-finally-in-power-automate-flow/ Or have you ever used the Pieter’s method to avoid variables and speed up your flows? https://sharepains.com/2020/03/11/pieters-method-for-advanced-in-flows/ You can contact me using contact@sharepains.com
