Question by AquaticSerpent · Sep 27, 2016 at 10:36 AM · asset compatibility updating bundles

Can changing a plugin from DLL to open source can cause backward compatibility issues?

Hi guys, I would like to release a plugin to the Asset Store.

It's going to be a DLL, and I was wondering if choosing to make it open source in future versions might cause backwards incompatibility.

My main concern is that users using the asset may experience broken references.

Do I have a cause for concern? Anything else I should be wary of?

Thanks!

Add comment · Show 2

tanoshimi · Sep 27, 2016 at 12:01 PM 1

Do you mean "open source"? That's normally a licensing term. Or do you mean uncompiled source (as in, .cs files rather than .dll). I can't see any reason why swapping out a DLL for the source files from which that DLL was compiled should generate any problems.