[Fix] *csproj, *.props, .git* configuration

[cschuchardt88]

Description

Configuration the repo and project files for easy organization (based off the same way we had with neo repo).

Also added back the pretty styling for on the nuget.org site

Nuget styling

Change Log

• Add File ./neo/neo.png
• Add File ./neo/README.md
• Add File .gitattributes
• Modified File .gitignore
• Modified File plugins\Directory.Build.props

Fixes # (issue)

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?

• Unit Testing
• Run Application
• Local Computer Tests
• No Testing

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

[erikzhang]

However, there is currently no package that need to be published to NuGet.

[cschuchardt88]

@erikzhang

However, there is currently no package that need to be published to NuGet.

All the plugins and Neo.ConsoleService

With the plugins on nuget its will be easier to use, replace and management the below problem now that we are using multiply repos.

neo-node/src/Neo.CLI/config.json

Lines 28 to 30 in 1c8930c

	"Plugins": {
	"DownloadUrl": "https://api.github.com/repos/neo-project/neo/releases"
	}

[erikzhang]

With the plugins on nuget its will be easier to use

I think NuGet packages are for development. I don't see how it makes the plugins easier to use.

[cschuchardt88]

"Plugins": {
"DownloadUrl": "https://api.github.com/repos/neo-project/neo/releases"
}

The above code for the config.json file automatically downloads the files from that URL. But can switch the URL to use nuget site to download the plugins for neo-cli.

[erikzhang]

Is it possible to automatically publish the plugin's DLLs to GitHub Releases instead of NuGet using GitHub Actions?

[cschuchardt88]

Is it possible to automatically publish the plugin's DLLs to GitHub Releases instead of NuGet using GitHub Actions?

Yes, Before n4 development I had some PR to Automate the process

See - neo-project/neo#4181 - I will be porting to this repo