One nuget package vs one package per component problem nuget version 26.2.4

Question

Hi,before I start. You are doing absolutely amazing work. I really enjoy working with your components. For quite some time I had a weird problem. I was using the package to get all the components. I also added the Syncfusion.Blazor.Themes. And in some cases I had this bug that is being described in https://www.syncfusion.com/forums/158329/could-not-find-sfblazor-in-window-in-nuget-18-3-0-35 or some simmilar. Some cases meaning for example using the scheduler component was impossible but using cards was possible.Thanks to your tutorials from Syncfusion Essentials Studio I realised that when I use a nuget per controller package f.e. I am easily able to show and work with the components without any issues.I am using 1) .NET 8 Blazor WebApp2) Interactivity type Auto3) Interactivity per page/component4) No authentication (it doesn't change anything)5) Theme Bootstrap v5Finally the question. Is it by design and the all in one nuget is obsolete or is it a bug or I just missed something in my setup?Looking forward hearing from you.

Vijay Ravi · Answer

Hi Pawel,We have validated your reported query regarding for
installing both `Syncfusion.Blazor` and `Syncfusion.Blazor.Schedule` packages
in your application . This may cause when both individual packages (e.g.,
`Syncfusion.Blazor.Core`) and the overall package (e.g., `Syncfusion.Blazor`)
are referenced in your application. This can lead to ambiguous errors between
the individual and overall packages.We suggest using either the individual packages or the
overall package alone to install this nuget package. For more details, please refer to
the documentation below.https://blazor.syncfusion.com/documentation/nuget-packages/ https://blazor.syncfusion.com/documentation/common/how-to/troubleshoot/#compile-time-errors Please let us know if you need any further assistance.Regards,Vijay