6 replies to this topic

[Schoening]

Hey guys,
I've started reading a bit on C# because i would like to make a indie game with the Unity engine.

I have seen a Tutorial where the person uses SciTe for C# and wondered how SciTe is compared to Visual Studio for C# editing

[Mat]

In the same way coding AutoIt using a hex editor is to using SciTE.

[Manadar]

If you don't use Visual Studio for C# editing then I will find you, come to your house, ring on your door, wait until you open, and then I would tell you to use Visual Studio for C# editing.

[Schoening]

If you don't use Visual Studio for C# editing then I will find you, come to your house, ring on your door, wait until you open, and then I would tell you to use Visual Studio for C# editing.

HAHAHA

Allright ^^ thx

Because of better syntax ehm.. "coloring" ?

[Manadar]

Because of better syntax ehm.. "coloring" ?

SciTE is a code editor. It has syntax highlighting, automatic suggestions and completion, matching brackets, and often a simple way to run your code in the sense of: Start the compiler, start the interpreter, start another program that handles debugging, etc.

Visual Studio is an integrated development environment (always called IDE). A code editor is part of an IDE, but an IDE offers much more functionality. The source code editor, the interpreter/compiler, the debugger are all integrated as part of the same program. Visual Studio also helps you with file management.

There is a whole list of C# language features and .NET libraries to be named which would be much less convenient if Visual Studio did not support them. A prime example of that is the way you can consume SOAP services with WCF. Building a service reference like that would take you about 30 minutes in SciTE if you knew what you were doing, in Visual Studio even a monkey can do it in 10 seconds.

Purely as a code editor, Visual Studio is better than SciTE. Mainly because of IntelliSense. All in all, Visual Studio is much preferred over SciTE because it helps your workflow greatly. The downside is you won't understand all things under the hood (like very useful command line arguments on the compiler), but some would argue that you don't have to.

Edited by Manadar, 24 January 2012 - 02:40 PM.

[Schoening]

thx:)

also: thx to moderator for moving my Topic:)

[Dasttann777]

Try out SharpDevelop, it is free, and whilst not as user friendly as MS, it is still a handy piece of Software.
Hope I helped