Getting Slammed with Errors (Screenshot included)

[Lairinus]

I'm using Visual Studios Express for my current project and upon importing NGUI to a blank project, I received one error about an enum not containing a definition for Blackberry. After I deleted that line, 15 errors popped up:http://postimg.org/image/rlkv9bj53/


Now, these errors don't actually interfere with Unity. I can still play the game fine and use any NGUI Components that I want with no problems whatsoever. It just seems a little excessive to have 15 errors always lingering around that I'll never be able to get rid of.

Is there a solution?

** Just went through and deleted everything causing an error**

Will this cause a problem down the line?


Also, I've had this problem in the past but I fixed it. I tried replicating the fix and it doesn't seem to work with the 3.0.8 update.

This also happens before and after I ran the 3.x update asset.

[ArenMook]

Does Unity even support Visual Studio Express? I do all my work in VS 2010 Pro and it works as expected.

Looks to me like your Editor-side scripts can't see the Runtime scripts. This means that VS Express doesn't support dependencies, so it's not going to work properly.

Don't "fix" things to make it compile in VS Express. You will only break NGUI's functionality on the Unity's side.

[Lairinus]

Unity supports VS Express but without the "click to open" functionality as with Mono and VS pro. I'm sure a bunch of other things aren't included but... yeah.

Thanks for the advice, though. Because I don't like Mono, I'm going to use NGUI while modified until (if) it breaks. At that point I guess i'll have to get VS pro.

[ArenMook]

Since the "errors" you see are on the editor side, you won't see any problems with run-time scripts. You will simply be missing NGUI editor functionality... which is extensive.

[Asse]

Seems like the UNITY_EDITOR define isn't set.

[Lairinus]

Thanks, Asse. I actually downloaded the trial for VS 2013 and got the same error which caused some intense rage.

Haven't personally messed around with too many editor scripts, but it needs to be configured to "Debug" not "Release" with editor defines.