Is VS 2005 the death of VB.NET?

1. Features from vs 2003 C# still have not made it into VB.NET
2. Poor support for any new features; see the hopeless refractoring support in VB ( one method) as an example..
3. No support for VB.NET breaking problems after almost 12 months..
- vs 2005 VB.NET still cannot compile any decent size project without crashing..
- vs 2005 VB.NET still has basic compiler checking problems.

The ONLY conclusion we have from the above is that MSoft want to move customers off VB.NET, by lack of any support! for VB.NET.

That isn't true, Microsoft is not planning on getting rid of it, no discussion of the sort has ever been made. The reason C# has features VB.NET doesn't is simply the developing team. The C# Team decided to add some of those features. VB.NET has features C# doesn't. I will say, on a personal note, that C# does seem to be favored over VB.NET, mostly because C# was originally created for .NET while VB.NET is somewhat old. But features the VB.NET Compiler does have are marcos. Like casting. CStr, CType, CInt, etc. But, it is really about the developer team.

That isn't true, Microsoft is not planning on getting rid of it, no discussion of the sort has ever been made.

>> The facts above show a different story.. 

 The reason C# has features VB.NET doesn't is simply the developing team.

>> why woudl I care less about the internals of MSoft development, when I buy VS I dont say well let me think who was on this dev team...

The C# Team decided to add some of those features. VB.NET has features C# doesn't. I will say, on a personal note, that C# does seem to be favored over VB.NET, mostly because C# was originally created for .NET while VB.NET is somewhat old.

>> See above, facts are basic  dotnet dev stuff has not been implemented in VB.NET..

But features the VB.NET Compiler does have are marcos. Like casting. CStr, CType, CInt, etc.

>> Also C# does not have the fundermental crashing problems of VB.NET see above..
Note it would appear that C++ is going the way of VB as well in this regard..

But, it is really about the developer team.

>> Dontcare about who is on the dev team, and why should I...

About VB.NET: of course not! VB is very important!

About C++: of course it stays. There are millions of applications written in C++ and even more being written as we speak. I am using C++ for one thing ;-)

If you think some feature are missing in VB, please voice your opinion on MSDN Product Feedback site.

"About VB.NET: of course not! VB is very important!"

 Talk is cheap..

But MSoft actions say otherwise..

A compiler with Breaking problems still not fixed after almost 12 months!!!,

Fact: MSoft is NOT supporting VB.NET...

"If you think some feature are missing in VB, please voice your opinion on MSDN Product Feedback site."

Yet anothjer marketing Joke... right !!

MSoft is judged by results not hype and marketing, and the resuts speak for themselves..

dude_4:

"About VB.NET: of course not! VB is very important!"

 Talk is cheap..

But MSoft actions say otherwise..

A compiler with Breaking problems still not fixed after almost 12 months!!!,

Fact: MSoft is NOT supporting VB.NET...

"If you think some feature are missing in VB, please voice your opinion on MSDN Product Feedback site."

Yet anothjer marketing Joke... right !!

MSoft is judged by results not hype and marketing, and the resuts speak for themselves..

 

Do you do anything other than complain? I have not read one of your posts that wasn't a negitive reply. In the past, you have been told how to properly channel your complaints (i.e. reporting bugs to MSDN, product feedback site, etc.) and you refuse to do so. Nothing is going to come of your negitive feedback. Perhaps you should channel your issues in a more appropriate place such as a blog instead of the forums.

"In the past, you have been told how to properly channel your complaints (i.e. reporting bugs to MSDN, product feedback site, etc.) and you refuse to do so. "

What arrogance.., what makes you assume that you know what someone else other than yourself has done!..

We have conservatively put though about 1,000 probelm reports in various places includign all the MSoft ones, without any progress..

"Nothing is going to come of your negitive feedback. "

Nothing has come of our positive feedback...

"Perhaps you should channel your issues in a more appropriate place such as a blog instead of the forums."

Thanks for your comments..

