# com.unity.ads Packman Package
## Local Development
#### Getting Started
1. To get started with this repo, you need the following tools:
- An empty Unity 2018.3 project (Can be created from Unity Hub, a standalone version of Unity, or the command line):
```sh
/Applications/Unity/Hub/Editor/2018.3.3f1/Unity.app/Contents/MacOS/Unity -quit -createProject UnityAdsTest
```
- This repo, cloned to your local file system (We will assume its cloned at `~/git/com.unity.ads` going forward)
2. Open the empty Unity project created and navigate to: `<ProjectRoot>/Packages/`
2. Create a symlink to the git repo you cloned
```ln -s ~/git/com.unity.ads com.unity.ads```
2. Update the manifest.json file located in `<ProjectRoot>/Packages/` with the following change:
```"com.unity.ads": "3.0.3"` -> `"com.unity.ads": "file:com.unity.ads"```
Thats it. Open the empty project you created in step 1 and if you look in the file explorer under the Packages directory you will see the local package source code and its fully editable with whatever default editor you use with Unity.
#### Compiling
The Package manager source code is automatically built when you first open a project, and anytime any of the source code managed by the assembly definition files changes. Any time you modify any of the source code in our project, unity will rebuild the package dlls immediately upon returning focus to unity. You can then immediately begin testing your changes in the editor without needing to invoke any build scripts or move assets around.
#### .NET Framework version
*more details to follow*
.NET 3.5 should be used when developing the package source code in order for us to maintain backwards compatability to Unity 5.6.6. We will solidify this decision with the 3.1 release, and for now this is mearly a guideline that should be adheared to until we decide to officially swap to .NET 4.6 for development. As a side note, this restricts us to C#4 constructs as Unity pairs .NET versions with C# versions and currently there is no way to alter this.
## Testing
Inside Unity, navigate to `Window => General => Test Runner` to open the test runner dialog. Inside, you can then click `Run All` to run tests.
After setting up the local environment, all tests in the package should be visible in the Test Runner window. If you want to be able to run the tests for a given package without going to the effort of setting up the development environment above, you can simply add the following to your package manager manifest file after the dependencies section: `"testables": [ "com.unity.ads" ]`. You should only need to add the testables json when you want to run the tests for a given package that you are not setup to locally develop for. This is useful when you are testing a package on staging and want to run its tests locally.
## Staging
Deploying the package to Staging happens by creating a tag using the following format: `v3.0.3-preview.1` or `v3.0.3`. Once the tag is created, the yamato build system will run all the test builds and if they pass, it will automatically deploy the package to bintray staging. You can monitor the status of the build jobs [here](https://yamato.prd.cds.internal.unity3d.com/jobs/36-Ads%2520Package)
#### Testing Staged Packages
In order to test a package that has been deployed to staging, you must update your project's package manifest to look at staging instead of production. Navigate to: `<ProjectRoot>/Packages/` and open `manifest.json`. Add the following line as a sibling element to dependencies (before or after this json element): `"registry": "https://artifactory.prd.cds.internal.unity3d.com/artifactory/api/npm/upm-candidates"`
## Production
Refer to [this](https://docs.google.com/document/d/1yN5cEnba4kJEU_hKjwnpl4h0TioWS7l2bo5cQSG9UOc/edit) doc on how to release the package to production. Please note that you should do all your testing as a preview package, and *ONLY* once you are *COMPLETELY* confident the package is fully tested and ready to be merged to production should you cut the final non preview version, deploy that to staging, and finally deploy that to production. FYI, once a version is pushed to staging, you cannot delete it, and so if your not ready to push that version to production as is, you will have forever lost that version number.
## Asset Store
The Asset Store (.unitypackage) is build via a shell script in the AssetStoreTemplate~ folder. It compiles platform specific dll's using mcs (Mono Compiler). This compiler is capable of converting the code from C#7 ([*most language features supported*](https://www.mono-project.com/docs/about-mono/languages/csharp/)) down to .NET 2.0 compliant code. By doing this we are then capatible with Unity 5.6.6 running on .NET 3.5.
没有合适的资源?快使用搜索试试~ 我知道了~
资源推荐
资源详情
资源评论
收起资源包目录
XZ_excavatorProject.zip (2000个子文件)
00000000000000001000000000000000 4KB
00000000000000002000000000000000 4KB
00000000000000003000000000000000 4KB
00000000000000004000000000000000 4KB
00000000000000004100000000000000 4KB
00000000000000005000000000000000 4KB
00000000000000005100000000000000 4KB
00000000000000006000000000000000 4KB
00000000000000006100000000000000 4KB
00000000000000007000000000000000 4KB
00000000000000007100000000000000 4KB
00000000000000008000000000000000 4KB
00000000000000009000000000000000 4KB
0000000000000000a100000000000000 4KB
0000000000000000a500000000000000 4KB
0000000000000000b000000000000000 4KB
0000000000000000b100000000000000 4KB
0000000000000000c000000000000000 4KB
0000000000000000c100000000000000 4KB
00187582b67e7654b914b5a0d37daafb 15KB
002876826ed0e4ee8b719bd036aed7dc 4KB
004c2acccab5a0f68b9cb77faf36b272 7KB
0050a72dbdb2aaf4247768291cc8bda8 4KB
006ad50a73ed144b9a69a6525c78ada1 5KB
007e0c158ab2b37661ba3595d3480617 7KB
0099c078d375f49cb8796570cbbb02d0 3KB
009a08243f5fa69e0d0c97fb9891f204 5KB
009d9ac5e10d71c14dec6e686427cdb8 4KB
00c8bc824ebda4a0682e0dfdcceeb260 4KB
00e923a8d73529d851c56d7cc9da4131 4KB
00ed25e3298ac440eb327c706a964e3a 11KB
010246a07de7cb34185a2a7b1c1fad59 5KB
0127f88343c1ea70c3a295d831567b46 14KB
012c4e7ed80308b09d389444902dff1f 178B
015812e983113a84b95773e55f3cec13 5KB
0165279dc3315e29c849bb550c1cb348 4KB
01798f6e35dd3ea7c00d64b06de2bf2d 18KB
01ada73c4792aba4c937ff5d92cce866 15KB
01cd96d8687272f4898cfd1562079dd7 5KB
01d56afee706990a5bca7dc315860aa3 2.68MB
01da6c5b7c781174d818662ce6f39b8b 17KB
01eddc5a0b90fd84fab3257e589baa57 6KB
01fb1d560777c8cf9e516746af41089f 5KB
0217a80286f79419daa202f69409f19b 6KB
025cf18141eb0f170d69ab289b9f19a6 5KB
027fad36d84070681c7408c62be6a03f 4KB
02893ffb522b490a9fa28eedd2584309 12KB
02b7c86062fedfe55501e0fc09b967d5 17KB
02c55b3670292766317fda79f7480dd8 5KB
02e0e31dcacab4b4370c3fc472a97cc3 21KB
02e1fe0a338b35545a5fed1345848332 6KB
02f771204943f4a40949438e873e3eff 4KB
03007844fd758134da084550d086cc12 5.35MB
0304baf8d224f3e47b22d872c8dcd412 52KB
030f85c3f73729f4f976f66ffb23b875 15KB
0336a32a79bfaed43a3fd2d88b91e974 8KB
033c884ba52437d49bc55935939ef1c6 8KB
0340c989e338c35d02c7389071c3bf4e 13KB
0343ef7e1c0073c42729d100ac01fc3c 6KB
0351af5d82c709a32cf6f3eb708180f2 10KB
0351cfcd38da4b2d5daacaa6a00495dc 13KB
036d03e26977243fa9a2d7af48e51e08 6KB
037b3c64c4a5f69c59bc3e52d0094ceb 17KB
0385892b042687e3d24e78171a0357d5 4KB
0386b6eb838c47138cd51d1c1b879a35 22KB
03945d4123d7d4b129acfacbc8090dc2 4KB
0395014660502a2c5a9f0916c3a80d60 17KB
039fdec261f9d23bfd20464d68584f17 4KB
03ae22b9de3989144a9bebf8972b4fad 17KB
03de73ecd04534d5bdb15fc4fe1a5b98 6KB
03e4cb83697976fc0e97bdaf8c5e1542 8KB
03e4d63665d06f04c8a6cf68133c1592 6KB
0422787a7ba404ebd3a8d4524ba43b81 17KB
04282ea1ced0e2948c2525502b68113e 17KB
043715c55cc89b33b3fe8a8476dcf5ea 4KB
043748262189b068676d6d649bf368c1 4KB
0442ca9515592e05c7f187674af80c1e 5KB
046c3854296c5ec48bac50da6ca248ec 9KB
0483b18f6546a8cb1c6f401fa81c5aea 9KB
048bd1ea46ab3766a38b7ab150d35e53 17KB
0499418dd1de70f8f788a9ed29492753 4KB
04a4f139ecdd6c2ef300d0fb07989d2a 16KB
0524c949ee5cdb35dae59415eb520b3c 17KB
054f66232edda3a3089121baff8cfbc8 10KB
055e70c6f791a12e38bfbd078f426a32 148B
05668f3e8f842f431a06f0356e1b621f 5KB
056819c66570ca54cadb72330a354050 9KB
05778dd1de4433d418793b6f3d3c18cf 7KB
05874c65cd32d041c5733f71c53c0e93 37KB
0589560d5ac4de5731ad947a8f9890cc 5KB
058998673f5ddfed15ed23901ad63d41 5KB
058cba836c1846c3aa1c5fd2e28aea77 31KB
05c30adc4f65aceccc9fe94ad78b816d 5KB
05dac56760427786ead8497a4b4a1e97 14KB
05f173677175adac0e6abbfcda734de1 224KB
05f5bfd584002f948982a1498890f9a9 32KB
05f7f519769978b79b31d063a7fc6fa1 5KB
05f92e4a2414cb144a92157752dfa324 7KB
0636b0a4b3fa8a00598a80c5c1e1b957 4KB
066619c9c9c84f89acb1b48c11a7efe2 14KB
共 2000 条
- 1
- 2
- 3
- 4
- 5
- 6
- 20
资源评论
- 彥爷2023-07-28阅读这个文件,我对挖掘机的工作原理有了更深入的理解,对于我在工程中的应用有很大帮助。
- 蒋寻2023-07-28这个文件提供了全面的挖掘机项目资料,对于需要了解挖掘机的人来说是非常有帮助的。
- 伯特兰·罗卜2023-07-28这个文件提供了详细的目录结构,让我可以迅速找到所需的信息,节省了很多时间。
- 白小俗2023-07-28这个文件不仅有理论知识,还包含了实际操作的示例,对于我来说是一次很好的实践机会。
- 文润观书2023-07-28XZ_excavatorProject.zip包含了丰富的文档和素材,可以帮助我更好地了解挖掘机的使用和维护。
柏雁
- 粉丝: 60
- 资源: 7
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功