CSRUN & CSPACK - Qual è lo scopo dei sitifisiciDirectory?

Question

Sto cercando di creare un pacchetto di distribuzione Azure utilizzando CSPACK sul mio server Build per DevFabric Deployment (CSRUN) su un server di test.CSpack copia diligentemente i binari del ruolo web e i file nel pacchetto CSX, ma richiede anche un percorso "SitephysicalDirectory" per ciascun ruolo web, che è incorporato in un file "rolemodel.xml".Questa directory deve esistere al momento della confezione.

Alla distribuzione, CSRUN imposta un sito IIS che punta direttamente al percorso del sitifisicoDirectory e sembra ignorare completamente i binari del ruolo Web confezionati nel pacchetto CSX.Inutile dire che la distribuzione del test su una macchina diversa non funziona.

Mi manca qualcosa qui?Perché cspack / csrun non riesce a impostare il percorso fisico in IIS per Approviera nel pacchetto CSX?Qual è lo scopo di un pacchetto CSX se i binari confezionati non vengono utilizzati?Cosa fanno i sitifisicoDectorys in una distribuzione azure di produzione?

Answer 1

I think part of this has to do with the addition of Full IIS. It used to be the case that your approot directory in Windows Azure was for both the RoleEntryPoint process and the IIS WAS Host (one in the same). However, with full IIS, you would have w3wp.exe running your web code and the WaWorker process executing your RoleEntryPoint.

The decision was made to effectively copy the entire website (which also has the WebRole.cs RoleEntryPoint) to a new directory and root full IIS there. As such, you will notice that your packaging for Web Roles actually contains a copy of your code twice. Once, for the website and once for the WebRole.cs RoleEntryPoint. Only your RoleEntryPoint is executed now out of approot. I don't remember all the technical reasons why this occurred, but it might have been easier/safer to copy the website out rather than risk missing a dependency.

Answer 2

I'm beginning to think the answer to all of those questions is "Because cspack/csrun are poorly-designed piles of garbage that should never have shipped". They seem to be built for Visual Studio support and nothing else.

Manually updating the RoleModel.xml file to set the physicalPath attribute to 'approot' (it's relative to the RoleModel.xml location) after packaging appears to be a viable workaround.

Answer 3

I would think that sitePhysicalDirectory should be set as the folder under AppRoot in your csx package, not the source of your web role binaries & files.