I have a web project written in .NET 3.5, on Visual Studio, which I have been supporting for a number of years.
I always deploy this myself using FTP. The project compiles to a single DLL file, which I put in the bin folder on web server. I then put the .aspx pages in the appropriate folders. I do NOT put the source code across. I am happy with this way of doing things. I find that there is little start up time on the app, and if I replace an aspx page on the fly, nothing is affected eg page lag.
I have a new web app built with .NET 4.5.
In the bin folder, I now find other files along with my DLL.,
eg folder called Rosyln, files called Microsoft.CodeDom.Providers.DotNetCompilerPlatform.dll, Microsoft.CodeDom.Providers.DotNetCompilerPlatform.xml
The app is running OK but..
One thing I find is that if I FTP up a replacement .aspx file, any request to a different page then takes a few seconds.
OK.. to my question... I would ideally like my 4.5 project to be deployed identically to my 3.5 project. That is, a single DLL file to FTP, plus the .aspx pages as needed, and hopefully get round the 'initial request lag' which I don't get on 3.5
Is there some setting I need to make it behave the same, and do away with the other stuff in the bin folder? Thanks