I know these aren’t going to cause any problems when running in unity but in visual studio if I reference the new unity3 unityengine.dll file I get a lot of errors that I didn’t get when using the unity 2.6 unityengine.dll.
They aren’t errors because of the api changes they are quite strange things such as :
Does anyone have a clue whats causing these or any idea how to fix?
cheers
Sorry to say I can’t offer a solution, but am interested too in a resolution for this. I started a thread about this but didn’t get any resolve. Went over to Monodevelop as the warnings were annoying me which was a shame cause I like using ReSharper in VS.
Here is my thread:
http://forum.unity3d.com/viewtopic.php?t=58362&highlight=
Regards,
Matt.
ah apologies I didn’t find another thread based on this, is this something the unity devs are aware of? seems to be something is conflicting within the dll itself. Ah well I hope there will be a solution soon I haven’t had much fun getting into monodevelop
I decided to upgrade to VS2010 today and there are no warnings or conflict in there.
Regards,
Matt.
likely you did something wrong and for some reason the project runs now in .NET 4.0 instead of .NET 2.0
also ensure to not have using UnityEngine; and using System; in there, that will commonly not bring much joy.