Delphi to Visual basic conversion utility - vb.net

Is there any code conversion tool for converting Delphi to Visual Basic? Please advice.
Thank you very much.

Not that I'm ware of. There are tools to convert Delphi to C# or Visual Basic to Delphi. But not the other way around. It's probably because Delphi has a lot more features then Visual Basic to make it a difficult transition.
You can do it by hand. But it'll take a while.

If you consider moving to VB.NET (and .NET platform in general butnot VB6), these questions might give you some ideas/options:
What tools exist to convert a Delphi 7 application to C# and the .Net framework?
Is there an easy way, to Port a Win32 App in Delphi 2009 to .NET ?
Migrating a Delphi 7 application to .NET
Delphi to .NET + C#
Delphi’s interoperability with .NET
You can try migrating the application from Delphi (Win32) to Delphi.NET or Delphi Prism
Once this step is complete you can consider migrating to VB.NET or C#
But it really depends on the technologies used by your original application (e.g. BDE, 3rd party components), level of interaction with WinApi and so on.

Delux Software has one.

Related

VB .NET vs. VB 2010

I just want to know if VB.NET and VB 2010 are the same.
I'm just wondering.
VB 2010 is the latest version of VB.Net. Microsoft dropped the ".Net" part of VB with the VB 2005 release.
Wikipedia has all you need to know about VB.net: Wikipedia Page
VB.NET is any version of Visal Basic since version 7, where the language moved to the .NET platform and became object oriented.
2010 isn't a version of the VB language, it's sometimes used to describe the version that comes with Visual Studio 2010, which is VB version 10.
As specified on the wiki page for VB.NET VB 2010, or VB 10.0 is a new version of the language commonly refered to as VB.NET.
as the time changed visual basic became more advanced. Before it used a p code compiler. but all the versions after vb 6.0 IDE it stopped using msvb60.dll and shifted to .NET framework which is now called VB.NET. But Microsoft removed the .NET after VB 2005 final release. Also it used a VBC.exe which is the new Visual Basic compiler. There was a lot of criticiscm after this because it was not compatible with Win 98 and previous versions.
Visual Basic .NET (VB.NET) implemented on the .NET Framework. Microsoft launched VB.NET in 2002 as the successor to its original Visual Basic language. Although ".NET" portion dropped in 2005,"Visual Basic .NET" to refer to all Visual Basic languages releases since 2002.
There is Visual Basic and Visual Basic .NET. Visual Basic .NET runs on the .NET framework and the former does not.
Basically yes, Vb 10 is just the newer version
Yes they are the same, but VB.Net runs with .NET framework.
Yes they are the same. Bassicaly VB 2010 is using .NET framework
Vb.net is the same as VB 2017. In your case it's 2010. Just more features
VB 2010 , because nobody is needed to know .net when they know vb
but in vb.net you also have to learn .net,
This version is also the latest
you can also have vb2010 express for free here
http://www.microsoft.com/visualstudio/eng/downloads#d-2010-express
(OR)
get the paid version like pro edition here (trial only)
http://www.microsoft.com/en-us/download/details.aspx?id=2890
VB.NET is the language that you can use on the .NET framework. Before .NET framework evolved, Microsoft had a separate product called Visual Basic, and in 2002 when Microsoft came with .NET framework then they discontinued Visual Basic as independent product, and combined it in the .NET framework.
Basically .NET framework supports 50+ languages (Visual Basic is one of them, and C# is another commonly known language) which you can use to develop variety of applications. Over the years, Microsoft improved .NET framework, so thus the VB language to make it more smart.
The VB 2010 that you are asking is the Visual Basic language that came with the Visual Studio 2010.
VB 2010 is a part of the VB .NET family. VB.NET uses the .NET language runtime, while VB6 and previous VB does not. VB .NET is object-oriented, and the classic VB is event-driven.

Does Mono support visual basic (not .NET)?

Someone asked me today if it was possible to port a visual basic application to Linux or similar platform, I assumed it was .NET so I suggested to use Mono, but noticed that on their vb support page they only talk about vb 8 (.NET)
Does mono support non-.NET vb? In fact I'm not sure what he is using, I think vb6, I'm not sure of the versioning at all though.
No, VB6 is an entirely different beast from VB.NET. Mono is basically there to run (via JITting, interpreting or AOT-compiling) IL - the Intermediate Language that VB.NET and C# compile down to. (Of course it also provides the libraries and compilers.)
Running VB6 requires an entirely different execution environment, basically.
No, but you could take a look at gambas
Gambas is a free development
environment based on a Basic
interpreter with object extensions, a
bit like Visual Basic™

Active X Development: VC++ or VB or Other technologies

We are in the process of creating active-x controls used within our application.
Since Microsoft stopped supporting classic Visual Basic, is it wise to use Visual Basic to develop the Active X control or the latest VC++/ATL/MFC libraries provide more feature where we can create controls faster by leaving Visual Basic flexibility?
We will not be able to use .NET/VB.NET/C# since the application is supposed to work inside containers and containers may not support latest .NET runtime.
Any other language is best fit for Active X control development other than VB and VC++?
I, personally, would recommend using Delphi for this. It is still actively developed, and has the control you get with C++, but a rapid development environment more like VB.NET.
#nobugz: If you are really interested what is ActiveX in Delphi, look at docwiki. Normally it is 100% source code (yours + VCL, VCL is also available as sources) with autogenerated COM wrappers. So all potential security problems are also in source code. If you find a security problem in VCL, please send a bug report to Quality Central.
Here is a good example on how to create ActiveX Controls with C# .NET
http://www.codeproject.com/KB/cs/CreateActiveXDotNet.aspx
By all means VB6 is the best language. After reading your question I feel that you are a VB6 developer. If you know VB6 and use it then why hesitate using it for producing ActiveX controls.
I program in Delphi as well as VB6 along with VB.NET and C# but creating ActiveX controls is the easiest in VB6 compares to all other development tools.
If you are hell bent on not using VB and if you are looking for an alternative then try out PowerBasic (commercial - very costly) or PureBasic (commercial but affordable) Get it from here or better still MinGW (a GNU C++ compiler).
I have to say that VB6 with a good book like Developing COM/ActiveX Components with VB6: A Guide to the Perplexed you will be up and running faster.

Resources needed to start windows programming with C++CLI

I'm already new in C++CLI , although I have been working on VB and C++ for a long time , but I need to start a projects on CLI using it's visual screens and easy codes (just in windows) , But I can't find any good Resource or book to start windows programming (I mean codes that you can give it to buttons or texts without using c++ classes) ,
Can I find any of them ?
thank you
I can suggest you 3 books ( I used them ):
Foundations of C++/CLI The Visual C++ Language for.NET 3.5
Pro Visual C++/CLI and the .NET 3.5 Platform
C++/CLI in Action
They are in order of difficulty.
The first and the 2nd are introductory and advance respectively.
The 3rd is great for advanced topics, like interop, mixed-mode coding etc..
Not sure what you have done in your work with C++ without classes, it is C with classes :). If you want to write Windows Program in C, Programming Windows, 5th Edition written by Charles Petzold could be a good start. Then you can decide which managed GUI to learn. Winform is mature with no future planned beyond .Net 4.0, while WPF is growing and is the main focus of Microsoft.

