Re: Separating .net from Visual Studio

  • From: Jared Wright <wright.jaredm@xxxxxxxxx>
  • To: programmingblind@xxxxxxxxxxxxx
  • Date: Tue, 23 Sep 2008 12:32:29 -0400

Hi Jamal, Thanks for the tips. .net 3.5 rather than 2.0 here, but I would imagine the command line options should still be there. I'll start looking at the SDK more, especially for the layout container controls, which I will admit I have no familiarity with as of yet.


Thanks again.
JW
Jamal Mazrui wrote:
As you might guess, I develop EdSharp and FileDir in C# 2.0 using EdSharp.
The .NET 2.0 SDK has a strong set of command-line utilities with
consistent syntax.  Although I have done my best to make the Visual Studio
scripts provide access to the IDE, and so have others, I ultimately found
that I was more productive hand coding forms with a powerful, speech
friendly text editor.  Yes, one gives up code completion, so I often
search MSDN or structured text files I have done of .NET documentation.
I do not like the way an IDE guesses what I want to do, however,
generating code automatically for me, some of which I do not understand or
do not find consistent with my own coding style.  I have found that the
layout container controls work in a more simple and elegant manner than
building forms through the Windows forms designer.

As an example of EdSharp's support for C#, try creating the file
hello.cs with the code below.  Then press Control+Shift+F5 and pick the
C# compiler.  Press Control+F5 to compile.  EdSharp will say "Done!" if
there was no compiling error, thus resulting in the executable hello.exe
in the same folder as hello.cs.  If an error is found, on the other
hand, EdSharp will say it and place the cursor at that point in the
source code.

Let me be clear that this is a personal choice that works well for me.
Others like the code completion and other benefits of the IDE a lot, and
are not bothered by the code generation or other aspects that I find
annoying.  Also, if one is working on a team, the IDE provides ways of
structuring projects that aid collaboration.

Hope this helps,
Jamal

using System.Windows.Forms;

class Program {
static void Main() {
MessageBox.Show("Hello world");
}
}


On Tue, 23 Sep 2008, Jared
Wright wrote:

Date: Tue, 23 Sep 2008 09:43:19 -0400
From: Jared Wright <wright.jaredm@xxxxxxxxx>
Reply-To: programmingblind@xxxxxxxxxxxxx
To: programmingblind@xxxxxxxxxxxxx
Subject: Separating .net from Visual Studio

Hi all, I was wondering what experiences any of you could share about
using any of the .net framework languages outside of Visual Studio? It's
obviously very powerful stuff and stuff I need to be comfortable with,
but I really just am not finding that I like the VS experience.
Apparently I can work with my text editor of choice unhindered with the
.net SDK, but I wanted to know if there are any other practical hurdles
I've overlooked. I don't know many folks that do their .net in something
other than Visual Studio, and I imagine there's a good reason why.
Apologies if it seems I"m cutting some corners here too, I do have a
programming class this semester centered around .net, hence the inquiry
itself, and I'm really trying to find an alternative for VS or at least
figure out VS real quickly, because it's sure making this course
irritating.  Not a lot of fun when 30% seems to be software dev and the
other 70% seems to be fighting with the IDE.Any thoughts welcome.

Best,
JW

__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind

__________
View the list's information and change your settings at //www.freelists.org/list/programmingblind



__________
View the list's information and change your settings at //www.freelists.org/list/programmingblind

Other related posts: