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++."
Related
recently I have switch to .net core. I have checked the .NET is now open source and .NET core can be developed by visual studio or visual studio code.
Below are my questions:
if .NET is now open source. why do I need to spend $ on the VS paid version (professional or enterprise instead of community)?
if I develop .NET core on VS code. How can I compile the .net core for debugging? Or i can only debug in the visual studio?
Can I develop/customize a product by only using vs community + vs code for my users commercially? (for example I want to customize an headless CMS which has the .NET core reference)
Thanks
Visual Studio Community
Visual Studio Community is an extensible free IDE, completely loaded,
designed to build mobile software for Android, iOS, Windows, web, and
cloud applications.
Visual Studio Community is the best option if you want to use Visual
Studio without spending a lot of money.
Visual Studio Professional
Visual Studio Professional is a Microsoft Collaborative Development
Area. It is used to build software, blogs, desktop browsers, online
services, and smartphone applications.
Visual Studio Enterprise
Visual Studio Enterprise contains a Mac Digital design. You can
recognize and enjoy the same visual studio interface, which has been
beautifully built and optimized for Mac. It is counted as the most
dynamic and is filled with rich and new features. Software architects
can use this medium in the best possible way and make the most out of
it effortlessly.
Develop new, quicker, and simpler than ever before, windows, or
Mac-based mobile applications with enterprise-grade software. It has
been specifically designed to help you experience the best services
and state-of-the-art features.
Visual Studio Community vs. Professional
The Visual Studio Community is open, whereas the professional edition
is not accessible. The community can be used by developers or a
smaller team of at least five individuals. But there are few
limitations to the professional edition.
It can also be used by a group of 5 to 25 developers. Another
important distinction is that the professional version supports the
business, while the visual studio community does not. The predominant
distinction between community edition and professional edition is a
widely renowned feature known as CodeLens. There are a plethora of
significant benefits that are offered by CodeLens, such as the users
can easily determine code changes along with other pertinent
histories.
One more important point that has to be addressed here is that the
difference between them shrinks considerably. However, when you are
supposed to be working in a large team, only then is the difference
relevant. These could be automated unit tests or collaboration tools.
Individual developers or even small teams incorporate the community
edition for the purpose of commercial development. Now, this small
group might involve five.
Visual Studio Community vs. Enterprise
Visual Studio Enterprise is for major corporations that get more
sales and earnings per year. At the same time, the community edition
is a free version, which can either be used for open source projects,
for research purposes or as a team of five or fewer developers, under
a variety of conditions.
Visual Studio Professional vs. Enterprise
The Enterprise version is filled with many features compared to the
Visual Studio Professional edition.
Check this link to compare the differences between the different versions
Hence, if you like to use Visual Studio Version for your own benefit, the community edition suits the best; there is no advantage of using Enterprise rather than Community Edition. Always remember, community edition is the professional edition for personal applications.
You can also debug in VS code, refer to this link
Check the MICROSOFT SOFTWARE LICENSE TERMS
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:
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 8 years ago.
Improve this question
The current version of Unity uses the old MonoDevelop 2.8 which is very primitive. Not only that it cannot register compile errors, I am also unable to know which method I can use. Each time I want to use some built-in method (like OnGUI or OnTriggerEnter) I have to search them manually.
Since I am coming from the world of IntelliJ IDEA or Eclipse or VisualStudio, this is a very primitive way of working.
I tried using the latest Unity with the newest MonoDevelop 4.0, but I did not succeed.
Can you suggest a modern IDE which I can use with Unity, the one where I will enjoy coding?
Updated 02/08/2022
JetBrains Rider
There's a new cross-platform .NET IDE by JetBrains - Rider with build-in resharper-like commands and quite a list of features including rich web development support and specifically Unity
Unity support
Deeper integration with the Unity Editor: if a method/script is used in a scene, prefab, or asset file, navigating from the Find Usages tool window to this usage will highlight the usage right in the Unity Editor.
Gutter mark icons for classes, methods, and fields that are implicitly used by Unity have been moved to Code Vision.
Check that a compilation in Unity was successful before running unit tests through Unity Editor in Rider.
Comments: I've been using it for some time already and my impression is very positive. It's faster compared to Visual Studio and has some really awesome hotkey combos, not to mention support for AceJump and a ton of other useful extensions.
Visual Studio C# Integration
What does this feature get me?
A more sophisticated C# development environment.
Think smart autocompletion, computer-assisted changes to source files, smart syntax highlighting and more.
What's the difference between Express and Pro?
VisualStudio C# 2010 is a product from Microsoft. It comes in an Express and a Profesional edition.
The Express edition is free, and you can download it from here: http://www.microsoft.com/express/vcsharp/
The Professional edition is not free, you can find out more information about it here: http://www.microsoft.com/visualstudio/en-us/products/professional/default.mspx
Unity's VisualStudio integration has two components:
Unity creating and maintaining VisualStudio project files. Works with Express and with Profesional.
Unity automatically opening VisualStudio when you doubleclick on a script, or error in Unity. Works with Professional only.
I've got Visual Studio Express, how do I use it?
In Unity, select from the menu Assets->Sync VisualStudio Project
Find the newly created .sln file in your Unity project (one folder up from your Assets folder)
Open that file with Visual Studio Express.
You can now edit all your script files, and switch back to Unity to use them.
I've got Visual Studio Professional, how do I use it?
Note: With Microsoft's Acquisition of SyntaxTree, Visual Studio Tools for Unity (formerly known as UnityVS) has been released free of charge in the Visual Studio gallery.
This replaces the below steps for users of Visual Studio Professional and removes a number of caveats mentioned further below, allowing for debugging within VS, advanced project file integration, a mirrored console window withing VS, and more.
In Unity, go to Edit->Preferences, and make sure that Visual Studio is selected as your preferred external editor.
Doubleclick a C# file in your project. Visual Studio should automatically open that file for you.
You can edit the file, save, and switch back to Unity.
A few things to watch out for:
Even though Visual Studio comes with its own C# compiler, and you can use it to check if you have errors in your c# scripts, Unity still uses its own C# compiler to compile your scripts. Using the Visual Studio compiler is still quite useful, because it means you don't have to switch to Unity all the time to check if you have any errors or not.
Visual Studio's C# compiler has some more features than Unity's C# compiler currently has. This means that some code (especially newer c# features) will not give an error in Visual Studio but will give an error in Unity.
Unity automatically creates and maintains a Visual Studio .sln and .csproj file. Whenever somebody adds/renames/moves/deletes a file from within Unity, Unity regenerates the .sln and .csproj files. You can add files to your solution from Visual Studio as well. Unity will then import those new files, and the next time Unity creates the project files again, it will create them with this new file included.
Unity does not regenerate the Visual Studio project files after an AssetServer update, or a SVN update. You can manually ask Unity to regenerate the Visual Studio project files trough the menu: Assets->Sync VisualStudio Project
Visual Studio Code (Windows, macOS, Linux)
Unity supports opening scripts in Visual Studio Code (VS Code). To open scripts in VS Code, go to Unity > Preferences > External Tools > External Script Editor and select Visual Studio Code. For information on using VS Code with Unity, see Visual Studio’s documentation on Unity Development with VS Code.
Prerequisites
To use Visual Studio Code for C# code editing and Unity C# debugging support, you need to install:
Mono (only required on macOS and Linux)
Visual Studio Code C# Extension
Visual Studio Code Debugger for Unity Extension (Not officially supported by Unity)
Sources:
http://docs.unity3d.com/Documentation/Manual/VisualStudioIntegration.html
https://docs.unity3d.com/Manual/ScriptingToolsIDEs.html
In Mac
1) Visual Studio Code
Lightweight
Support debug
https://code.visualstudio.com/
2) Consulo
Intellij IDEA based IDE
Support debug
https://github.com/consulo/consulo
3) Sublime Text also can be your choice on Mac.
Using Sublime Text as a script editor
There are some useful packages for unity too. (Code Completion, Syntax coloring...)
ST package for unity3d
And Video Tutorial
You can use MonoDevelop or SharpDevelop. I need to highlight that all the capability in the .NET framework and not in the IDE in other words you can use text editors and CLR compiler without the need to use any IDE.
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 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.