I'm using Team Foundation Services to deploy my store. I have only managed to deploy the compiled files of Nop.Web. What do i have to set to have Nop.Admin files to be in the same package with the correct folder structure into Nop.Web package? The version I'm using is 3.90.
I'm using Team Foundation Services to deploy my store. I have only managed to deploy the compiled files of Nop.Web. What do i have to set to have Nop.Admin files to be in the same package with the correct folder structure into Nop.Web package? The version I'm using is 3.90.
We use VSTS (and teamcity) to deploy nopCommerce 3.90 to azure. nop.admin is a directory under nop.web so should be included in the nop.web zip file.
Are you using the deployment templates provided by VSTS?
Im using ASP.NET(PREVIEW) template. Cause im publishing to aws ec2. After building into package, my Nop.Web.zip is separated with Nop.Admin.zip. May i know which template you are used?
Im using ASP.NET(PREVIEW) template. Cause im publishing to aws ec2. After building into package, my Nop.Web.zip is separated with Nop.Admin.zip. May i know which template you are used?
But my Nop.Web.zip only has Nop web files. It doesnt have admin files in it. Admin files is in another zip, Nop.Admin.zip. Do u know where can i configure it to be in the same zip?
But my Nop.Web.zip only has Nop web files. It doesnt have admin files in it. Admin files is in another zip, Nop.Admin.zip. Do u know where can i configure it to be in the same zip?
As i've said, nop.admin is a sub directory (administration) of nop.web and so is already part of the nop.web. I don't do anything special, just build the solution.
I have finally found out why. Its because of I have custom build configuration. The custom configuration didnt inherits settings from debug/release. Thats why it is not publishing it correctly.