To all those who have released paid assets on the Asset Store (something with scripting in it), did you use Unity Script or C#, and why?
bump (wow, bumpy road here)
I prefer C#, first of all because it’s greatly supported in Visual Studio. Second reason is that I don’t trust Unity Script too much, although I know it may produce the same CIL code if used carefully, but still… And also, I have found the templates feature in C# useful a couple of times.
I use both.
Not sure why though 
I use c# in all of my personal work as it is has all of the goodies that make development better, and it is seems to be more monodev friendly. But for paid assets i have used both, but i lean more on uniscript as i is what new comers usually learn and they are the most likely to need a paid scripting pack as i only do scripting packs. in my latest release i have coded the source in both for the user to decide which version they would like
SecureClient, one of the assets I sell on Asset Store would be impossible to achieve if I’ve used Unity’s JavaScript.
SecureClient acts pretty much like a focused anti-virus to prevent use of debuggers like cheat engine, some considerably big studios working with Unity are using SecureClient today mainly on their webplayer and standalone windows builds; Some have requested open source code to expand it internally and to me is clear they would NOT want to use it if made with UnityScript.
C# was important in this case because if not for an interface with .NET 4+ the game-guard system wouldn’t work at all…
Just an example of how JS may be limited for certain things.
Very simply- as someone who does a lot of mobile stuff, I groan when I find an asset in unityscript, because mostly, it’s not done with #pragma strict.
This has led me to favour c#, because once you’re using pragma strict, your syntax / readability is no better than c# anyway, and explicit casting in unity script can look really horrible- even clunkier than c#.
Mike
@runonthespot