Will llblgen be developed for vb.net in the future as well? I have a customer that's a little bit concerned about using the product. It would be interesting to find out how many % of all .net applications are developed in c# and in vb.net. Most of my projects are in c# but early users and projects of .net seems to have chosen vb.net.

I think it's great that you provide code for both c# and vb.net. I can't understand why the book publishers must release seperate ones all the time. Well money, I guess. :-)

Will llblgen be developed for vb.net in the future as well?

I don't understand the question?

taking into consideration the following line:

I think it's great that you provide code for both c# and vb.net

(edit) please note that LLBLGen Pro generates VB.NET code as well as C# code. Which ever you choose.

Rauken wrote:

Will llblgen be developed for vb.net in the future as well?

Of course. VB.NET and C# are the target languages for LLBLGen Pro, always have been and always will be.

I have a customer that's a little bit concerned about using the product. It would be interesting to find out how many % of all .net applications are developed in c# and in vb.net. Most of my projects are in c# but early users and projects of .net seems to have chosen vb.net.

I can't give you any numbers on that, other than that we have a lot of VB.NET developers among our customers, as well as C# developers. We use C# ourselves, but that doesn't mean VB.NET is a second class citizen, in fact we try to provide all functionality on VB.NET even if it requires us to jump through a few hoops (like on .NET 1.x, making a datatable serializable for remoting required us to write a C# class so the VB.NET generated code could derive from that to be serializable... )

I think it's great that you provide code for both c# and vb.net. I can't understand why the book publishers must release seperate ones all the time. Well money, I guess. :-)

Well, providing all examples in both languages can be tedious to the reader sometimes. All our code is written in C# first and then we port over the templates to VB.NET. Additions to templates for new features for example are made together to C# and vb.net templates. It's more work, but as our customers want to use VB.NET, we'll give them that.

Thank you for your answer. That's what I thought, that's quite a lot of work to support both languages. Many or mappers only support C#. My concern was that you plan to just support C# in the future. No I'm not going to debate C# vs VB.NET, I use them both and it's up to my clients to choose.

Rauken wrote:

Thank you for your answer. That's what I thought, that's quite a lot of work to support both languages.

It is, but fortunately, we can put a lot of code in the runtime libraries which are usable from both languages .

Many or mappers only support C#. My concern was that you plan to just support C# in the future. No I'm not going to debate C# vs VB.NET, I use them both and it's up to my clients to choose.

That's also our philosophy: our customers should have the choice, it's fine by us which language you take. Of course, we have our preferences, but that doesn't mean these have to be the same for our customers nor that our customers have to live with what our preferences are.