VSTS Azure DevOps : Trying to Build and save only certain folders but everything from Project TFS Folder is getting built and deployed - azure-devops

I'm trying to build and publish certain folders of a project and deploy them to remote server using Azure DevOps. My Copy files task and Archive copies everything from TFS instead of the content I want to build and deploy.
The last two screenshots display the Build folder getting published and the last one is the folder which is supposed to be Published.

Related

Uploading a folder to azure devops

I have a project that is in azure devops
Now I had to add a special DLL
which is inside a folder
And I tried to upload the project + the folder to AZURE
And the folder doesn't come up
I added it manually to the drum folder inside bin->debbug
I would appreciate it if you could help me
What I don't understand is how to upload a folder or a file that I paste inside the project
As of this time, however, it is not supported to upload folders or folder structure through Azure DevOps. You can only upload files.
Generally, we use git command to upload folders to Azure DevOps. If you are using Visual Studio or VS Code, you can also connect Azure DevOps repos to them and upload folders through them.

Azure DevOps deploy Angular app to IIS with Octopus

I'm trying to deploy a Angular application to my IIS server using Octopus and Azure DevOps
My application has multiple environments, each environment with it's own settings (config.prod.json)
What I want to do
Basically Octopus should take the release from Azure DevOps, and copy the release to multiple folders, with different config.prod.json files.
Each folder corresponds to a specific IIS website.
Azure DevOps pipeline setup
Use Node 14.x
npm install
ng build --prod
Archive dis/angular-app ; Archive type: zip
Publish Artifact; Path $(Build.ArtifactStagingDirectory)
Triggers : Enable continuous integration
Azure DevOps Releases setup
1. Package Application for Octopus
2. Push Package(s) to Octopus
3. Create Octopus Release
Octopus setup
One step DEPLOY TO IIS
1. Package details
2. Custom Installation Directory
[![enter image description here][5]][5]
3. IIS Web Site and Application Pool
Errors
In IIS while I click Binding, Basic settings, I get this error: There was an error while performing this operation. The parameter is incorrect
Also, the folder mapped in iis for the website that I'm targeting. Contains a folder drop with the zip file 27.zip (27 is the release id)
How do I unzip the zip file?
How do I replicate the zip file to the other environments?
Is my configuration ok so far? What am I doing wrong?
Just a few of the links that I've checked:
https://octopus.com/docs/guides/deploy-aspnetcore-app/to-iis/using-octopus-onprem-azure-devops-builtin
https://www.youtube.com/watch?v=NFqrWsUPCAM&t=345s
https://www.youtube.com/watch?v=oeNYtYuhZQ4&t=2s

Azure Devops Publish Artifact generates .cs,.bat etc (not deployable files) in Directory [duplicate]

I'm trying to build and publish certain folders of a project and deploy them to remote server using Azure DevOps. My Copy files task and Archive copies everything from TFS instead of the content I want to build and deploy.
The last two screenshots display the Build folder getting published and the last one is the folder which is supposed to be Published.

VSTS Build not including all dll's in artifact

I am trying to build a dot-net web application in Azure DevOps using the agents/tasks below
UseNuget, Nuget Restore, Visual Studio Build, Publish Build Artifact
The Artifacts generated contain the dll's within the bin folder and some aspx pages.
However it does not generate two folders inside the Bin folder named Release and Rosely which contain more dll's.
Can someone please suggest what i am doing wrong.

VSTS performs web deploy successful, but website does not work

I am trying to get Visual Studio Team Services (VSTS) to perform a web deploy of my app. According to the VSTS UI the web deploy is successful, but when I browse the deployed web site it shows the default IIS screen ("Welcome - IIS").
This is my publish step in the build pipeline:
This is my release definition:
This is the resulting deploy folder:
Build.log (with replaced values) - https://drive.google.com/file/d/1y6q2Cjr1gxBVMcHeh6n_r7qu-JpJFSyC/view
Do I need to add an additional step to the release pipeline to get the .zip files extracted?
You do not need to add an additional step to extract your zip, but you need to tell the IIS Web App Deploy task to deploy your zip file and not a folder. You have specified a folder for the Package or Folder input, so the task is doing exactly as you told it to do, deploy the specified folder.
If you only have one zip file in your build artifacts, the default value for this field, $(System.DefaultWorkingDirectory)\**\*.zip, will pickup your zip file and correctly deploy it. If you have multiple zip files in your build artifacts, you will need to specify the full path to the zip file in order for it to deploy.