Can Visual Basic run as a Windows Service?

I am less than a week into my Visual Basic education. I have downloaded Visual Studio 2008 and am teaching myself Visual Basic 2008 in hopes of landing a particular contract position.
In the meantime, a friend of mine told me that it is not recommended to write a Windows Service with Visual Basic. Is that true? Could he be referring to some much older version than 2008? Does the .NET version come into play?
What is at stake is that the company that my friend works for is going to completely re-write a component of their flagship product at great cost and expense and simply abandon their existing VB code. If the only hang-up is getting it to run as a service then they could save a lot of money if Visual Basic could, in fact, run reliably as a service.
You can write .NET services in any CLR language, including VB.NET --- your friend was thinking of VB6 and earlier.
(I do recall some fairly crazy kludges that allowed services to be written in VB6, but for all practical purposes, services written in VB6 weren't really a viable solution...)
There is no reason that Visual Basic .Net can't write a windows service. You can select a project which will create a windows service under the "Windows" projects in the Visual Basic section.
Writing a Windows Service in VB.NET (using any version of Visual Studio >= 2003) is just as effective as writing a Windows service in any other language.
Your friend may have been thinking of Visual Basic 6...or he's partial to another .NET language.
In either case...you should be fine to keep going on your path the way you are.
Your friend may be referring to Visual Basic, not VB.NET.
While VB.NET has syntax that is similar to Visual Basic and some convenience functions are still present, they are two entirely different languages and environments.
Your friend is correct in stating that Visual Basic (meaning 6 and earlier, not VB.NET) is a poor choice of a language for a service (or any new application), but VB.NET is every bit as legitimate as C# or any other CLR language.
It may be useful to refer to what you're learning as "VB.NET" or "Visual Basic .NET", rather than just "Visual Basic".
.NET certainly allows you to use Visual Basic to write a Windows Service. I believe there is even a default project template to do so. Here is an tutorial as such: http://www.vbdotnetheaven.com/UploadFile/mahesh/Winservvb11172005233242PM/Winservvb.aspx
All .NET code is converted to an intermediary language that is executed, thus all .NET languages can be used to write a windows service.