Best practices for source files added via the NuGet package

1 Answer 54 Views
General Discussions
Bill
Top achievements
Rank 1
Bill asked on 14 Jan 2022, 02:59 PM

We've added the Telerik.UI.for.AspNet.Mvc4.2021.3.1207 NuGet package to our project and I was wondering what the best practices are for excluding unneeded content from publishing. There is a folder called 2021.3.1207-source which by default is published with all the other content that the NuGet package has added. So far we have manually marked the content to not be included when published in our build pipelines, but we're wondering if there is a more standard way of doing this? Is there a NuGet package which excludes the source folder?

In addition to this, is there a preferred method of excluding themes from a project? Again we can manually remove them or mark them to not be published, but I was wondering if there is a suggested way to configure what is and isn't included.

Many thanks

1 Answer, 1 is accepted

Sort by
0
Ivan Danchev
Telerik team
answered on 19 Jan 2022, 11:08 AM

Hello Bill,

Currently, we don't have a separate package that does not include the -source folder. There is a feature request in our feedback portal about splitting the packages, instead of having a single one that adds everything: https://feedback.telerik.com/aspnet-mvc/1357556-provide-separate-content-and-assembly-nuget-packages

I would suggest voting for it, and also to leave a comment specifically about the -source folder, as a separate package that adds this content can be considered.

Until the package is split, excluding the unwanted content has to be done manually.

Regards,
Ivan Danchev
Progress Telerik

Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.

Tags
General Discussions
Asked by
Bill
Top achievements
Rank 1
Answers by
Ivan Danchev
Telerik team
Share this question
or