I'm using VS2013 Premium with a complex "single page" web site project, written in vb.net. I'm publishing to file system and uploading with FTP to a remote host. I'm Just starting to test deployment.
The web site runs fine in the local development.
When I publish as "pre-compiled, single assembly", the application runs fine on the remote host. I haven't tested all the functionality, however it does many major functions. This also helped to identify a few compilation errors that I fixed.
However, when I publish the web site with no "pre-compile" settings, I get a compile error when I run the app on the remote host.
The compilation error detail is a lot of text that looks like this (in part):
"C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\cbfe14e5\d79d23f0\App_Code.hrrdiq93.8.vb" "C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\cbfe14e5\d79d23f0\App_Code.hrrdiq93.122.vb" "C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\cbfe14e5\d79d23f0\App_Code.hrrdiq93.0.vb"
> Is there a particular way to read and interpret the compilation errors to find out what the specific problem might be?
> Is there a potential that the compilation error could be "hidden" in the "single assembly" version, and produce a functional error later?
Any help with this would be appreciated.