在不预编译源代码的情况下执行IIS .NET Webforms网站

Question

I want to publish to IIS the source code of my website (visual studio 2017 web forms website in vb.net or c#) without pre-compiling the project, so I can modify the source code directly on the server with IIS.

I know this is possible, I have done it in the past, and I have seen it done even now, but I cannot figure out what I need to do for this.

When I copy all the website source code to the server with the IIS, the website does not run... any ideas? or where to look for an answer? Is it a matter of setup? of the type of project?

When I call the website I get the following error:

Configuration Error Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: The CodeDom provider type "Microsoft.CodeDom.Providers.DotNetCompilerPlatform.VBCodeProvider, Microsoft.CodeDom.Providers.DotNetCompilerPlatform, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" could not be located.

Source Error:

An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Thanks!

Answer 1

@Gabe Thanks for the directions:

File - New Project, I see it under Visual Basic/Visual C# - Web - Previous Versions (ASP.NET Web Forms Site)

I tried it, and it works just fine! Basically if you create a project like you describe, you can just copy the source code in a server, without even installing visual studio there, and you can develop the site directly there.

This is ideal when you want to test things directly with external users, test things directly on the live or test servers, and of course you can make sure you have the source code of the project running, without having to keep both the source code and the compiled version.

There are a few drawbacks though: 1) you disrupt the website when you change things, and the application pool is restarted whenever there are changes, users in sessions are kicked out, etc... 2) there is a small delay while the site gets recompiled 3) there are cases where if while the code gets recompiled there are users online, there is asp.net corruption

Thanks for the replies!! Regards Manos