Skip to main content
Game Development

Return to Answer

edited body
Source Link
Tetrad
Tetrad
  • 30.1k
  • 12
  • 96
  • 143

You should probably stick with MonoDevelop. It's not as polished as visual studio but is the only debugger you're going to be able to use with Unity 3.

Personally I use Visual Studio Professional when I'm on WIndowsWindows, and all of our projects stick to C# exclusively. It's a great IDE and the C# integration (read: autocomplete) is pretty good.

You should probably stick with MonoDevelop. It's not as polished as visual studio but is the only debugger you're going to be able to use with Unity 3.

Personally I use Visual Studio Professional when I'm on WIndows, and all of our projects stick to C# exclusively. It's a great IDE and the C# integration (read: autocomplete) is pretty good.

You should probably stick with MonoDevelop. It's not as polished as visual studio but is the only debugger you're going to be able to use with Unity 3.

Personally I use Visual Studio Professional when I'm on Windows, and all of our projects stick to C# exclusively. It's a great IDE and the C# integration (read: autocomplete) is pretty good.

Source Link
Tetrad
Tetrad
  • 30.1k
  • 12
  • 96
  • 143

You should probably stick with MonoDevelop. It's not as polished as visual studio but is the only debugger you're going to be able to use with Unity 3.

Personally I use Visual Studio Professional when I'm on WIndows, and all of our projects stick to C# exclusively. It's a great IDE and the C# integration (read: autocomplete) is pretty good.