|
Might I also add NUnit? It's changed the way development is done in these parts (and many others, I'd guess).
--
Herb Warren
|
|
|
|
|
We still have to support Windows 95 in many cases, and AFAIK .NET apps won't even run on 95.
We also have issues when customers download our stuff, even though Microsoft thinks that cusomters won't mind a 20 meg download, many of our customers will certainly complain.
Internally, though, there's a prototyping team that uses it. It would not be unheard of for us to use some C# or something for some internal web apps, too, but who knows.
No single raindrop believes that it is responsible for the flood.
|
|
|
|
|
Still supporting Windows 95? im guessing your at a banking company or Financial company? I noticed they usually still support alot of older operating systems.
Anyhow, even if your company doesnt use .NET I would suggest you start learning it on the side.
|
|
|
|
|
Oh, that same company did pay for an on-site C# class. Regardless of whether we ever use .NET for anything or not, knowledge is power.
No single raindrop believes that it is responsible for the flood.
|
|
|
|
|
Most financial companies use NT.. they have to for security reasons, and while some still have NT4 I don't think I've come across any bank larger than 10 people who would even consider having W95 installed on a PC.
|
|
|
|
|
Not that I use it, but just to be fair (as there isn't an option of typing your own option). There are also .NET languages not developed by Microsoft as well (like Fujitsu COBOL.NET[^])
--Colin Mackay--
"In the confrontation between the stream and the rock, the stream always wins - not through strength but perseverance." (H. Jackson Brown)
Enumerators in .NET: See how to customise foreach loops with C#
|
|
|
|
|
I think that is what the Other option is for. Otherwise Chris would have had to list all 20+ .NET languages (Fortran, COBOL, J# etc. etc. etc.)
regards,
Paul Watson
Bluegrass
South Africa
Brian Welsch wrote:
"blah blah blah, maybe a potato?" while translating my Afrikaans.
Crikey! ain't life grand?
|
|
|
|
|
Obviously!
--Colin Mackay--
"In the confrontation between the stream and the rock, the stream always wins - not through strength but perseverance." (H. Jackson Brown)
Enumerators in .NET: See how to customise foreach loops with C#
|
|
|
|
|
I'm the only coder and my boss wouldn't know the difference anyway so I'm not sure if you could call it a standard, but it's C# for me. The case-sensitivity helps with my lack of creativity in thinking of local variable names.
Charlie
Here I am. Love me.
|
|
|
|
|
Me the first one to cast the vote
Me voted for VB .NET, not coz we love VB (infact we do a bit) but it is coz the C# editor of VS .NET is not that much cool as compared to the VB one. I mean in C# we have to type case-sensative variable names and intellisense is not that much intelligent. Anyway, being C Person, I still, whenever get chance, write code in C#. C Rules!
mE
-------------------
IMPORTANT NOTICE: No trees were killed during the sending of this message but a large number of electrons were terribly inconvienced.
|
|
|
|
|
fadee wrote:
Me the first one to cast the vote
Congratulations.
fadee wrote:
coz the C# editor of VS .NET is not that much cool ... in C# we have to type case-sensative variable names
I think that is because C# (like C and C++) has case sensitive variable names rather than the editor being uncool.
--Colin Mackay--
"In the confrontation between the stream and the rock, the stream always wins - not through strength but perseverance." (H. Jackson Brown)
Enumerators in .NET: See how to customise foreach loops with C#
|
|
|
|
|
amen.
A student knows little about a lot.
A professor knows a lot about little.
I know everything about nothing.
|
|
|
|
|
Yup but you have noticed that VB .NET is also kind of case sensative?
Consider
dim DBEnumValue as Integer
Now whatever you type (e.g. dbeNUMvALUE) it will automatically be converted into correct case, I mean the one in which it was declared.
Can't MS ppl impart such kind of facility in C# editor... I mean for me, it would be a blessing
-------------------
IMPORTANT NOTICE: No trees were killed during the sending of this message but a large number of electrons were terribly inconvienced.
|
|
|
|
|
fadee wrote:
Can't MS ppl impart such kind of facility in C# editor
No. Because C# is case SENSITIVE. Therefore myVariable is not the same as MyVariable unlike VB where they do mean the same thing regardless of what the editor does.
--Colin Mackay--
"In the confrontation between the stream and the rock, the stream always wins - not through strength but perseverance." (H. Jackson Brown)
Enumerators in .NET: See how to customise foreach loops with C#
|
|
|
|
|
|
Michael P Butler wrote:
And with that sentence, you have just shown why VB programmers have such a bad reputation amongst C++ developers.
yeah... but you know, I know a thing; no-matter-what-sophisticated evironment or tool I use... but whenever I open the blue environment of Turbo C++ 3.0 - boy I remember the day when I got into university; and start feeling at home - C syntax is kind of mother language syntax... Wowee... boy... Mother Language Syntax... what a term
-------------------
IMPORTANT NOTICE: No trees were killed during the sending of this message but a large number of electrons were terribly inconvienced.
|
|
|
|
|
fadee wrote:
Wowee... boy... Mother Language Syntax... what a term
Do you have any more of that stuff you're on left over for the rest of us?
- Nitron
"Those that say a task is impossible shouldn't interrupt the ones who are doing it." - Chinese Proverb
|
|
|
|
|
what you think?
ha ha ha... what about sharing yours?
-------------------
IMPORTANT NOTICE: No trees were killed during the sending of this message but a large number of electrons were terribly inconvienced.
|
|
|
|
|
reputation??
What are you talking about?
I do NOT thik VBer has any reputation!
|
|
|
|
|
Actually, in my opinion, I do not see much different between VB.NET and C#?
Sonork 100.41263:Anthony_Yio
|
|
|
|
|
WOW... there is no difference between...
dim MyVariable as Integer
and
Integer MyVariable;
??? I think the last one is more cool...
-------------------
IMPORTANT NOTICE: No trees were killed during the sending of this message but a large number of electrons were terribly inconvienced.
|
|
|
|
|
You can do this in VB.NET
dim MyVar%
which is the same as
dim MyVar as Integer
Anyway, it is just a matter of taste.
For me, I would rather choose between, to .NET or not to .NET.
Sonork 100.41263:Anthony_Yio
|
|
|
|
|
ha ha ha... Your saying could be right in a sense... and No Comments
btw me myself is C then C++ then Java then C# then VB .NET converted creature... so no offenses to everyone
btw, here I remember song of shrek; Bad Reputation; Here, sing with me...
I don't give a damn about my reputation
You're living in the past, it's a new generation
Hey, a girl can do what she wants to do
And that's what I'm gonna do.....
yeeeeee haaaaaaa!!!!!!
ha ha ha...
-------------------
IMPORTANT NOTICE: No trees were killed during the sending of this message but a large number of electrons were terribly inconvienced.
|
|
|
|
|
I don't understand the point about Intellisense not being much good, I see no faults with it, I like the way it displays my XML Comments for my own classes and methods.
For my team C# is the standard (My decision). This was for a few reasons, a big part of which was the much greater supply of documentation and examples already available in C#, but also when looking at other tools, tools such as NUnit, NAnt and NDoc really stand out. Another big influence was the ability for C# and Java developers to understand each others code fairly easily.
Personally, I believe VB.Net was created to keep VB6 developers (of which I was one) from feeling too pissed off at losing the massive intellectual investment they made in becoming experts in their language. I think the initial learning curve going from VB6 to either C# or VB.Net is so great, that it doesn't really matter which language you choose, it will be difficult, but ultimately worth it.
I don't like the way VB.Net has methods that are not part of an object I think this was a decision made partly to please VB6 programmers, and partly to make it look like a different language to C#
Being in a minority of one, doesn't make you insane George Orwell However, in my case it does
|
|
|
|