damianedwards / aspnet5-workshop Goto Github PK

Hi,
I have followed the instructions in the lab, but I get an exception from the host = WebHostBuilder()....Build() call in Main.

{"Method 'Log' in type 'Microsoft.AspNet.Server.Kestrel.KestrelTrace' from assembly 'Microsoft.AspNet.Server.Kestrel, Version=1.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' does not have an implementation.":"Microsoft.AspNet.Server.Kestrel.KestrelTrace"}

Am I doing something wrong?

From a C# client

https://stackoverflow.com/questions/34547398/when-uploading-files-to-asp-net-5-web-api-the-collection-of-iformfile-is-empty

From a web browser

https://stackoverflow.com/questions/34466141/how-to-upload-file-with-jquery-to-mvc-vnext-webserver

Would be a nice lab addition I think

Working in an enterprise scenario (multiple apps, single source of authZ), it'd be useful to see examples of how you'd plug in an external authorization provider to work with the new policy based authorization filter. Would you do it via middleware or are there existing extension points in the framework?

We have several scenarios where we want to extend MVC applications from a plugin, which seems easier to do in ASP.Net Core MVC but still has bits to figure out a best approach on, can we add examples (or "no, you can't do that"s) for:

• Adding routes & actions to an existing application, preferably just by including the package (e.g. the parent app looks for and adds, via LibraryManager?)
• Adding views for those routes, that exist in the library package

We have use cases that lie on both sides of this and maybe there are simpler ways than we're approaching it. Practical use cases are things like dashboards where we'd like people to be able to write their own panels, pages, and post actions without touching the main application or involving a monolithic codebase there along with the community being able to share and contribute on these.

On the other side like our error handler we want to be able to drop in a few views in the app for easy access. Currently I'm approaching it as a simple route/action you drop in your application with a 1-liner to the package to handler the request...which is ultimately something like StringBuilder for shared libs with SystemWeb counterparts or possibly could include Razor dependencies on the Core MVC side of the fence.

How would you guys approach this? I'm curious if there are much better hooks or it's just not really an envisioned scenario you want to support. Either's fine, knowing either way helps.

Would absolutely love to know more about how one would go about taking a project.json project and building and publishing it as a nuget package. Lots of little in-between things to cover I'm sure.

This might do well as a whole section, broken down into various activities:

• Building the package and dealing with target platforms
• Publishing publicly
• Publishing to a private repository
• Setting up or what to look for in a build server
• If applicable, any caveats to consuming the project from a .csproj (use a Xamarin project as an example)