[Neo Plugin Fix] Fix targes

[Jim8y]

Description

This pr fixes the issue of multiple targes for plugins while there is only one target specified. Making it impossible for dotnet publish to automatically detect the target.

Fixes # #3344

Type of change

• Optimization (the change is only an optimization)
• Style (the change is only a code style for better maintenance or standard purpose)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Test Configuration:

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[cschuchardt88]

Whats the problem with the Targets?

Reason for so we can do Standard or any other target in feature. Unless you have a problem coming up, than I dont see the point.

This PR breaks github actions and building environment.

[cschuchardt88]

This was fixed already

[cschuchardt88]

Why you approving something is breaks our environment. everyone's inexperienced or lack of knowledge of dotnet is disappointing when the issue is just that.

This break tests and other things in your our github workflows. Including the environment locally.

[cschuchardt88]

Doesnt work in all enviroments, breaks testing and github workflows, along with local development and other frameworks like dotnet standard.

[Jim8y]

This was fixed already

i know we can do this, but why we need to do this while there is only one target supported? why use targets instead of target? and why this can cause problem? BTW, dont worry about approvals, as long as workflow fails, pr can not be merged.

[cschuchardt88]

Because we build for dotnet Standard too from solution or *.csproj that is the reason, or it will fail on other OSS like this PR did. So you need TargetFrameworks not TargetFramework.

[Jim8y]

Close as #3343 (comment)