Hello,

Its very nice of us to have VB.NET code by a helping forum member.

But simultaneously it becomes difficult for a beginner to peep in to codes (VB) everytime reading the book in C#.

Since the codes are around for quite a while, can we expect an e- book version with VB.NET codes.

It will be a great loss for VB community to take the maximum advantage of this book.

Reading the book in C# and having a look again and again in VB.NET codes in VWD is not that easy.

Wrox should really think now. Its already late on their part, to help VB community.( majority developers and students are still VB.net )

I personally feel so.

Thanks

SoftMind.

I am with you. The need is out there

I agree 100% with you!!

Hello,

I need many more supporters here to prove that Vb.net is a very huge community.Just 2 supporters will not help here.

The C# version for this book was out in may 2006. After 8 months, can we ask for Vb.net version atleast in e-book form...?

Wrox already had the same book in VB.net for 1.1

How about this time, when asp.net 2.0 is great and more powerful than 1.1 in many many ways.
This book can create a milestone in Vb.net edition.

Hello Wrox, think once again in our favour.

I agreed.

Everyone should know by know that I support the VB community and this book in general, so my remarks about this are going to be somewhat of a surprise.

I've come to terms with the fact that the book was written in C# and I think if everyone who is complaining took a few days to actually learn the language you'd find it easy to understand. Sure, there are a few issues (like NULL really doesn't have a parallel in VB, the closest we come is Nothing) but the resemblance of C# to VB is remarkably striking. With that in mind I think the choice of supporting only one language, given the production costs, is a wise one.

One of the points that I think that is really being missed here is that what is being showcased is not the language, but ASP.NET 2.0. Sure VB has been improved and can take its place among the best OOP languages, finally, but the real glue that holds everything together is ASP.NET and the .Net Framework.

That's my .02 worth.

I agree with MythicalMe.
When reading a book as a .Net developer, it shouldn't make a difference whether it's written in C# or VB.Net. It's just a different syntax.
I read a lot of VB.net books while I only develop in C#.
The book is about architecture and concepts and not about vb.net or c# and as MythicalMe states, it's ASP.Net that is important here.

my 2 eurocents :)

I dont think, the difference is just syntax.

If that was the only reason, one could have easily translated the C# codes into Vb.net and have actually solved the problem.

If that was the reason, there would have been no book from wrox for 1.1 in Vb

I think its not that easy to translate the C# codes. The syntax is odd for any vb.net developer to understand.

If i am used to...
Sub
'and
End Sub

I will never undertand that when the sub starts with
{
//and ends with
}

This is just one example. C# is different in plenty of ways.

I strongly oppose that C# learning curve can help Vb community.

VB.NET book is much welcomed here.

If there's a C# code snippet you aren't able to convert to VB easily, you could post it here.

VB is the larger language of the 2, and it's easier to go from the smaller to the larger, if that's any consolation.

Eric

I'm with you softbank!
If both language are equal, why you dont selected VB.NET?
Cheers!!