Multi project access level in azure DevOps

I have 3 .netcore project in one solution

  1. Data: to manage database
  2. ViewModel: to manage mvvm view model
  3. Design: wpf design

Data referenced in viewModel project and all Data and ViewModel refrencee in design

I want to use Azure DevOps installed on windows server to manage this solution. But I want to set permission to project Data to user AAA, set permission to project ViewModel to user BBB, and user CCC can access to entire solution.
How can I config DevOps for my project with correct project refrence in solution?
I’m new in DevOps and I don’t know that I must create one DevOps project for entire solution or create DevOps project for each project.
If seperate for each project is correct, how can I manage all project in one solution for user CCC ?

To set permissions for specific users to access your .NET Core projects in Azure DevOps, you can follow these steps:

Navigate to your Azure DevOps project and select the “Settings” icon in the bottom left corner.

Click on “Permissions” and select “Project settings”.

Select the project you want to manage permissions for, such as “Data”.

Click on “Security” and select “Add”.

Add the user AAA and select the appropriate permissions for that user, such as “Read” or “Contributor”. Repeat this step for user BBB and the “ViewModel” project.

To grant user CCC access to the entire solution, you can add them to the “Contributors” group, which will give them access to all projects in the solution.

To ensure that the project references in your solution are set up correctly, you can use Azure DevOps pipelines to build and deploy your solution. In your pipeline, you can specify which projects to build and how to package and deploy them. You can also specify any project dependencies or references that need to be included in the build.

Once your pipeline is set up, you can trigger a build to test that everything is working correctly. If there are any issues with your project references or dependencies, you can review the build logs to identify and fix the issue.

Leave a Comment