Code Converter. Free Online Code Translation for .NET C# and VB and TypeScript, Convert VB to C# and C# to VB. Convert C# to TypeScript. Convert VB to TypeScript. Convert Java to C#. Convert Java to TypeScript. Convert Java to VB
Carlos Aguilar Mares works at Microsoft. If you find any issues with the
product, please contact Carlos (the contact info can be found at the
top-right corner of the blog). I believe that Carlos will be very happy to
hear from your feedbacks.
Regards,
Jialiang Ge (jialge@online. microsoft.com, remove 'online.')
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at: msdnmg@microsof t.com.
This posting is provided "AS IS" with no warranties, and confers no rights.
Thanks to someone's reminding, I should have pointed out in the last reply
that Microsoft does not have the support responsibility for the language
convertor tool:
Code Converter. Free Online Code Translation for .NET C# and VB and TypeScript, Convert VB to C# and C# to VB. Convert C# to TypeScript. Convert VB to TypeScript. Convert Java to C#. Convert Java to TypeScript. Convert Java to VB
Jialiang Ge
Microsoft Online Community Support
"Jialiang Ge [MSFT]" <jialge@online. microsoft.comwr ote in message
news:Odd1J$gHJH A.3932@TK2MSFTN GP03.phx.gbl...
Code Converter. Free Online Code Translation for .NET C# and VB and TypeScript, Convert VB to C# and C# to VB. Convert C# to TypeScript. Convert VB to TypeScript. Convert Java to C#. Convert Java to TypeScript. Convert Java to VB
>
>
>
Carlos Aguilar Mares works at Microsoft. If you find any issues with the
product, please contact Carlos (the contact info can be found at the
top-right corner of the blog). I believe that Carlos will be very happy to
hear from your feedbacks.
>
>
>
Regards,
>
Jialiang Ge (jialge@online. microsoft.com, remove 'online.')
>
Microsoft Online Community Support
>
>
>
=============== =============== =============== ====
>
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at: msdnmg@microsof t.com.
>
>
>
This posting is provided "AS IS" with no warranties, and confers no
rights.
>
=============== =============== =============== ====
>
"a" <a@a.comwrote in message
news:eId3YNgHJH A.3932@TK2MSFTN GP03.phx.gbl...
>Does anyone know a C# -VB conversion tool? There are a lot of
>converters on the web, but most of them have bugs.
"Parsa Amini" <parsa.amini@ho tmail.comwrote in message
news:e5QT72QOJH A.3968@TK2MSFTN GP02.phx.gbl...
>a wrote:
>Does anyone know a C# -VB conversion tool? There are a lot of
>converters on the web, but most of them have bugs.
You can use SharpDevelop. It has a good VB, C# converter
I'd think twice about doing that as VB is definately a poorer choice.
There's various problems with it but just the intellisense being not as good
is enough.
I think that you should eat less, by eating so much you have deffinitly a
change on a hart attack.
Cor
"Michael C" <mike@nospam.co mwrote in message
news:%23gFLoiaO JHA.3472@TK2MSF TNGP04.phx.gbl. ..
"Parsa Amini" <parsa.amini@ho tmail.comwrote in message
news:e5QT72QOJH A.3968@TK2MSFTN GP02.phx.gbl...
>>a wrote:
>>Does anyone know a C# -VB conversion tool? There are a lot of
>>converters on the web, but most of them have bugs.
>You can use SharpDevelop. It has a good VB, C# converter
>
I'd think twice about doing that as VB is definately a poorer choice.
There's various problems with it but just the intellisense being not as
good is enough.
>
"Cor Ligthert[MVP]" <Notmyfirstname @planet.nlwrote in message
news:uC5Pu4eOJH A.2292@TK2MSFTN GP04.phx.gbl...
Michael,
>
I think that you should eat less, by eating so much you have deffinitly a
change on a hart attack.
I'm sure I would but I think the general concensus in the dot net community
is that C# is the preferred choice. VB does have its advantages (I like the
handles keyword and creating your own events is much easier) but it missed
out on some really big show stoppers such as lack of pointers. Most of the
advantages it has are fairly minor really and just save a bit of typing but
are offset anyway by the need to type dim, directcast, next, end if,
function, sub, property, readonly etc repeatedly.
"Michael C" <mike@nospam.co mwrote in message
news:uE1WBH7OJH A.4332@TK2MSFTN GP06.phx.gbl...
As for the intellisense I'm very suprised you would say C# is behind VB. I
find the VB intellisense annoying and feel like they got it just a little
bit wrong. The reasons are fairly solid reasons and more than just a
matter of opinion.
1) Whenever you select a control name, eg txtWhatever, the intellisense
always goes to the first event handler, eg txtWhatever_Key Down. In all my
years of programming I've never called an event so always have to scroll
up one.
2) Instead of moving to the required item in the list, the list gets
smaller as I type. If I mistype a single characters then the list usually
disappears. I then have to backspace until the list reappears and select
the item I want. In comparison the list in C# does not get smaller and
does not disappear so usually when I mistype I can see the item I want in
the list and select it.
3) Because of 2 when you push backspace intellisense appears.
4) Intellisense seems to popup more often when it is not wanted and I find
myself pushing esc all day. In comparison intellisense in c# seems to
appear more in line with when I want it. I'd have to be in front of my
work PC to fully work out what's going on here.
I forgot number 5 which is when I type "public readonly property" the
intellisense shows readonly and property but for some reason they are not
selected and I have to down arrow 1 to select each of these. This is
annoying consider both keywords are not required in C# at all.
Although that you took the subject Event Handler, you did not write how an
eventhandler has to be set in C# and in VB.
Maybe you can tell us in which way C# outclasses VB in that so we can laugh
even more here.
Cor
"Michael C" <mike@nospam.co mwrote in message
news:u3MjqN7OJH A.4576@TK2MSFTN GP06.phx.gbl...
"Michael C" <mike@nospam.co mwrote in message
news:uE1WBH7OJH A.4332@TK2MSFTN GP06.phx.gbl...
>As for the intellisense I'm very suprised you would say C# is behind VB.
>I find the VB intellisense annoying and feel like they got it just a
>little bit wrong. The reasons are fairly solid reasons and more than just
>a matter of opinion.
>1) Whenever you select a control name, eg txtWhatever, the intellisense
>always goes to the first event handler, eg txtWhatever_Key Down. In all my
>years of programming I've never called an event so always have to scroll
>up one.
>2) Instead of moving to the required item in the list, the list gets
>smaller as I type. If I mistype a single characters then the list usually
>disappears. I then have to backspace until the list reappears and select
>the item I want. In comparison the list in C# does not get smaller and
>does not disappear so usually when I mistype I can see the item I want in
>the list and select it.
>3) Because of 2 when you push backspace intellisense appears.
>4) Intellisense seems to popup more often when it is not wanted and I
>find myself pushing esc all day. In comparison intellisense in c# seems
>to appear more in line with when I want it. I'd have to be in front of my
>work PC to fully work out what's going on here.
>
I forgot number 5 which is when I type "public readonly property" the
intellisense shows readonly and property but for some reason they are not
selected and I have to down arrow 1 to select each of these. This is
annoying consider both keywords are not required in C# at all.
>
Michael
>
"Cor Ligthert[MVP]" <Notmyfirstname @planet.nlwrote in message
news:O7SMPxAPJH A.1268@TK2MSFTN GP06.phx.gbl...
Michel,
>
Although that you took the subject Event Handler, you did not write how an
eventhandler has to be set in C# and in VB.
>
Maybe you can tell us in which way C# outclasses VB in that so we can
laugh even more here.
What a pity, your reply above in the other thread was mature and
intelligent, then you go and ruin it here with this childish rant. You
didn't answer a single one of my points and ran off on a tangent.
Comment