pubxml | Generates public.xml for Android library projects

What do i need to specify for the root file/folder in publish task for MSBuild "Release"?

Is the .NET release basically the binaries? Because for AngularOutput build I had to specify path of the AngularOutput, but for .NET Release, I am not sure what path that would be, i would think its the entire project, which means...its the binaries?

expected artifact:

UPDATE: Resulting artifact following Kevin's YAML:

inside _PublishedWebsites

Following update3, when running on windows agent:

Update#4: Using VSBuild

I have a .NET 5.0 project, ProjectA, which depends on a .NET Standard 2.0 project, ProjectB. I can build and run the .NET 5.0 including its dependency without issues. The two projects are stored in the same root folder, and relying only on default configurations, the resulting libraries end up in

I have a .net solution that I can build with msbuild and successfully generate a deploy package with a PublishProfile.pubxml transform for deploying to a single web server.

I need to take that build and generate deploy packages for different environments, which are set up as transforms using various .pubxml profile files.

I know I could build each profile separately, and it'd be negligible risk of injecting a change into a build, but it's time and space that aren't necessary to consume. I would only end up keeping one of them anyway, and just copying the unique web.configs from each transform into their own deploy package's folder (sorry if this isn't clear, happy to clarify).

I'm looking for something like this pseudocode, which I know is syntactically incorrect but should get the point across:

Edit
Process Explorer shows seven instances of w3wp with a lock on that file. So I think we need to stop these extra instances.

Since upgrading one project to .NET 5 (the solution has 27 projects in it), we're getting this error when publishing in the post-build event:

The process cannot access the file because it is being used by another process. [D:\somepath\MyProject.csproj]

The post-build event looks like this:

Some additional context: I created a solution using the Angular project template with ASP.NET Core in Visual Studio 2019. The app has several different environments: DEV, STG, and Production. There are corresponding "appsettings.json" files for the .NET project ("appsettings.DEV.json", "appsettings.STG.json", "appsettings.Production.json"), as well as "environment.ts" files in the "ClientApp" folder ("environment.DEV.ts", "environment.STG.ts", "environment.Production.ts"). This app will be deployed to IIS on a Windows Server, and I have created ".pubxml" publish profiles targeting a folder for each of these environments.

The project template generates the following in the .csproj file:

I'm trying to deploy a netstandard2.0 class library nuget to a local folder repository (specified in FolderProfile.pubxml). This works fine via VisualStudio's publish context action on a project: the process behind the scenes builds the project and packs desired items according to project.csproj and then copies the nuget package according to FolderProfile.pubxml. I've expected this could be achieved with msbuild as well (to be used in scripts).

I have been facing this problem with git in which I am trying to upload .mp4 files in a subdirectory of wwwroot/ but whenever I am writing git status, they won't appear.

The new video files are located inside wwwroot/Content/Videos/ZoomEspecialista/ This problem has never occured before. I have uploaded maybe 10-15 new .mp4 files.

Regardless of that, in my .gitignore file, I am not excluding the folder which contains these .mp4 files. I have checked multiple times to see if there is something, but I think the problem lies somewhere else. If anyone has any idea on how to tackle this issue, it would be superbly appreciating. Thanks!

The only thing I get from doing a git status is this despite of having uploaded my files to that subdirectory:

EDIT 2: Here is my .gitignore file:

I tried referring the solution suggested on https://docs.microsoft.com/en-us/aspnet/core/fundamentals/environments?view=aspnetcore-3.1 with the section Set the environment.Also, I added the below part of code in Project file/publish profile

For Windows IIS deployments: Include the property in the publish profile (.pubxml) or project file. This approach sets the environment in web.config when the project is published:

I have a Visual studio solution with several projects in it, specifically a DotNet5 asp.net app, that has several netstandard 2.0 references on it. it builds and runs fine in the debugger but continuously throws the metadata errors. It keeps specifically referencing its looking for a net5 folder in the netstandard2 project. I cannot find where its getting this from, the problematic one used to be a multitargeted project against framework 4.7, 4.8, and net5.0, but i got annoyed with the multiple dll's and just migrated it to standard2.0 and had no issues till i want to publish it.

I've tried what a few other questions referenced, cleaning, rebuilding, remove and re add references to other projects, deleted the obj and bin folders out of the solution, the removing the sou file, tried VS 2019 (16.9.0 preview 2) preview vs 2019 (16.8.3) release, different computer (pulled back down from a lan git repository) and got the same error.... also tried searching the entire solution for references to net5.0 and didn't find it outside of the expected locations like the csproj for the asp.net project and its respective pubxml. And just for fun, I temporarily retargeted the library project back to net5.0 and it still threw the same error even when the exact file and path listed did exist.

Using enters for the error below for the different columns in the error message, and removed the "sensitive" info. There is no error code provided by Visual Studio. Anyone else got any more ideas on what to try?

Error

Metadata file 'C:\Users\UserName\source\repos\Solution\Project 2\bin\Release\net5.0\ref\Project 2.dll' could not be found.

Project 1

CSC

0

Edit: adding a couple other sections of the error messages: