Is it possible to use ANTLR with Visual Studio 2013?
I installed ANTLR language support, which says it is for VS 2010 and 2012. And when I install the ANTLR 4 NUGET package into a VS 2012 project, then right-click the project and select add new item, a bunch of ANTLR-related file types come up in the menu -- ANTLR4 Combined Grammar, and so forth. But when I do the same thing in VS 2013, the ANTLR-related file types do not appear.
The ANTLR 4 NuGet package and the ANTLR Language Support extension are two completely independent products (neither depends on the other, although they are most often used together).
The ANTLR 4 NuGet package does not depend on any specific version of Visual Studio, so it works fine with Visual Studio 2013. As of today, the ANTLR Language Support extension has been released for Visual Studio 2010 through Visual Studio 2013.
Related
In Visual Studio 2019 *.vbhtml files were working fine in my computer. After upgrading to Visual Studio 2022, C# IntelliSense and highlighting are still working, but in VB IntelliSense and highlighting fully disappear.
Also, any attempt at adding VB templates (Microsoft.VisualStudio.Web.CodeGeneration.Design) became forbidden.
Is there a way to bypass these restrictions and unblock VB in Razor Pages with some tuning of Visual Studio or with some extension for Visual Studio or with some 3rd party product?
Razor Pages are no longer supported in VB.NET after MVC5. As noted, editing and compilation (without IntelliSense) did work under Visual Studio 2019, but that functionality has been removed in Visual Studio 2022.
A working alternative for MVC and Razor Page projects in VB.NET under .NET Core 6 is Vazor, which can be found here.
My final solution you can see there https://github.com/Alex-1557/SplitViewAndCodeInAsp.Net.Core.Project/tree/main
Yes, have I lost opportunity to use VB in View and VBHTML, but I receive opportunity to split ASP.NET Core project to 2 full different projects.
For connect static files to root I have rebuilded this extension https://marketplace.visualstudio.com/items?itemName=CeciliaWiren-CeciliaSHARP.FolderToSolutionFolder
for Visual Studio 2022 - https://marketplace.visualstudio.com/items?itemName=alexev14.AddFolderToSolutionForVS2022
I have a number of projects created in earlier version of Visual Studio. These open fine in 2017, I can edit and save changes, but the solution file still has the icon indicating they are VB10, VB11 or VB14 solutions.
My concern is that in later versions of Visual Studio the solutions will no longer be supported. Can I force a complete upgrade to Visual Studio 2017? Is this necessary?
I'm currently working on a Visual Basic project with a team of developers, some of which will be able to move to Visual Studio 2015 as soon as it is released, and some who will be stuck on Visual Studio 2013 for several months. In testing with the RC we have found that Visual Studio will open 2013 projects without a problem, but will happily let users use new language features, such as string interpolation, that are not available for users in VS 2013. If a 2015 user checks in this code the 2013 users will get compile errors. Is there any project, solution, or Visual Studio setting that will tell the compiler to restrict features to what is available in the previous version of VB.net? Ideally the compiler should return a compile error when trying to use these features in 2015.
This features is available in C# under Project Properties > Build > Language Version, but I can't find any equivalent for VB.net, and the google searches are failing me.
I just wanted to mention that setting the .Net runtime version to 4.5 doesn't help, as these new language features are compiler level features that work perfectly fine on older frameworks.
There is no UI feature to set the Language version, but you can unload the project file and add <LangVersion>11</LangVersion> to default Visual Basic to the 2012/2013 language settings. The C# project adds this property under the Project Configuration property groups, so for consistency's sake I've done the same in the sample below.
The C# property pages do the same thing, except that C# uses a different set of version numbers.
A full set of all the language versions can be found here.
2002 (VB 7.0)
2003 (VB 7.1)
2005 (VB 8.0)
2008 (VB 9.0)
2010 (VB 10.0)
2012 (VB 11.0)
2015 (VB 14)
Just tested and this works for me, but I did have to change the casing to:
This results in:
And a nice build failure:
I want to create my installer. But missing Other Project Type > Visual Studio Installer > Setup Project
They are not supported anymore on VS2012.
http://blogs.msdn.com/b/buckh/archive/2011/03/17/visual-studio-setup-projects-vdproj-will-not-ship-with-future-versions-of-vs.aspx
VDProjects are no longer supported. Either:
Use older versions of visual studio to build existing VDPROJ project types (you can keep them in the solution)
If creating new installers, use a framework such as WiX which contains Visual Studio integration. Little bit of a learning curve, but a very good product (and free). This will produce an MSI from XML within a WiX project in visual studio after you install it.
http://wixtoolset.org/
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