Click here to Skip to main content
16,016,500 members
Please Sign up or sign in to vote.
1.00/5 (1 vote)
See more:
When we publish our .NET project to Azure websites, during the actual publish, the live site gets runtime errors


Description: 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.

<!-- Web.Config Configuration File -->

XML
<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>


Is this normal? Is there a better way to publish deploy?
Posted
Updated 1-Sep-15 16:07pm
v3
Comments
Sergey Alexandrovich Kryukov 1-Sep-15 19:27pm    
No, this is not normal. Properly deployed site should also overheat and eventually burn several CPUs on the factory.
—SA
ZurdoDev 1-Sep-15 21:38pm    
You need to see the full error and stack trace.
Patrice T 1-Sep-15 22:12pm    
Are you saying that you don't understand why your site crash when it is an arbitrary mix of files from old version and from news one ?
Serious ?

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900