How To Open Visual Basic 6 Project In Visual Studio 2019

[Marquez Feliciano]

VisualStudio 2010 does not provide tools for upgrading applications and projects from Visual Basic 6.0. If you want to upgrade your project from Visual Basic 6.0 to Visual Basic 2010, you can use the upgrade tools provided with earlier versions of Visual Studio and then upgrade the project again in Visual Studio 2010.

integrates with the solution explorer and the code editor having support for syntax highlighting, basic outlining (allows to expand/collapse methods, properties and types) as well as navigation bar support.

Although 2008 and below versions do provide an automatic function to convert Vb6 code to the VB.net framework. But, the problem starts after the conversion - it can skip some code, add functions/variables on its own, or modify the functional behavior on its own, and with that the VB.proj will be created with errors and you will not be able to open it anywhere as a solution file. The same with any 3rd party tools.

Make sure you are clicking on the project file itself... Right click on the file and select "Open With" and select your visual studio program. It may need to be converted and if so, it will prompt you to convert the project.

I have first to apologize for my poor level in english, I will try to do my best to be understood. Few day ago, I installed the Intel Fortran Compiler (ifort) on Windows 10, by installing the intel oneAPI Base Toolkit and the oneAPI HPC toolkit. The aim was to compare the compilation between gfortran from GNU on linux and ifort on a windows computer.

When I installed the toolkits from intel on windows 10, I wanted to be sure that the additionnal compilers where included in Visual studio 2019. In fact, it was the case, because I have now the possibility to create fortran projects, and I secceeded to debug and execute a simple fortran code on 1 file (.f).

My lack of knowleadges on how to use Visual Code will now appears. In fact, I don't know how to set up tasks to debug and compile my fortran files. So, by using only the command lines all works, here are the command I used :

Now, on Visual Sudio 2019, I don't know first if a have to create a fortran project, then I copy my fortran files into it. Also how do we create I simple task and a makefile to debug and run those files.

When you are using Visual Studio, you must create a project, which then resides in a "solution". Normally, when you create a new project, the solution is created automatically. A solution can hold more than one project and is something that builds an end result (executable, for example).

Since you have existing files, select Empty Project and click Next. The next screen will ask you to name the project and say where you want the new project/solution folder created. Click Create. On the new screen that appears, you'll see something like this on the right, reflecting your new project.

Now click Project > Add Existing Item... and select all your source files. Alternatively, you can use Project > Add Existing Items from Folder, or you can just "drag and drop" files onto "Source Files".

I added my subroutines to the Source file tab, and have the program file in the main VS screen. When I build the solution there are no errors found but an exe file is apparently not produced since starting the debug process I get a message that says '*.exe file not found'.

I am curious what it is you are trying to compare - runtimes? Numerical answers? In both cases I expect differences don't you? You know you will probably get different answers, yes? You are not expecting the same answer out to 12 digits are you?

I just want to make sure you're not wasting your time. 2 different OSes, 2 different compilers == different numerical results. Not to mention runtimes. Since you are a Physicist, it's like saying " I want to throw a baseball on earth and on Mars and to compare the two." If you expect differences, great. If you expect roughly the same behavior then you're starting with a false assumption.

I understand your question, I went too fast to explain what I'm trying to compare and why. Actually, I use 2 different OS just because gcc compilers and so gfortran, is simpler to be installed and used on Linux. And, by reading some forums, I noticed that intel toolkits where also incorporated very well to VS 2019 IDE. So ifort was used on windows.

The issue was that I taked this code wrote by my supervisor that makes big calculation in nuclear physics (the program find quadrupole momentum and binding energy of nucleus in isotopic chains). I should specify that the files were always compiled by my supervisor by using ifort from intel and on linux (ubuntu).

When I tested thoses files, I used gfortran (on linux) because I never heard about ifort or intel compilers before now. So I was surprised to see that the code was not compiled will gfortran, it signals to many errors and warnings. As you said it, I think it is due to the fact that the 2 compilers have 2 differents behaviors ; my assumption was not Ok, I thought that for a language (here fortran 95) 2 different compiler will just be different in the numerical answers or runtimes But if the compilation and the execution is a success with one compiler than it will be the same on the other ( as I said in my previous message, I didn't have lectures on theorical computing..but if you know some books to understand how it really functions, I would be interested ).

- Since I have installed HPC and bases toolkits from intel, how can I know what compiler VS uses when I run a C++ program ? (because I assume that there will be now 2 different C++ compilers on it, even if I don't know what was the default compiler when I installed VS without intel toolkits)

- Also, I have a question about debugggers. I think that the GDB debugger from GNU project is used on VS by default. But when I installed the 2 intel toolkits, is VS IDE using IDB debugger know ? Also when I compile on the command prompt, what is the command to use GDB or an other debugger for example here : ifort hfaxial7.f vector.f gmatrix.f pn.f newlan.f laso.f -o hfaxial7.exe (before the command line, I set up the intel environment)

Amar, many of your questions reveal that you are not yet capable of debugging this program. You will need to take courses, read books, talk to colleagues and learn how to debug Fortran programs of at least medium size.

You wrote in your original post, ".. how do we create I simple task and a makefile to debug and run those files. .." and other sentences that suggest you feel somewhat like a beginner and you would like to learn more about how to do code development and also debugging.

If I understood your points correctly, I suggest you look at resources online such as TutorialsPoint, here is an example link for debugging is _debugger/index.htm. There are several other resources such as this one, an internet search engine is your friend.

With above links I have provided, please note I am basing them on the following: the quantity and quality of information on how to develop and DEBUG C++ code is tremendous. If you go over even a fraction of such material and gain a bit of ease with C++ debugging, you will be able to apply CERTAIN of those concepts to Fortran as well and it will help you in your work with Fortran also.

Visual Studio (on Windows) does not use gdb for debugging - it uses its own, excellent debugger. For Intel Fortran, the Microsoft debugger is enhanced with Fortran-specific support, but it is still the Microsoft debugger. IDB, which was at one time the Intel Debugger for Linux, no longer exists.

To build an application for debugging from the command line, add the /debug option to all commands. While it is possible to invoke the debugger from the command line, it is not a command line debugger (it's the Visual Studio debugger) and it is far easier to do this from within Visual Studio with the project you built there.

The compiler defaults for a new VS project are different from those on the command line. Especially for a Debug configuration, additional compile-time and run-time checks are enabled. You encountered one of these, generated interface checking. From the command line this is /warn:interface . Another option enabled in a Debug configuration is array and string bounds checking (/check:bounds).

If you select the Intel C++ Compiler Classic (I suggest not using the DPC compiler unless you are using its features), the project will be reconfigured, and it will show you the selected compiler after the project name:

2. If this is your masters topic work then you need to fix all of the errors -- there are 20000 lines of code so someone with say 40 years of experience it will take a long weekend of nothing else -- you might just get it running - this includes getting rid of all of the commons, implicit variables and finding all of the missed named variables. The code was written in 1982 - there is a lot of potential errors that a modern compiler will pick up that the old compilers allowed. If you are doing it then set aside a month of time to learn and do it. At the end you will be a good programmer and intimately familiar with these people here. The six errors shown are just the tip of the iceberg, there are a lot there. Reading the code made me smile.

3a8082e126