0

Is it possible Extended existing ASP.NET CORE Web API without recompilation.

e.g existing API works on "mysite.com/API/Controler1/Method1" want to add new controller "mysite.com/API/Controler1/Method2", without recompilation and stooping existing server.

whole idea is, not touching things that's working.

Should I split project in to two project ? (In that case how to deal with routing ?)

Improve this question
6
  • This depends on a lot of things that you haven't told us, like how much of the application runs on the server. Commented Feb 17, 2019 at 14:52
  • Related: stackoverflow.com/q/38298312 Commented Feb 17, 2019 at 14:54
  • Related: stackoverflow.com/q/36121999 Commented Feb 17, 2019 at 14:56
  • Every time when I Update my server application (webAPI) with new functionality I have to stop everlasting recompile it and redeploy. It would be nice to have ability to deploy new controlers for existing asp.net application without recompiling it. Commented Feb 17, 2019 at 15:05
  • That would be a neat trick. C# is a compiled language. The only way to do it would be to dynamically compile some code for each web request. There are ways to do that, but it would take some time to work out a good solution, and there are performance penalties. Commented Feb 17, 2019 at 15:24
Related questions
1
Extend ApiController
3
Versioning of Web API in .Net Core 1.0
0
Upgrading Asp.Net Web API from RC1
Load 7 more related questions Show fewer related questions

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.