Hello Team;

I'd like to suggest to offer us an easy way to use the different themes offered by Bootswatch (bootstrap themes) during development and also allow us to offer that capability to our user, so they can pick their own theme.

Hope this helps!

Thanks!
..Ben

In release 2.0.0 it was possible to set default property Visible to "true" for AnimationContainer. That is now gone. How do I make the AnimationContainer visible per default, i.e without calling ShowAsync() in some stage?

Br,

Sten

Hi. 

Because https://feedback.telerik.com/kendo-jquery-ui/1360369-blazor-ooui is not closed I am now suggesting that you make controls for the Uno UI platform and Ooui.

Ooui and Uno are both known in context with Web Assembly and I think you should make controls for both.

You should also consider making controls for Ooui server side. If I could choose from all the worlds' options to build a web application, I would use Ooui server side, if it wasn't because of the lack of controls. The server side option is so simple to use and it was actually the reason Frank Krueger created it to begin with. He wanted a super simple way to display something on the web and he achieved that.

Flemming 

 Microsoft.AspNetCore.Components.Server.Circuits.CircuitHost[111]
      Unhandled exception in circuit '_2TiBAG0g2G9PCcWgKc-G4zmfFAGiDJEO7pd7Jbjxpk'.
System.IO.FileLoadException: Could not load file or assembly 'Telerik.DataSource, Version=1.2.0.0, Culture=neutral, PublicKeyToken=20b4b0547069c4f8'. The located assembly's manifest definition does not match the assembly reference. (0x80131040)
File name: 'Telerik.DataSource, Version=1.2.0.0, Culture=neutral, PublicKeyToken=20b4b0547069c4f8'
   at System.Signature.GetSignature(Void* pCorSig, Int32 cCorSig, RuntimeFieldHandleInternal fieldHandle, IRuntimeMethodInfo methodHandle, RuntimeType declaringType)

Did I miss installing something.

Used the installer telerik.ui.for.blazor.2.1.0.commercial.msi

A basic Menu control is one of the most fundamental common controls ....  Why was it not included in the first release of UI for Blazor???

How about a basic fundamental Menu control in the UI for Blazor?   If not now, when?

You may get an exception like

InvalidOperationException: The current thread is not associated with the Dispatcher. Use Invoke() or InvokeAsync() to switch execution to the Dispatcher when triggering rendering or modifying any state accessed during rendering.

or you may get components that simply don't work (for example, a Window does not show, a treeview does not expand).

The solution is to revert to the RenderComponentAsync method in your _Hosts.cshtml file.

If filtering is enabled, the error may prevent the view from rendering  similar to NotImplementedException: Unexpected frame type during RemoveOldFrame: None.

Without filtering, an exception is thrown when you attempt to edit a field, similar to Error: System.InvalidCastException: Unable to cast object of type 'System.String' to type 'System.Nullable`1[System.Int64]'.

Using the new Grid grouping feature in 1.6, the Grouping button and the group header row both use the field name of the group column, rather than the title.  This is visible in the animated demo, where a column titled "On Vacation" becomes "IsOnLeave" once it is used as a group name.

I expect this is already known and slated to be fixed, but there aren't any grouping issues at all in the public tracker, so just in case...

After upgrading from 1.1.1 to 1.2.0 I get following exception on app start when hosted on azure app service, locally it works fine.

I have tried using the "static assets" and "CDN" version for retrieving the .js file, both yield this error.

An error occurred while starting the application.
DirectoryNotFoundException: C:\Users\VssAdministrator\.nuget\packages\telerik.ui.for.blazor.trial\1.2.0\staticwebassets\

