Geek asks and answers

What is the purpose of sitePhysicalDirectories? Csrun & cspack?

I am trying to create an Azure deployment package using cspack on my build server to deploy devfabric (csrun) to the test server. cspack faithfully copies binary and web role files to the csx package, but it also requires the path "sitePhysicalDirectory" for each web role that is embedded in the "RoleModel.xml" file. This directory must exist at package time.

After deployment, csrun installs an IIS site that points directly to the sitePhysicalDirectory path and appears to completely ignore the web role executables packaged in the csx package. Needless to say, the test deployment on another machine does not work.

Am I missing something? Why can't cspack / csrun set the physical path in IIS to match the csx package? What is the purpose of csx package if batch binaries are not used? What does sitePhysicalDirectories do in an Azure deployment?

+3
source share
3 answers

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

( WebRole.cs RoleEntryPoint) IIS. , , - . - WebRole.cs RoleEntryPoint. RoleEntryPoint . , , / -, .

+2

, : " cspack/csrun - , ". , Visual Studio .

RoleModel.xml, physicalPath "approot" ( RoleModel.xml) , .

+5

I think it sitePhysicalDirectoryshould be installed as a folder in AppRoot in your csx package, and not as the source of your files and web role files.

+1
source

More articles:


All Articles