sorry for asking this, but I'm really newbie to this. I just receive a code from my boss and it is a code with VB 6.0 version, he then ask me to convert into the latest version of VB. Now I get confused because when I google I found out that the latest version is VB 6.0 . So I get confused now.
Can anyone correct me if I'm wrong and if theres any latest version,how can i convert it? Is there any converter tools like developerfussion? TQ
I don't recommend a direct translation. VB 6.0 was the last release for the classic visual basic. After that it became in VB.net, which is not the same, is a 100% object oriented programming language but, you could be able to convert it by hand. Since VB.net is OOP and VB 6 is not you can transcript from VB 6.0 to VB.net using the procedural way, loosing all of the OOP advantages. The other thing you can do is re-write the program from scratch to VB.net, which is going to take a while but it will worth it. The latest version for Visual Studio is 2013.
Your boss may sugest a convertion from visual basic 6 to vb.net. You have several tools to do that. You can use the free visual studio 2008 Express (open and convert the code), or you can try the mobilize vb upgrade tool (free until 10.000 lines of code).
https://www.mobilize.net/solution/msdn
This limit of loc is quite small, exclude the comments but includes all the code and the design code.
You have lots of help here using the
https://stackoverflow.com/questions/tagged/vb6-migration
Related
I converted VB6 project to VB.NET in Visual Studio 2008 but not able to open it in VS2010. Getting error
"Editor doesn't support the extension of file .VB"
Any pointers in this will be helpful.
As far as I know, even if you do a conversion, it will never be compatible. 2008 could open it with compatibility mode, but 2010 can't. You have to recode everything.
As far as i know, they have discontinued the support of conversion to VS2010. The only last chance you have is to convert to project VS2008. I have had the same problem with a huge project. And I was not able to convert it completely.
Even if you are trying to convert the project with VS2008 and if you used 3rd party components in it, after the conversion the project will not be able to run after some tweaking.
If you have a small project with pure VB6 that does not involve 3rd party components, then you can give it a try. Chances are only 50/50 for you.
Conversion in VS2008
Simple answer : Don't waste your time for converting it and then fixing the problem in it, just re-write the whole thing in .NET which is very ideal
Conversion of VB6 project to directly VS 2012 is not possible, Upgrade the project first by VS 2005 and then upgrade the vs2005 project to vs2012. It will work.
Is one able to compile VB 6 code in Visual Studio.NET ? In other words, is it backwards compatible with older VB code?
Since I know there is a difference between managed code (.NET) and unmanaged code, I am wondering if Visual Studio.NET is able to compile unmanaged code as well?
Kind regards,
Kris
While you cannot compile vb6 in the .net Visual Studios, you may use interop libraries to allow vb.6 to utilize managed code
http://msdn.microsoft.com/en-us/library/kew41ycz%28VS.71%29.aspx
No, you can't compile VB6 code in any VS.NET version.
You can open a VB6 .vbp project file in Visual Studio. This automatically invokes the project converter, it will try to translate your VB6 code into VB.NET. The translator does a fairly decent job of it but the VB.NET language has changed pretty drastically. It depends on how 'clean' your VB6 code was.
After the conversion is completed, you'll have to walk through the list of warnings and errors you'll get. Getting none at all is rare. There might be hundreds or thousands. If you're in that boat, it starts making sense to rewrite the code.
Anyhoo, just try and see what hits the fan. You'll have a good idea what you're in for in about ten minutes. Don't forget to copy the project before you start the conversion.
No it is not compatible. I think there is an upgrade wizard, but you will end up fixing some stuff manually.
In Ironpython site exists references to a language called VBx using DLR. But i can't find any reference to this in google. Where is it?
Edit: Is a Implement of Visual Basic 6.0 in DLR? if yes is so cool. Is more expected for people using VB6 yet and can't migrate because big frameworks.
From this mailing list post:
VBx was an implementation of Visual Basic on the DLR. It was first meant
to be in Silverlight, but the VB team decided they'd rather put VB.NET in
Silverlight rather than build a new implementation up from scratch. So, VBx
is on hold.
Apparently it's an implementation of VB in the DLR:
http://www.mail-archive.com/users#lists.ironpython.com/msg05933.html
Straight from the mouth of Paul Vick (long time VB architect)
What is VBx?
VBx was one of the four language implementations that were originally driving the design of the DLR, the other three being IronPython (from which the DLR was extracted in the first place), IronRuby and Managed JavaScript.
VBx was intended to be a dynamic version of Visual Basic.NET or a .NET version of Visual Basic 6, whichever way you want to look at it. It was primarily intended as a testbed for the flexibility of the DLR, secondarily as a testbed for a more dynamic version of VB.NET and tertiarily (is that a word?) as a scripting language for Silverlight. It has fulfilled its primary goal and the designers of VB.NET decided that they want to pursue goals two and three within the existing VB.NET language, rather than producing yet another slightly different incompatible version of VB. (You already have VB.NET, VB, VBA and VBScript.)
Managed JavaScript was also abandoned, the team was folded into the IE team and is responsible for the ECMAScript 5 engine in IE 9.
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.
I would like to hear of the experiences of classic vb developers who migrated their applications to delphi rather than vb.net. How has it worked out? Are you glad or sorry that you didn't move to vb.net?
I am not really a vb developer but rather a Delphi developer who was forced to maintain some vb apps for a while. I tried to migrate one vb app to vb.net and after that experience I never tried it again. I successfully migrated several vb apps to Delphi. It wasn't easy and it became a pain in the lower back to find native Delphi replacements for some of the OCXes that had been used (I will never again rely on a third party library for which I do not have the source code.), but it worked out OK.
But as said above: I am an experienced Delphi developer, so I didn't have to learn Delphi at the same time as migrating a vb app. That certainly made it much easier.
I just spotted this on DelphiFeeds:
Delphi for Visual Basic developers
Help to migrate VB applications (knowledge and skills) to Delphi
I had a good friend who moved from Classic VB to Delphi a while ago (back before .NET). He was really happy with the move.
The company he worked for made applications in VB, and they put together a special team (2 developers) to create Active X controls in Delphi for the rest of the company to use. Additionally, when there was something that they couldn't do in VB then the Delphi team would do it. That was when he was introduced to Delphi.
He said it didn't take long before the Delphi team could prototype applications in Delphi faster then the rest of the development group (he never said how large, but way more then two) could. The company never made the switch to Delphi from VB because someone was under the impression the VB was a better solution despite the evidence that Delphi was more powerful and faster.
A few years are I was working with another student on our placement year. We worked for a very large manufacturing company. One of his projects was to create a classic VB app to interface with multiple cameras on a production line and analyse the data in real time. In classic VB this was a shambles - it took on average 1.5 minutes to process a single frame from a single camera (7 cameras at 24 fps) there was no that he could optimise it.
He eventually took the plunge in to Delphi and re-written that app and works fantastically. I've recently been in contact with a few friends who still work there and his app is been running smoothly for 3 years now.
I've worked in both VB and Delphi, and Delphi is (IMO) much less frustrating/limiting. You should be able to use ActiveX / OCX controls as needed (though I agree w/other comments re: avoiding there where you can, and being sure ot have full source code). Apps we've migrated from VB to Delphi (two) have gone well.
I did try in two instance to migrate from VB to Delphi but unfortunately I had to abort midway in one app as it used a lot of third party ActiveX (most from ComponentOne and a few from CodeJoke). We had to abort midway as we could not find any VCL components having equivalent functionality to the ActiveX used in the project.
It was a nightmare for us. Thank god we aborted midway and switched to C#. It was unbelievable that we could get all the features in .NET component to the ditto!
The app we managed to convert, went well off but we had to get rid of a few features that we had implemented in the original software as they required more work in Delphi.