-
Notifications
You must be signed in to change notification settings - Fork 1.2k
A Basic Solution Structure to Enable Infrastructure Development #3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| <ProjectGuid>{DF7D2697-B3B4-45C2-8297-27245F528A99}</ProjectGuid> | ||
| <OutputType>Library</OutputType> | ||
| <AppDesignerFolder>Properties</AppDesignerFolder> | ||
| <RootNamespace>Microsoft.PackageDependencyResolution.Tasks</RootNamespace> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How many "tasks" libraries do we expect to have in this repo? This name seems very specific, and not many tasks will be able to live in this assembly.
For example, my next task is to add the tasks for "Generate .deps.json" and "Generate .runtimeconfig.json" files. I don't think they would belong in an assembly named Microsoft.PackageDependencyResolution.Tasks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 with @eerhardt
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, we could explore a rename
As we discussed offline, checking this in to unblock Jenkins work
Importing the publish profiles from the package.
This basic solution includes an empty placeholder project for the PackageDependencyResolution task. (I left out the source of the task because that is a longer review.) This PR is the minimal layout we need to start working on infrastructure tasks (Jenkins, Microbuild etc.). More detailed build.cmd, Settings.targets etc can be fleshed out later.
/cc @333fred @srivatsn @dotnet/project-system