2.0.6 Update Compile Error Bug (SOLVED : Unity's fault, not NGUI)

[ENAY]

After updating to the latest version of the NGUI I get the error:-

"Assets/NGUI/Scripts/Interaction/UIButton.cs(19,33): error CS0115: 'UIButton.OnEnable()' is marked as an override but no suitable method found to override"

Clearly something is odd, have just had a few odd looks from other people in the office since everyone has just updated their the project from the assett server and can no longer compile.

I am looking into it now.

[edit]

Well I am not sure what is wrong, if I fix that error, another error appears, and another, did I do the update wrong?
I deleted all of the original NGUI stuff and then added the new update. Did I do something wrong?

[ArenMook]

Did you start a new scene beforehand? Sometimes Unity holds on to certain references. You need to make sure NGUI is wiped out before re-importing it. This includes removing it from the Plugins folder if you moved it there.

[ENAY]

Create a new scene?

We have the NGUI used in multiple scenes so I am not sure what you mean about making a new scene.
How do we delete the Unity references? It is odd because the readme still says 2.0.1 even though the textfile is named 2.0.6

[ENAY]

Well we have no idea what has gone wrong. Now if we delete the original source code from the asset server (in other words revert the project) the non compilable source code just magically reappears again. 

Looks like we will have to create a new project from scratch and reimport all the old source code and assets. 

[ArenMook]

Asset Server? Well, that pile of ridiculously overpriced shit is your first problem right there.

Using the free and much more powerful Git or even SVN you'd have much easier time.

Straight from NGUI's readme:

--------------------
 How To Update NGUI
--------------------

If you have the Professional Edition of NGUI that comes with Git access, just pull the latest changes.

If you have a Standard Edition:

1. In Unity, File -> New Scene
2. Delete the NGUI folder from the Project View.
3. Import NGUI from the updated Unity Package.

[ArenMook]

Asset Server has a stupid amount of bugs and weirdness associated with it. From randomly missing files to corrupt repositories. We tried it 3 years ago and quickly learned better. Watching the beta boards, people are still crying about it and Unity is doing nothing.

The fact that Unity robs people $500 per developer for something that I would never use even if it was free is just mind-boggling.

[ENAY]

You're not kidding there. We have often crazy problems. Like I will update from the server and it will ask me to confirm whether or not I want to rename some graphic assets that a graphics artist has created and has nothing to do with me.

Anyway, everything is only working fine on the machine of the boss (who installed NGUI) and it is just everyone else who is struggling. So certainly there is a problem with the asset server.

[dlewis]

Yea, Asset server is a pain. I spent a lot of time this morning trying to get NGUI updated.

I had to remove NGUI, commit that and then update and make a second commit (then someone else broke NGUI and I have an even harder time fixing it). I miss the days of perforce (we should be moving off the asset server soon...hopefully).