Need translation from C# to VB
-
Dim byting_into_void As unsafe?
Cheers, Sebastian -- Contra vim mortem non est medicamen in hortem.
-
IIRC unsafe code and pointers (Type*) aren't available in vb.net. The languages are almost identical, but there are a handful of features in each not supported by the others. C# has unsafe (dunno why it's not in VB), VB has optional parameters (depricated and only kept for legacy VB code support, but useful for writing com wrappers in any langauge), managed C++/C++Cli allow a more direct mixing of managed and native code (useful for high performance interop situations).
-
There are no equivilents. Unsafe code blocks and pointers are not supported in any version of VB/VB.NET to date. It doesn't look like they'll show up in the next release either.
Dave Kreskowiak Microsoft MVP - Visual Basic
-
There are no equivilents. Unsafe code blocks and pointers are not supported in any version of VB/VB.NET to date. It doesn't look like they'll show up in the next release either.
Dave Kreskowiak Microsoft MVP - Visual Basic
Thank you. I've been programming with VB for a while now and am trying to decide if I need to pick-up C#. I have an application that has alot of images that need to be displayed an then manipulated quickly. I've found a ton of helpful articles on CP but there almost always in C#. I have a good C# to VB converter but it has been balking at these bits of code. Thanks again everyone.
-
Thank you. I've been programming with VB for a while now and am trying to decide if I need to pick-up C#. I have an application that has alot of images that need to be displayed an then manipulated quickly. I've found a ton of helpful articles on CP but there almost always in C#. I have a good C# to VB converter but it has been balking at these bits of code. Thanks again everyone.
AreJay wrote:
trying to decide if I need to pick-up C#.
It couldn't possibly hurt. For image manipulation, C# is just about a must, or a Managed C++. I know VB.NET and C#. My C++ is pretty rusty, but I can still read it and translate very easily. I do the bulk of my work in VB.NET, but use C# for the stuff that VB.NET doesn't support, like pointers and unsafe blocks for image manipulation. (Thank you Christian!)
Dave Kreskowiak Microsoft MVP - Visual Basic