1: log files cannot be written directly.
No direct operation in azureCompositionSo the function of writing logs directly cannot be used.
Solution: Write it to tablestorage. Or write it to the SQL azure log table.
2: PDF reports cannot be generated.
The error message "out of memory" is displayed. Is a GDI bug. Do not expect to solve this problem for the time being, especially when using third-party PDF controls (even Microsoft's own rdlc report has an error ).
Solution: Modify the PDF fileCode.
Another method I used: generate a stream of the PDF file on a third-party server and return it to azure.
3: the code file declaration of the aspx/ascx file codefile = ''cannot be compiled.
The system prompts that the XXX. CS file cannot be found.
Solution: Use the codebehind flag.
4: Modify the default homepage.
In web. config
<System. webserver>
<Defadocument document>
<Files>
<Clear/>
<Add value = "index. aspx"/>
</Files>
</Defadocument document>
</System. webserver>
5: staging Server
Each releaseProgramIn fact, it takes a lot of time, about 30 minutes, and there is a possibility of errors.
Therefore, first release it to the staging server, test it correctly, and then change staging to production in "Swap.
6: different database configurations of staging/production server
It cannot be placed in the web. config file because the file must be compiled, generated, and published.
Solution: Define the link string in the serviceconfiguration. cscfg file. This file can be modified externally without being involved in the compilation process. In this way, different servers can have different settings.
7. incremental release
This indicates what to do if only one DLL needs to be released again.
It seems that it cannot be done now. It can only be compiled as a whole.
I am still thinking, if the DLL is treated as a blob object in the container, it will be removed, instantiated, and then loaded for implementation. I don't know how it works.
8: workrole and queue.
This model can be considered when processing complex operations.
Related: problems encountered when Windows azure was released at the beginning of the previous writing.
Http://www.cnblogs.com/dlwang2002/archive/2010/07/08/1773429.html