CSRUN＆CSPACK - SitePhysicalDirectoriesの目的は何ですか？

Question

DevFabric展開（CSRUN）のためにテストサーバにCSPACKを使用してAzure展開パッケージを構築しようとしています。CSPACKはWebロールのバイナリとファイルをCSXパッケージに忠実にコピーしますが、「rolemodel.xml」ファイルに埋め込まれている各Webロールの「SitePhysicalDirectory」パスも必要です。このディレクトリはパッケージ時刻に存在する必要があります。

展開時に、CSRUNはSitephySicalDirectoryパスを直接指すIISサイトを設定し、CSXパッケージにパッケージされているWebロールバイナリを完全に無視します。言うまでもなく、異なるマシンのテスト展開は機能しません。

ここで何か不足していますか？CSPACK / CSRUNがCSXパッケージのApprotootにIISで物理パスを設定できないのはなぜですか？パッケージされたバイナリが使用されていない場合、CSXパッケージの目的は何ですか？SitePhysicalDirectoriesは生産紺碧の展開で何をしますか？

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.