sync to Neo.SmartContract.Framework v3.0.0-rc3#44
sync to Neo.SmartContract.Framework v3.0.0-rc3#44vncoelho merged 14 commits intoneo-project:masterfrom
Conversation
|
Duplicate of #43 |
csharp/NEP17/NEP17.cs
Outdated
|
|
||
| public static UInt160 GetOwner() => Owner; | ||
|
|
||
| public static UInt160 GetOwner2() => Owner2; |
csharp/NEP17/NEP17.cs
Outdated
| [ManifestExtra("Description", "This is a NEP17 example")] | ||
| [SupportedStandards("NEP-17")] | ||
| [ContractPermission("*", "onNEP17Payment")] | ||
| [ContractPermission("*", "*")] |
csharp/NEP17/NEP17.csproj
Outdated
|
|
||
| <ItemGroup> | ||
| <PackageReference Include="Neo.SmartContract.Framework" Version="3.0.0-preview5" /> | ||
| <PackageReference Include="Neo.SmartContract.Framework" Version="3.0.0-CI00300" /> |
There was a problem hiding this comment.
Missing NuGet.Config file
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<packageSources>
<clear />
<add key="MyGet-neo" value="https://www.myget.org/F/neo/api/v3/index.json" />
<add key="NuGet.org" value="https://api.nuget.org/v3/index.json" />
</packageSources>
</configuration>
We can iterate examples if any code style changes but not do anything together before release, it could help developers to know the changes step by step. |
Agree, it's good for me. I'm writing sc on neo and it makes the example more clear and these methods are all compatible with the latest compiler as what I tested. |
|
The NEP-17 example should inherit |
update csproj
All done. |
|
@erikzhang pls review again. |
|
@shargon pls review again. |
|
@erikzhang Merge? |
vncoelho
left a comment
There was a problem hiding this comment.
Working as expected. Thanks,
Close #46