Hi Kevin,

I have been following your posts, but am missing something somewhere, it is mostly working, but seems to miss some files and I have no idea why.

I think I am confusing the two different methods and something isn't quite working. I need an App_Plugins folder and files in the wwwroot folder and I think this is where I am getting very confused, I either get one or the other but not both.

Screams very loudly!!

local nuget cache causing problems :D, getting somewhere now.

Thanks for the pointers Kevin, everything seems to be working now for Umbraco 10, I just need to get it sorted for v11 next :D

What about things like doctypes/templates? That is where I'm struggling the most. I'm currently importing a package XML which works fine in 10 but I just can't get it working in 11

I haven't tested or workes with any packages in 11 yet, so I can't help you (yet). Maybe the package.xml structure was changed? I find that hard to believe though that that is the case. I'll let you know if I find out more.

Maybe the package.xml structure was changed?

I don't think it has, but I will manually create some stuff in a vanilla 11 and create the package xml in that to do a compare

Maybe more important: are the files present in the package? NuGet packages are pretty stupid because they are meant for class libraries. Adding (static) content files to a packages usually requires some effort.

are the files present in the package

Mmm, no they aren't :( the App_Plugins folder is, just not the views

I thought so ;) These are exactly all the problems I ran into when I created the first package. So reminder for next time: always check first what's actually in the package.

You need to edit the project file and and tell it to pack it. Here is my section, you can modify for your situation:

    <ItemGroup>
        <Content Include="App_Plugins\ModularUmbraco.BasePackage\**\*.*">
                <PackagePath>App_Plugins</PackagePath>
                <PackageCopyToOutput>true</PackageCopyToOutput>
              <CopyToOutputDirectory>Always</CopyToOutputDirectory>
            </Content>

        <Content Include="src\scripts\**\*.*">
            <PackagePath>src\scripts</PackagePath>
            <PackageCopyToOutput>true</PackageCopyToOutput>
            <CopyToOutputDirectory>Always</CopyToOutputDirectory>
        </Content>

        <Content Include="Views\**\*.*">
            <PackagePath>views</PackagePath>
            <PackageCopyToOutput>true</PackageCopyToOutput>
            <CopyToOutputDirectory>Always</CopyToOutputDirectory>
        </Content>

        <None Include="buildTransitive\**\*.targets">
            <PackagePath>buildTransitive</PackagePath>
        </None>
    </ItemGroup>

You'll see here that the App_Plugins folder was also set this way by Umbraco in their template. I think officially you're supposed to add static content in a certain folder in the package, but I just put them on the root to make life simple ;)

mmm, If I do that I get an error about Duplicate content items and it won't build

If I manually add them in the nuget package file, it all works, so just need to figure out how to get them in :D

Bezinga!

I think I've cracked it :)

I had to do it like this

<ItemGroup>
    <Content Include="App_Plugins\MediaWizards\**\*.*">
        <ExcludeFromSingleFile>true</ExcludeFromSingleFile>
        <CopyToPublishDirectory>Always</CopyToPublishDirectory>         
    </Content>
<None Include="views\**">
  <Pack>true</Pack>
  <PackagePath>Views</PackagePath>
</None>
<None Include="build\**">
  <Pack>true</Pack>
  <PackagePath>buildTransitive</PackagePath>
</None>
</ItemGroup>

So far so good, however I now need to get the views registered as templates in the backoffice otherwise the documents do not pick them up.

If I use a package.Xml and use a migration Plan it overwrites the content of the views with the content from the package.Xml which I don't want, is there any way to either prevent that, or maybe register them as templates in code?

I am already running some code to create member types and groups, but never created a template definition in code.

I managed to work out how to do this.

I removed the templates from the package.zip and added the views back in the RCL, then in my PackageMigrationbase, I registered the views as templates prior to importing the package like this

    protected override void Migrate()
    {
        //register the views as templates first
        _fileService.CreateTemplateWithIdentity("ForumMaster", "forumMaster",null);
        var master = _fileService.GetTemplate("forumMaster");

        if (master != null)
        {
            var templatesToFind = new[] { "forum", "forumPost", "login", "members", "profile", "register", "reset", "verify", "searchPage" };
            foreach (var template in templatesToFind)
            {
                _fileService.CreateTemplateWithIdentity(template.FirstCharToUpper(), template,null,master);
            }

        }
        //Now the templates are registered we can import the package xml
        ImportPackage.FromEmbeddedResource<ImportPackageXmlMigration>().Do();
        Context.AddPostMigration<PublishRootBranchPostMigration>();
    }

Nice! I might implement this as well :)

Mmm, doesn't seem to be that reliable :( I installed an updated package version and it removed the templates from the doctypes!

Doh! ignore my last comment it was me being an idiot :D

Mmm, that is currently what I'm doing, but the package.xml migration overwrites the views that are in the nuget package as it gets run afterwards, so may as well just get rid of the views from the nuget package and just use a package.xml file and migration plan which just seems a bit counter intuitive as you then need to keep both the package project and the site project which created the package.xml in sync

And I couldn't even get the migration plan working in Umraco 11, it just did nothing.

Oh well, will just keep digging, Thanks for your suggestions.

You are correct. I just tested it (in Umbraco 11) and the template file that came out of the NuGet package gets overridden when Umbraco starts and executes the migration. Never knew. Because it's practically an empty file I never noticed it. But in hindsight, we've had some issues where a certain file would sometimes be empty. This explains it.

Looking at the package.xml, it does indeed contain the content for the template file. I can't find any documentation about what's possible in the package.xml file. So I'm not sure if we can skip the creation of the physical file.

In my case, it's the template for the homepage, which by default is empty so we can start development. But it means that if a developer runs the project for the first time when development is already underway, the homepage template might be overridden by the one in the page. I'm gonna try to remove the design tag - which contains the template html - in the package.xml and see what happends :P

It the templates are not in the xml then Umbraco does not see the views and all the pages have no template :)

Yeah I know, made an error in my previous post. I want to try to remove only the section of the template that contains the html.

If you do that it creates an empty view which overwrites the ones in the package, I already tried that :D

I created a separate topic with this question to keep things clean :)

https://our.umbraco.com/forum/using-umbraco-and-getting-started//110666-migration-with-templates-only-override-physical-file-if-it-doesnt-exist

Exactly how I felt when I had to build the first package. However, it's much easier after the first time and you know the different parts that make it work.

Glad to be able to help :)