Tomáš Herceg

I've found one issue here - the assembly name can be just the name or a fully qualified name. I am not sure what solution will be better - we...

Thanks for the feedback. ## Arrays You are right, `elementType` doesn't support nested arrays - we'll use just `type` with the full specification of the array. However, I'd prefer to...

I have started implementing the type metadata in the `viewmodel-types` branch. It's not working right now, but the generation of type metadata JSON works and is covered by a few...

I've never seen such exception on IIS. I can see some `dotnet watch` entry in the stack trace - we should investigate what's the problem: ``` Microsoft.AspNetCore.Watch.BrowserRefresh.BrowserRefreshMiddleware.InvokeAsync(HttpContext context) ```

What is your version of DotVVM NuGet package? I think we already fixed this issue.

Are you using Resharper or any other extension that "tampers" with the IntelliSense? I am asking because my experience with Resharper is that the dotprop option doesn't show up but...

It's not that easy - the Hot Reload is done also by a special loader which basically decorates the default file-system loader. Maybe we can re-architect this to work differently...

I've been looking at this again, and the problem is that the order of services returned by `IServiceProvider.GetServices` is not guaranteed. * The loaders which use a prefix need to...

Calling instance methods on viewmodels from static commands is not supported. You should use [Static Command Services](https://www.dotvvm.com/docs/tutorials/basics-static-command-services/2.0). Since the static commands don't send the viewmodel to the server, property values...

I think that the only reason for using an instance method as a target of static commands is the dependency injection, so we can change the behavior and make a...