Add VB.NET to Visual Studio 2010 Professional - vb.net

In the past I have only used Visual Studio 2010 Professional for C#, but now I need to work on a little bit of Visual Basic. When I go to create a project it only shows C# project templates. I am assuming when I installed Visual Studio 2010, I only installed C#.
How do I now install VB.NET support?
I tried following a MS tutorial: I went to Control Panel and selected Change/Uninstall on Visual Studio, but then it asked me to insert a CD, of which I have none since it was donwloaded.

Nevermind I figured it out. (win7) Control Panel -> Programs and Features -> Uninstall/Change on Visual Studio -> then when you hit the Add/Remove features and you get the popup asking about the cd (which is where I assumed i was stuck before) if you hit Download it takes you to the dialog where you choose additional languages to install and it worked.

I apologize for my earlier flippant comment, and offer you
http://download.cnet.com/Microsoft-Visual-Studio-2010-Professional/3000-2212_4-10618634.html

I had same problem but i did the simplest solution ,since i had my .iso(visual studio express) file i had downloaded I used my winrar to extract files ,went to VBExpress ,open the folder and click on the setup and it all worked out successfully...

Related

Uninstall Atomineer

Looks like I am being held hostage by the Atomineer Pro Documentation add-in for Visual Studio! The trail period is over, I have no use for it! But now everytime I do something in Visual Studio I get an error message and get sent to their web site!
I have looked all over to find out how to uninstall it and have not found away to uninstall it!
WARNING TO EVERYONE - This Atomineer Pro is not easy to uninstall!! Just from the problems of uninstalling it, I would highly recomend no one ever installs it!
I ran into this too running on Windows 10 and VS 2013. Ended up installing and running IObit Uninstaller, which clean up the registry, but Atomineer was still loading in Visual Studio. My second pass was to search my C: drive for "Atomineer" which got several hits including some in a VS AddIns folder (I think). I just deleted everything and that did the trick.
Visual Studio 2015 onwards (Standard VS Extension)
In Visual Studio, go to Tools > Extensions and Updates, select Atomineer from the list, and click the Uninstall button.
Visual Studio 2005-2013 (Standard VS Add-in)
Use Control Panel > Programs and Features to uninstall it just like any other app, or
Run the Atomineer installer and select "uninstall", or
In the unlikely case that neither of the above work, you can manually search your drive and delete any "AtomineerUtils.Addin" files you find.
In any case if you have any problems, email Atomineer support and we'll be happy to help.

Modifying and running VB.net project in Visual Studio Code?

Is it possible to modify and run existing VB Visual Studio 2010 projects in Visual Studio Code? I have some VB.NET projects that I would like to open in visual studio code and I haven't found anything online that says whether or not this is possible. Drag and drop functionality isn't necessary for me, I only care about being able to run the source code.
I'm running Ubuntu 14.04 if that makes any difference.
Thanks in advance!
You can use Visual Studio Code to edit any text file you want.

How to open visual basic 6 program with visual studio.net

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

vs 2008 broken snippets functionality

Is there a way to reset to the original vb.net snippets that came along with visual studio 2008?
I recently installed a purchased third party lib, that managed to break almost all the default snippets.
I can see that the snippets do physically exist in C:\Program Files\Microsoft Visual Studio 9.0\VB\Snippets\1033 but only the following sections are loaded to vs 2008:
application
office development
os
wpf
Any help would be appreciated...
Found a solution !!!
I went to tools > Code snippet Manager
and re-added the C:\Program Files\Microsoft Visual Studio 9.0\VB\Snippets\1033 folder
Everything works great now !!!
You can try to reset the IDE-settings by calling it with /resetsettings
It sounds like your SnippetIndex file is broken. There should be a file at the directory you listed named SnippetIndex.xml. This is the file that is consulted in order to build the initial list of snippets. Can you check that file and see how big it is. It should be at least 500+ lines (mine is 579).
If it's less then this is almost certainly your problem. You can fix this by repairing the Visual Studio install
Go to Control Panel -> Add Remove Programs
Select Visual Studio
Choose Repair

Visual Studio Tools for Office (VSTO 2005) newbie deployment question

I have Visual Studio setup with a VSTO word project, and when I hit run it runs fine.
But, how do I setup a word document to use my code without having Visual Studio running?
You must deploy the VSTO runtime whether by hand or with an installer. Check out this blog post for a detailed explanation.
You can do it using a Windows Installer project; starting point here. You can also use the Publish Wizard.
A more general starting point can be found in MSDN here.