The Underscore Archives

On 14/12/2007, Peter Marshall <marshallp at sparkdata.co.uk> wrote:
> VS2005 after SP1 is quite stable, but before that we used to get loads and loads of crashes - especially using one of the major new features of 2005 which was to able to debug without recompiling.  Yes, that you could do in VB6!
>
> Not a problem running 1.1 & 2.0 on the same webserver, just need to tell IIS which one to use for which site.
>
> You can do a straight migration, but we've used the change to bring in some new coding standards so not done much of it ourselves.
>
> We're predominantly a VB house here and of two recent leavers, one was a real new technology junkie and left to go somewhere to do bleeding edge stuff in C#, but converted his team back to VB.net after a couple of months.  The other still works in C# and his view was that there's not a big difference between them, but that a lot of the Beta/freebie stuff available out on t'interweb is done in C#.
>

I've not dealt with VB, never needed to until recently where I
converted a VB component to a  C#.Net one (basically rewrote it). As a
language I like C# a lot, it's quick to develop and true typed OO,
syntacticly almost identical to Java. The beauty of the .NET framework
is the fact that you can code in any language that meets the
standards, so whatever your team can do language wise you can probably
code in it. It's compiled MSIL at the end of the day.

MS head hunted the chap that developed Delphi by my understanding, and
he was a key part in developing C#. I'm surprised anyone would convert
from C# to VB, IMO C# is the language of choice when developing in the
.NET framework.

Though I'm not an MS evangelist, just take a look at the pricing
structure for team foundation!

rick (not Rick)

-- 
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
-Benjamin Franklin