Corey H.

Case 1 - just referneceing TinyCore in your main project baloons the size up

Incrementally deploying assemblies to device
Deploying assemblies for a total size of 64856 bytes
Assemblies not successfully deployed to device.
Deployment to the device was not successful.


For Case 2 - if you have a class library project. Even if that other project includes TinyCore, it does not get pulled in unless you reference EventHandler in the class library project

        public TinyCLRTest()
        {
        }

        public void DoTest()
        {
            // I really don't need to do anything
        }

        //EventHandler OnError;

So For Case2, uncomment the line

EventHandler OnError;

<br class="Apple-interchange-newline">
This will cause your deployment to go From:


Incrementally deploying assemblies to device
Deploying assemblies for a total size of 1456 bytes
Assemblies successfully deployed to device.


To :


Incrementally deploying assemblies to device
Deploying assemblies for a total size of 65208 bytes
Assemblies not successfully deployed to device.
Deployment to the device was not successful.

Long Story Short: TinyCore is not so tiny...


Corey

Hi Corey and welcome to the forums.

Are you sure you only commented out that single line? I'm curious because of this:


That one line appairently makes a difference of 63880 bytes, which is a lot. With a Netduino Plus it's reaching the code memory limitation that way.

Yes, I went back and forth around 5 times verifying it. The fact that this was "odd" is why I mentioned it. I was originally porting a "non-micro framework" project that interacts through a serial port to the "micro framework" and was stumped when it would not deploy. I then removed every class and added items back one at a time until it no longer deployed. THen commented out items in that class until it deployed. The key to the size was referencing the EventHandler class. That is when I noticed that just referencing the event handler in the code caused the deployment size to become very large. There must be some dependent references where if you include that, other assemblies may be referenced or an issue with how the Netduino is loading that assembly.

I can try to pull together a solution that shows just that problem tonight when I get home.

Corey

I also ran into the same file and it resulted in the size of the deployment growing significantly, so your first inclination is correct.

I could leave the reference to tiny core in there if I commented out all references to event handler...

//        public event EventHandler OnError;

Everything deploys just fine:


Incrementally deploying assemblies to device
Deploying assemblies for a total size of 14728 bytes
Assemblies successfully deployed to device.


Add the line to one of your classes:

public event EventHandler OnError;

Incrementally deploying assemblies to device

Deploying assemblies for a total size of 78608 bytes
Assemblies not successfully deployed to device.
Deployment to the device was not successful.

When I remove the reference to TinyCore, I get compile errors on EventHandler. Other than your idea of creating another handler, I don't know the workaround.

Something in that class is causing the size of the deployment to balloon up. Is this expected behavior or is this a bug?( N+ 4.2 app)