5

So, anybody else has and idea how to go about this?

[Edit] The reason for all those limitations are that it's not going to be a multi-user Web app but just a closed group of people will be accessing it and only on an Intranet so we were looking for a simple solution where we don't have to use any software setup outside our own (which has already update capabilities and handles up-/downgrades) and have full support/access to our already existing internal framework.

Community
  • 1
  • 1
macf00bar
  • 673
  • 1
  • 14
  • 32
  • I don't believe so but why would you want to do this? IIS serves websites... – Ahmed ilyas Feb 19 '14 at 11:33
  • You seem to have ruled out a lot of possibilities, without explaining why. If you don't make it clear what your criteria are (i.e., *why* are all those options not feasible?), it's going to be very difficult for anyone to make useful suggestions. – Chris Feb 19 '14 at 11:39
  • You may try to create HTML page markup, script and style streams manualy by WCF service. It's a solution without IIS but without ASP.NET MVC Framework possibilities to. – potehin143 Feb 19 '14 at 12:00
  • Why can't you use IIS? What are you hoping to host the MVC site on? – B-Lat Feb 19 '14 at 17:24
  • @benl2k: it's not so much about "can't" but "don't" like or it has to be installed, set up, etc... if everything is inside my own proc then I have full control – macf00bar Feb 20 '14 at 09:25

1 Answers1

2

after some "creative" googleing (we got inspired by IronScheme - have a look at IronScheme.WebServer and IronScheme.Web.Runtime -> Web/Hosting) and reverse engineering a sample MVC App (just look at the call stack and dig thrugh MSDN) we've found a possible solution.

we're going to utilize System.Web.Hosting.ApplicationHost.CreateApplicationHost for accessing our MVC app and HttpListeneras our own lightweight only-for-our-purpose "webserver".

macf00bar
  • 673
  • 1
  • 14
  • 32