Answer If an ASP.NET MVC program is running in production, apart from database, there are two types of changes that are generally required to be carried out.

1). Changes in Algorithm, Logic, Security implementation etc. These are mainly done in Controller methods, and ultimately carried forward by the compiler itself to the relevant dynamic link library (.dll file).
2). Changes in User Interface (UI) components and these are generally done in .cshtml /html /JavaScript files.


For the first kind of changes, you need to first change the project configuration to "Release" mode, and compile the project. This will produce an updated dynamic link library (.dll) file in the folder like "/obj/Release".
For deploying this new .dll file to the production/staging setup, use any FTP tool to upload the new file to the designated folder like "/bin" on target server setup folder structure. While doing so, it is advised not to delete the previous .dll file, but keep it as renamed to some other non-executable format like ".txt". This will be required in the event of non-desired results. Please note that you are not required to upload .cs or source code files on the production server.
The server would then reload the new .dll file for your program.
You would need to take a proper downtime when deploying new files on the server, because of the fact that new library will abolish all existing sessions on the server, when loaded first time.

In the similar manner, upload new files for changes mentioned in step 2.

Answer My installation folder contains executable (.exe) files, and that are not supported /allowed by the service provider. I am not able to run my program...

Answer @Surinder, you need to do away with Nuget packages that make it mandatory to install .exe files on production server. Just un-install such plug-ins and recompile your program. It should work.