[RESOLVED] The end of Visual Basic

[JuggaloBrotha]

Not true: parts of it are C++, parts of it even in VB.Net.

Nearly true though.

The actual compilers and most tools, the CLR, and big parts of the IDE are C++.

I was told by an MS person in the vbf slow chat that the FW was made all in c#, the CLR was made in c++ and the VS IDE was made in c# & vb.net

So according to MS, the FW was made in c# like I said.

Not that much of that really matters much.


I'm still awaiting the Grand Reunification of .Net with Java. Then we might end up with a single language hybridizing Java and C#.

Hmmm, a unification between MS and Oracle. I highly doubt that'd ever happen, let alone a "reunification".

[techgnome]

I was told by an MS person in the vbf slow chat that the FW was made all in c#, the CLR was made in c++ and the VS IDE was made in c# & vb.net

So according to MS, the FW was made in c# like I said.

that tracks with what I've seen in the FW, and what I've been told by the VS Developers on more than one occasion.
In fact the VS2010 IDE (the GUI part) was done in XAML. It's one of the reasons some of us have issues with it.

-tg

[JuggaloBrotha]

that tracks with what I've seen in the FW, and what I've been told by the VS Developers on more than one occasion.
In fact the VS2010 IDE (the GUI part) was done in XAML. It's one of the reasons some of us have issues with it.

-tg

XAML is just a styling thing, the code behind the GUI layout is probably mostly c# (though some features are probably in vb.net still) but I'd bet more of VS2010 is in c# than anything else.

[gep13]

It's one of the reasons some of us have issues with it.

Out of curiosity, like what?

[techgnome]

The delay and the repainting that goes on when switching from code to the designer, and vice versa... That was the biggest one for me.

-tg

[gep13]

Hmm, I can't say that I have seen this issue, but then I am mainly in web applications, going between ASPX and code. Are you talking about switching between Windows Forms and Code?

Gary

[NeedSomeAnswers]

The delay and the repainting that goes on when switching from code to the designer, and vice versa... That was the biggest one for me.

Are you using XP, Vista or Win 7 ?

[techgnome]

Gary - winForms...
NSA - Take your pick: XP & Win7.

It's a known problem... I've seen several people complain about it. It has to do with the IDE compiling the form in the background when you switch. Doesn't seem to be a lot that can be done about it.

-tg

[JuggaloBrotha]

What I don't like is if you're in the code window and you use a control by name (and you haven't renamed it on the form itself yet) so you use the new name in code first then when you switch to the form to name the control (so the code compiles) you can't because the stupid IDE shows the form's compile error message and not the form with the controls on it. Which leaves me having to go back to the code, change the variable then go to the form, rename the control and then go back to the code... it's one of the larger reasons to why I'm not using VS 2010 much at all. Also the default syntax highlighting bugs (whoever picked class names to be shown in light green when the code window is white should be shot) and changing it all to VS2008's highlighting is huge pain since there's way to many color options to change to get it right, I just dont bother.

[gep13]

Gary - winForms...
NSA - Take your pick: XP & Win7.

It's a known problem... I've seen several people complain about it. It has to do with the IDE compiling the form in the background when you switch. Doesn't seem to be a lot that can be done about it.

-tg

Interesting. I will need to keep an eye out for this then.

I am away to be getting my head into Windows Forms again soon.

Gary

[Jenner]

I'm also less-than-impressed at VS2010's IDE. The UI is sluggish for me as well (Win7 Ultimate on an Intel i7) compared to 2008 and the highlighting default options stink. It also seems to annoyingly and hyper-actively jump on errors before you get done typing the line much like how C# 2k8 behaves. I have noticed I get a lot more designer compile errors as well when I code for some of the stupidest things.

[techgnome]

That's the other major complaint I hear... and it comes from the overly aggressive background compiler. That annoys me less than simply switching from form designer to code and back again... From designer to code I get... it's picking up any UI changes... but going from code to designer... it shouldn't... but eh, it is what it is.

-tg