Full redeploy on rebuild

1

Why does meadow re-deploy ALL assemblies each time I build my code !!!

2>[01/09/2020 15:16:57] Deploying to Meadow on COM7…
2>[01/09/2020 15:16:57] Initializing Meadow (00:00:00.0001501 since last.)
2>[01/09/2020 15:17:12] Device (00:00:14.0616481 since last.)
2>[01/09/2020 15:17:12] Checking files on device (may take several seconds) (00:00:00.0149793 since last.)
2>[01/09/2020 15:17:42] Deploying for the first time may take several minutes. (00:00:30.1399184 since last.)
2>[01/09/2020 15:17:42] Writing App.exe (00:00:00.0276212 since last.)
2>[01/09/2020 15:21:02] Writing GraphicsLibrary.dll (00:03:20.0198120 since last.)
2>[01/09/2020 15:24:22] Writing Meadow.dll (00:03:20.0301343 since last.)
2>[01/09/2020 15:27:42] Writing Meadow.Foundation.dll (00:03:20.0134367 since last.)
2>[01/09/2020 15:31:02] Writing mscorlib.dll (00:03:20.0116711 since last.)
2>[01/09/2020 15:34:22] Writing System.Core.dll (00:03:20.0066711 since last.)
2>[01/09/2020 15:37:42] Writing System.dll (00:03:20.1735729 since last.)
2>[01/09/2020 15:41:02] Writing TftSpi.dll (00:03:20.1121509 since last.)

Why do all the assemblies take 00:03:20 !?
Finished deploying at 15:45 - 28 minutes to deploy - what a joke !

Sorry but using the Meadow board is always such a painful experience, I am migrating across to NanoFramework which is quick to deploy and has full debug facilities, networking etc.

Andy

2

Okay, after much pain re-flashing the OS (needed to replace the ST driver with the help of Zadig), the deploy is much quicker :slight_smile:

Might persevere for a bit longer (until I give up waiting for debugging to be implemented !)

Andy

3

Nope, it is back doing it again.
New application took 20 minutes to download and run.
Made a one line change and again deploying ALL assemblies - WTF !

1>------ Build started: Project: 24AA02E48, Configuration: Debug Any CPU ------
2>------ Deploy started: Project: 24AA02E48, Configuration: Debug Any CPU ------
2>[20/09/20 12:32:23] Deploying to Meadow on COM7…
2>[20/09/20 12:32:23] Initializing Meadow (00:00:00.0000658 since last.)
2>[20/09/20 12:32:29] Device (00:00:06.3153786 since last.)
2>[20/09/20 12:32:29] Checking files on device (may take several seconds) (00:00:00.0223750 since last.)
2>[20/09/20 12:32:59] Deploying for the first time may take several minutes. (00:00:30.3191172 since last.)
2>[20/09/20 12:32:59] Writing App.exe (00:00:00.0362130 since last.)
2>[20/09/20 12:36:19] Writing Meadow.dll (00:03:20.0514533 since last.)
2>[20/09/20 12:39:39] Writing Meadow.Foundation.dll (00:03:20.0169533 since last.)
2>[20/09/20 12:42:59] Writing mscorlib.dll (00:03:20.0454271 since last.)
2>[20/09/20 12:46:19] Writing System.Core.dll (00:03:20.0084705 since last.)
2>[20/09/20 12:49:39] Writing System.dll (00:03:19.9997531 since last.)
2>[20/09/20 12:52:59] Resetting Meadow and starting app (30-60s) (00:03:20.0023429 since last.)
2>[20/09/20 12:53:02] Deployment Duration: 00:20:39.3371541 (00:00:02.5190878 since last.)
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
========== Deploy: 1 succeeded, 0 failed, 0 skipped ==========

Deploy started at 12:32 and took 20:39.833 minutes

It is interesting that several DLLs take more or less the same time to deploy 00:03:20 - could this be a timeout ?

Andy

4

Can anyone from Wilderness Labs comment on this please !!
It is unusable to have to wait 20 minutes each time I make a change to my code.

Andy