ASP.NET vNext is interpreted like PHP?

Asked

Viewed 125 times

4

ASP.NET vNext is presenting a lot of news in relation to previous versions, among them is the idea of not compiling the codes, just modify and already see what happens on the page. This means that ASP.NET will be interpreted in the same way that PHP is interpreted by Apache?

This gives me a concern, one of the advantages I’ve always seen in ASP.NET was not exposing the source code and not having to send it to the server at deploy time, basically just sending the binaries. With vNext it will be like PHP that we send the same codes and everything is interpreted on time?

1 answer

5

No, it’s not interpreted, if you look at the Getting Started you will see that it says that vNext uses Roslyn to compile the code dynamically, so you have the facility to change the code at any time you want and still maintain the performance of the compiled code.

  • the cool thing is that I don’t need to build my application all over again to "update" part of my code?

  • 1

    all indicates that this is exactly what they want, which in my view greatly facilitates the life of the programmer, how many times I do not update the browser just to realize that I forgot to compile the last change I did...

  • Okay, that answers the main part of the question but you could also answer the second part of it that asks if it is necessary to do the deploy providing the sources? I imagine the sources are needed to achieve the flexibility of editing and running, right? But if you don’t need the Edit & run and want to do the deploy torque only, it is possible?

  • This I can no longer say, as it is something very new, I do not know yet how the part of the deploy, whether it will have option to pre-compile everything or not.

  • Yes, @bigown you can still choose to deploy and publish only the binaries, just as you currently do.

Browser other questions tagged

You are not signed in. Login or sign up in order to post.