I think what Ryan, myself, and others are trying to say is that these forums are for an exchange of ideas. And to be honest, every single one of your posts is a complaint, and what is worse is that you never appreciate feedback, or at least you never show it. These forums are not an escape for you to complain. If you are going to post, then there is a good chance you will get a reply. Sarcasm does not help, nor does being overly critical. In fact with the way you are speaking to people willing to help you, you will not get their respect, and people will be less willing to help you. If you want help, you should present yourself in a manner that shows that you deserve it. People have tried to help you, I have tried to help you. It appears that none of us can give you the answer that you are looking for.

Your are right, you cannot help..

The problems can only be fixed by MSoft..

But you are welcome to your opions, as is anyone else..

But to be honest these last two as realy are a waste of both our time.

But as long as you feel better, I supose this is enough...

What would help is: Someone from MSoft taking responibility to make vs 2005 and VB.Net work.
This is not a unique enduser problem, it is  fundermental flaw that has been well documented, and know about before the relase of vs 2005 last movember...

If you dont have the problem, fine, just read and move on, but dont assume that you have the exclusive knowledge of every user..
I.e if you dont have the problem or cannot help, then dont respond, telling me you dont have a problem is actually not helpful at all...

Not sure what prompts people like yourselves to make such comments, but hey its a free world...

dude_4:

Your are right, you cannot help..

The problems can only be fixed by MSoft..

But you are welcome to your opions, as is anyone else..

But to be honest these last two as realy are a waste of both our time.

But as long as you feel better, I supose this is enough...

What would help is: Someone from MSoft taking responibility to make vs 2005 and VB.Net work.
This is not a unique enduser problem, it is  fundermental flaw that has been well documented, and know about before the relase of vs 2005 last movember...

If you dont have the problem, fine, just read and move on, but dont assume that you have the exclusive knowledge of every user..
I.e if you dont have the problem or cannot help, then dont respond, telling me you dont have a problem is actually not helpful at all...

Not sure what prompts people like yourselves to make such comments, but hey its a free world...

If we can't help, then why do you waste your time posting complaint after complaint after complaint here on the forums? We have heard your complaints and it is the same issue after another. Even if you are told there is a solution (i.e. Visual Studio 2005 SP1) you still complain. To be honest, this thread and all of your other threads are a waste of everyones time. I suggest you find another source to vent your frustrations.

I am not sure I will answer to your satisfaction, but I'll try to shed some light on few things. I am not member of C# or VB teams, I am a development manager in Visual Studio Web tools and my team owns Web editing (i.e. markup, client script, CSS, etc).

1. Features from vs 2003 C# still have not made it into VB.NET

2. Poor support for any new features; see the hopeless refractoring support in VB ( one method) as an example.

Teams makes decisions to implement this or that set of features depending on the user feedback. C# users may have requested different features than VB users. So one language editor may have certain features other editor does not. VB, for example, has My namespace which C# does not have (at least not directly). C# is case sensitive and VB is not since VB was always case insensitive. Difference in feature set simply means that teams balanced feature requests against available time and resources and implemented features in the priority order (priority actually comes from customers). It does not mean one language is more important than the other. You can talk directly to VB language architect Paul Vick here: http://www.panopticoncentral.net/ and Lead Architect John Rivard here: http://blogs.msdn.com/johnri/

3. No support for VB.NET breaking problems after almost 12 months.

VS 2005 SP1 is underway, I understand your pain, I really want SP to get out faster, but it takes quite some time to properly test all the changes and ensure they work on all configurations and platforms. We are working on improving our processes so hopefully service packs will take less time to release in the future. Here is link to the SP1 page: http://msdn.microsoft.com/vstudio/support/servicing/sp1_vs05/default.aspx

And yes, we do listen to the feedback from MSDN site. As a dev manager I am reading feedback regularly. Here is what we do with the feedback in the Web Tools: http://blogs.msdn.com/mikhailarkhipov/archive/2006/07/19/671663.aspx

If VB is crashing on you, please obtain minidump as described here: http://blogs.msdn.com/mikhailarkhipov/archive/2006/07/25/678308.aspx and send it to me at mikhaila-at-microsoft-dot-com, I will forward it to VB team.

For those interested, search google with H8013141e  (the underlying issue with vs 2005 since its release)..

PS: The bugs are still not fixed (as at SP1 beta), but are at least being worked on..