Skip to content

feat: Copy plugins to publish directory#30

Merged
DevD4v3 merged 3 commits intomasterfrom
feat/issue-29
Jan 14, 2024
Merged

feat: Copy plugins to publish directory#30
DevD4v3 merged 3 commits intomasterfrom
feat/issue-29

Conversation

@DevD4v3
Copy link
Owner

@DevD4v3 DevD4v3 commented Jan 14, 2024

Resolves #29

The package was published here: https://www.nuget.org/packages/CopyPluginsToPublishDirectory

@DevD4v3
Copy link
Owner Author

DevD4v3 commented Jan 14, 2024

It has been decided to create a target instead of a .props for one reason:

The target files are imported at the end of the project file, so properties such as Configuration and TargetFramework would already be defined. With a .props file, however, it is different, as they are imported at the beginning of the project file, so the value of TargetFramework would not be available (i.e. it is empty).

See https://learn.microsoft.com/en-us/nuget/concepts/msbuild-props-and-targets#packagesconfig-projects

.props is added at the top of the project file; .targets is added at the bottom.

@DevD4v3 DevD4v3 marked this pull request as ready for review January 14, 2024 19:33
@DevD4v3 DevD4v3 merged commit 5fcfe4c into master Jan 14, 2024
@DevD4v3 DevD4v3 deleted the feat/issue-29 branch January 14, 2024 19:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Copy plugins to publish directory

1 participant