next version of VS.NET

[goodmorningsky]

Does any one know when the next version, maybe VS.NET 2004, comes out?

 

And what kind of functions added on new release?

 

I'm using visual C# 2002 version. It doesn't have good debug tool. Actually debug tool is terrible. for Window/ Web applications!!

And too many tool bugs... bugs.. bugs... --> have caused me too much hastle..

 

I'm waiting for more stable tool with good debug tool as they did on VB6.

 

What do u guys think of all these?

[samsmithnz]

If you can upgrade to C#/ Visual Studio 2003, its better for stuff like that.

 

The only feature that I've really heard about is that they are bringing back edit and continue to vb.net (Like vb6, where you can stop at a breakpoint, fix some code and continue without restarting). Not sure if this will apply to all .NET languages.

[mutant]

Not sure if this will apply to all .NET languages.

Using VS.NET 2004, only VB.NET will have edit-and-continue available. As far as I know there is no plans to include it in VS.NET 2004 for C#.

[samsmithnz]

Do you know if they were doing anything else to make vb.net different from C#? I know that a lot of the REALLY STUPID BUTTMUNCH vb6 crowd was really pushing for .net to be more like vb6. (Which as you can see I don't approve off).

[divil]

Yes, you're quite right. There are a _lot_ of features being introduced in VB.NET 2.0 to make it more like VB6. It's almost sickening.

 

For instance, default instances of forms are back in. The code editor starts hiding things from you like attributes that it thinks are too advanced for you to see. Of course, it's still at the pre-beta stage so anything could change.

[mutant]

If all you are saying Divil will make it to the final version it will unacceptable. I understand they want to make the move the from VB6 not very hard, but there plenty more people who don't need to make a move, instead want to enjoy the new language instead of just a clone of VB6 with a different runtime.

[samsmithnz]

Lets just hope it never comes to this.

 

damn lazy vb6 programmers.

[iebidan]

Well, if VB.NET starts looking like VB6, then I'll stop using it, C# will be the language I'll be using.

Its too bad that edit and continue will not be available for C#, that's the only thing I miss from VB6, but well, I really don't care too much about it

[samsmithnz]

Yeh at first VB.NET really annoyed me. But you're right, if they change vb.net too much I might think more about changing (or not upgrading).

[goodmorningsky]

It's really matter to me, iebidan.

I'm using C#, since I'm familiar to java either.

But, the debug tools in VS.. drive me crazy..

Immediate window doesn't give list of member when I put "." dot after object.. as vb does.. and doesn't support interface related statement..

And when I modify code on break mode, the step doesn't follow right trace..

 

So far it's standable.., but, when you goes to ASP.NET, the debug tool some times work, some times not. I don't know why..

I put break point on Load of web form, it works some time, all of suddent, it doesn't work...

Execution doesn't stop at break point!! sometimes it stop on the code of java script that is added by ASP.NET.

 

I think Microsoft released not ready product thinking only beatting market against Java.. specially for VS.NET..

C#, .NET framework.. itself, it's ok, but not for VS.net..

 

All in one strategy of VS.nEt means "All bugs in one" to me..

[irasmith]

If they do truly make VB.NET more like VB6, I hope they limit the changes to just VB and not invade C# with similiar changes.

 

I am just starting to really get into .NET programming and really love it. I first began working with VB.NET Standard, but some that I have talked with have convinced me to give C# a try.

 

Last night I was happyily reading away in my Professional C# book which was delivered to me yesterday. My VS.NET package is enroute to me and I can't wait to get it installed and start working with C# :)

 

I realize that things change over time and to truly take advantage of new technologies sometimes you just gotta accept change. But I guess for die hard VB6 people who have had VB6 for so many years now, the urge to change may not be that great.

 

So cheers to everyone as I get ready for a weekend of loosing myself in my C# book:cool:

[Volte]

For instance, default instances of forms are back in. The code editor starts hiding things from you like attributes that it thinks are too advanced for you to see. Of course, it's still at the pre-beta stage so anything could change.

"Hide Advanced Members" is already a feature, and it's on by default. I hate it. I spent hours trying to figure out how to load a Graphics object from an hDC, only to find I *had* been looking in the right spot, but Intellisense was hiding 'FromHDC' from me. I thought I was missing a library or something...

 

Anyway, VB.NET truly is the .NET "beginners" language as far as I'm concerned. After getting a good grip on the language, I think most people will probably find C# far better. I still use VB.NET for some things, but for large-ish projects, I use C#.

[divil]

I'm not talking about hide advanced members.

 

The problem is, Microsoft itself regards vb as the "beginner" .net language. And they choose not to stand up to the morass of vb6 programmers who whine that their language is changing. VB.NET 2.0 will therefore contain a number of things that will "baby" up the language a bit.

[reboot]

Will we be able to remove these "things" by removing Microsoft.VisualBasic and/or Microsoft.VisualBasic.Compatibility ?

 

If so, who cares...

 

If not, kudos to Microsoft for continuing to screw up what could be a very good language... :-\

[samsmithnz]

What IS a good language and what COULD be corrupted.

[divil]

reboot: yes, I think you can disable them in the compiler options.

 

Whidbey introduces the concept of "developer profiles". If you pick "vb developer" instead of "c# developer" when you install it, everything will seem a little alien to established vb.net users. More advanced features will be hidden, menu layout will be changed, etc.

 

The way I see it, competant VB developers will get irritated by these things and eventually drift over to C# which is in no danger of getting this treatment. It's not the way it should be, but I think it's what's going to happen.

 

 

Disclaimer: Of course, all this released information about Whidbey is subject to change in the coming year before it's released. It hasn't even gone in to beta yet.

[Roey]

Not a good start to the day reading this doom and gloom posting. I really hope you guys are wrong. I would also move to C# before going back to the VB6 days....