This project has moved and is read-only. For the latest updates, please go here.

ASP.Net hosting

Aug 19, 2013 at 10:35 AM
Edited Aug 19, 2013 at 11:12 AM
Hey there

I'm working with a project that needs to host a simple webserver. Previously we have used HttpListener and HttpRuntime.ProcessRequest. But we are moving forward and trying to use Katana(Which from my understanding does the same, but we can rely on someone with more expertise :-)).

Therefore I have spent some time "improving" the Katana.Boot.AspNet package, and would like to know how to submit a patch/PR or how to get it in review. The code looks a lot like this where I made a PR before I knew about Katana.Boot.AspNet

Secondly I have some issues with managing assemblies, there are quite a bunch of dependent assemblies which either needs to be copied to the webproject, or somehow the path added to the assembly loader. Can anybody tell me how to deal with this?

EDIT: When building, can you limit the build to only build Katana.Boot.AspNet and its dependencies? I'm a bit new to the .Net build environment.

I hope these changes can help somebody out there looking to host ASP.Net on Katana

Kind Regards
Nicolai Willems
MaCom A/S
Aug 19, 2013 at 5:02 PM
See our Contribute page:

Nuget package restore is a great way to deploy 3rd party assembly from Some other assemblies you'll just have to deploy as part of your app. There's also the AppDomain.CurrentDomain.AssemblyResolve event you can use to provide manual fallback to an alternate location.

When building from the command line build.cmd there's not a simple way to limit what is built. Inside VS you can right click on a single project and select Build to only build that project and it's dependencies. Alternatively in VS you can unload projects you are not interested in.