Microsoft.Extensions.FileProviders.PhysicalFileProvider..ctor(string root, ExclusionFilters filters)

    DirectoryNotFoundException: C:\Users\VssAdministrator\.nuget\packages\telerik.ui.for.blazor.trial\1.2.0\staticwebassets\
        Microsoft.Extensions.FileProviders.PhysicalFileProvider..ctor(string root, ExclusionFilters filters)
        Microsoft.Extensions.FileProviders.PhysicalFileProvider..ctor(string root)
        Microsoft.AspNetCore.StaticWebAssetsFileProvider..ctor(string pathPrefix, string contentRoot)
        Microsoft.AspNetCore.StaticWebAssetsLoader+<>c.<UseStaticWebAssetsCore>b__2_0(ContentRootMapping cr)
        System.Linq.Enumerable+SelectEnumerableIterator<TSource, TResult>.MoveNext()
        System.Linq.Enumerable.OfTypeIterator<TResult>(IEnumerable source)+MoveNext()
        System.Collections.Generic.List<T>..ctor(IEnumerable<T> collection)
        System.Linq.Enumerable.ToList<TSource>(IEnumerable<TSource> source)
        Microsoft.AspNetCore.StaticWebAssetsLoader.UseStaticWebAssetsCore(IWebHostEnvironment environment, Stream manifest)
        Microsoft.AspNetCore.StaticWebAssetsLoader.UseStaticWebAssets(IWebHostEnvironment environment)
        Microsoft.AspNetCore.WebHost+<>c.<ConfigureWebDefaults>b__9_0(WebHostBuilderContext ctx, IConfigurationBuilder cb)
        Microsoft.AspNetCore.Hosting.Internal.GenericWebHostBuilder+<>c__DisplayClass8_0.<ConfigureAppConfiguration>b__0(HostBuilderContext context, IConfigurationBuilder builder)
        Microsoft.Extensions.Hosting.HostBuilder.BuildAppConfiguration()
        Microsoft.Extensions.Hosting.HostBuilder.Build()
        *.Program.Main(string[] args) in Program.cs

    System.IO.DirectoryNotFoundException: C:\Users\VssAdministrator\.nuget\packages\telerik.ui.for.blazor.trial\1.2.0\staticwebassets\

       at Microsoft.Extensions.FileProviders.PhysicalFileProvider..ctor(String root, ExclusionFilters filters)

       at Microsoft.Extensions.FileProviders.PhysicalFileProvider..ctor(String root)

       at Microsoft.AspNetCore.StaticWebAssetsFileProvider..ctor(String pathPrefix, String contentRoot)

       at Microsoft.AspNetCore.StaticWebAssetsLoader.<>c.<UseStaticWebAssetsCore>b__2_0(ContentRootMapping cr)

       at System.Linq.Enumerable.SelectEnumerableIterator`2.MoveNext()

       at System.Linq.Enumerable.OfTypeIterator[TResult](IEnumerable source)+MoveNext()

       at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)

       at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)

       at Microsoft.AspNetCore.StaticWebAssetsLoader.UseStaticWebAssetsCore(IWebHostEnvironment environment, Stream manifest)

       at Microsoft.AspNetCore.StaticWebAssetsLoader.UseStaticWebAssets(IWebHostEnvironment environment)

       at Microsoft.AspNetCore.WebHost.<>c.<ConfigureWebDefaults>b__9_0(WebHostBuilderContext ctx, IConfigurationBuilder cb)

       at Microsoft.AspNetCore.Hosting.Internal.GenericWebHostBuilder.<>c__DisplayClass8_0.<ConfigureAppConfiguration>b__0(HostBuilderContext context, IConfigurationBuilder builder)

       at Microsoft.Extensions.Hosting.HostBuilder.BuildAppConfiguration()

       at Microsoft.Extensions.Hosting.HostBuilder.Build()

       at *.Program.Main(String[] args) in d:\a\1\s\*\Program.cs:line 11

.NET Core 3.0.0-preview6-27804-01 X86 v4.0.0.0    |   Microsoft.AspNetCore.Hosting version 3.0.0-preview6.19307.2    |    Microsoft Windows 10.0.14393    |   Need help? 

At the moment, dropdown and popups (like the DatePicker and DropDownList) render in the place of declaration, and CSS rules from their parent elements affect them heavily (for example, they are hidden behind grid cells when used as custom editors).

The popups should be detached and rendered higher in the DOM if possible, so they don't get confined in their parent like that. This may be applicable for more components as well.

All controls (such as TelerikGrid, TelerikDropDownList, etc) should have a "Visible" property. This bindeable boolean value controls whether the control is visible on the page or not:

<TelerikGrid Visible="@IsVisible" />

@functions {

protected bool IsVisible

}

This is a much better method than surrounding the entire control's markup in an @if(IsVisible) block, since that causes the control to get removed/added to the dom at runtime. This can cause many issues such as the control's constructors being fired multiple times, the dom getting "jiggled" about unecessarily.

I feel the "Visible" property is a cleaner way to hide controls.

When following the Blazor UI code examples for the Grid, the source for index.cshtml contains the following:

@page "/grid/index"

@using Telerik.Blazor.Components.Grid
@using TelerikBlazor.Shared
@inject HttpClient Http

Notice that the using directive for the Shared component doesn't have a . separating Telerik and Blazor. It should read:

@using Telerik.Blazor.Shared

Hello Team;
Hope you're enjoying your well-deserved holiday.

As the new features arrive, the new/update docs will be arriving too. In order for us to stay on the top of all the changes taking place on the Doc section, I'd like to suggest to have a page that each line contains:
a) Date
b) Doc description
c) A link to that section

This way, we can regularly look at this list and jump to the new docs to stay up to date with the team.

Thanks!
..Ben