I have to continue to support VB6 applications. I've got both VB6 (Visual Studio 6) installed and Visual Studio 2008 as well. Can I read and write to VB6 projects while in Visual Studio 2008? Will it damage or destroy my VB6 application? It would be very cool if I could free up a lot of space and get rid of Visual Studio 6.
Visual Studio 2008 can't compile VB6 applications. You could use it as a text editor only (though it will offer you the VB.NET IntelliSense, not VB6). However, you need Visual Studio 6 to be able to build your application.
The VB6 IDE will coexist along side the Visual Studio 2008 quite happily.
The VB.NET LANGUAGE is related but not compatible with VB6. Conversion between VB6 and VB.NET is problematic. There are a lot of subtle and gross differences between the two making them effectively separate languages.
You need to keep both separate IDES and libraries installed on your computer in order to deal with both languages.
If you need for the two interoperate you can do this by creating COM libraries. Both languages can consume COM Libraries created in the other.
If you remove VB6 you won't be able to build your VB6 apps? VS2002/3/5/8 doesn't know how to compile VB6 projects.
Related
I ran Dependency Walker on an assembly (.exe) after compiling in Debug (Any CPU) and it seems like there are older core and kernel issues. The entire code is VB.NET 2010, so I am wondering why VS2017 Pro didn't clean those out?
Something interesting was that the Conversion to a new VS version did not occur, for which errors are shown -- it just showed the forms, modules, etc. as if there were no errors.
Should I try a Reload or something?
The errors were caused by having old references or assembly libraries which called DLLs (like VBIDE.dll and MSCORE.DLL) in the applications folder. There were very old references, some of which were to VB6.
Recall, remember that Visual Studio has always been dropping certain Windows forms controls over VB 2005, VB 2008, VB2010, etc. so you need to make sure those older controls are not in forms when you upgrade to e.g. VS 2017.
I have an existing Visual Studio 2005 project for which I get a conversion wizard prompt when opening in the freshly installed Visual Studio 2010. What are the implications of carrying out this conversion? Converting to anything more recent than 2010 is not an option.
The conversion process is usually pretty seamless, it will take your 2005 project and upgrade it to a 2010 project.
It should not be an issue unless you have projects with 3rd party components which, for whatever reason, do not like the newer version of Visual Studio. The only one I've ever had a problem with is Crystal Reports and that was going from a .NET 1.1 project in VS2003 to .NET 4.0 in VS2010. (But hey, one does not simply do things with Crystal Reports)
The conversion wizard will also back up your old project if you tell it to, although I would hope it's in source control of some kind anyway.
Of course, people who only have VS2005 on their machine will no longer be able to open your upgraded 2010 project, you are effectively committing to VS2010. It can always later be upgraded to VS201x at a later date if this becomes an option.
Currently our BSP is built using Visual Studio 2005. I would like to update this to use VS 2010 at the very least, preferably 2012. I have not been able to find anything that will allow me to do this. I tried to upgrade the project to VS 2008, but it failed to load the project. I was wondering if anybody had some ideas or could at least point me in the right direction.
Visual Studio 2008 does support the Platformbuilder Plugin and creating Applications for Win CE, however the import wizard is not perfect, you may need to change some settings by hand.
Visual Studio 2010 does not support creating BSPs or applications for Win CE.
Visual Studio 2012 will support creating of BSPs and applications for Windows Embedded Compact 2013.
It also includes a new faster version of the .Net Compact Framework.
http://blogs.msdn.com/b/windows-embedded/archive/2012/11/14/windows-embedded-compact-v-next-uncovered.aspx
http://channel9.msdn.com/Events/Visual-Studio/Visual-Studio-2012-Virtual-Launch/Visual-Studio-2012-support-for-Windows-Embedded-Compact
I want to open a program (written in Visual basic 6) to be open in Visual Studio.net. Please guide, how could I do that?
While trying to open VB6 (.vbp file) program directly from the OPEN project option in visual studion.net, I was getting this error,
"Visual Basic 6 (.vbp) files cannot be opened in Visual Studio"
I am trying to open in VS 2010.
Visual Studio 2010 does not support VB6 projects. See the link here
From the msdn documentation:
Visual Studio 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.
Visual Basic Tools for Visual Studio
There's a plugin called Visual Basic Tools for Visual Studio that provides the following features:
load classic VB workspace- and project-files and offers quick access to the extension´s options
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.
Classes, Types, Modules, Forms and Controls can be inspected using the Object Browser and Class View.
From the reading, it's unclear if you can actually build the project, though it does say:
The import tool creates a new solution and MSBuild compatible projects.
Links to the plugin by VS Version
2012-2013
2015
2017
RAD Basic
There is also an independent IDE called RAD Basic that claims the following features:
New and modern IDE (Integrated Development Environment) with form designer supporting drag and drop, code completion, refactoring tools, etc.
RAD Basic Compiler: Compiler 100% compatible with your VB6 project (vbp, frm, bas and cls files). Generate native executables (exe and ocx) in both 32-bit and 64-bit.
RAD Basic Forms: Reimplementation of common VB6 controls and components supporting 32-bit and 64-bit.
etc.
Speaking from my experience, it's not easy to open a Visual Basic 6.0 project in any versions of Visual Studio above 2008.
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.
If you want to open the VB6 code try Visual Basic 6.0 Portable edition.
But headache will still follow you there, please refer this link
Installation of VB6 on Windows 7 / 8 / 10
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.
Thanks!
Download Visual Basic Tools for Visual Studio,allows to work with classic VB workspaces and projects
I want to be able to develop code using Visual Studio 2010. I just got VS2010 and I'm not able to get the languages I want on it. The main reason that I'm asking this is that I'm trying to migrate to ONE IDE that does it all for me. Thus far eclipse has been doing a good job, but I've been informed that VS2010 is better and I'm trying to get into the groove of that standard
So my question is two-fold.
I am not able to find a complete list of languages supported by VS2010. What are these languages?
How can I get VS2010 support for:
Python/IronPython
C/C++/C#/XNA
Java
My Googling has given me no promising/definitive results.
I'd really appreciate any help.
From Wikipedia (search Visual Studio 2010):
"Visual Studio supports languages by means of language services, which allow the code editor and debugger to support (to varying degrees) nearly any programming language, provided a language-specific service exists. Built-in languages include C/C++ (via Visual C++), VB.NET (via Visual Basic .NET), C# (via Visual C#), and F# (as of Visual Studio 2010[3]). Support for other languages such as M, Python, and Ruby among others is available via language services installed separately. It also supports XML/XSLT, HTML/XHTML, JavaScript and CSS. Language-specific versions of Visual Studio also exist which provide more limited language services to the user. These individual packages are called Microsoft Visual Basic, Visual J#, Visual C#, and Visual C++."