Visual Studio Professional 2022 includes features that extend your mobile development experience. Deliver native apps for Android, iOS, and Windows through unrestricted, professional mobile development, code sharing and debugging.
Subscriber benefitsIncludes everything a developer needsWith a standard subscription you get the software and benefits you need to stay up on all things code, including access to core Microsoft software for development and test, monthly Azure dev/test individual credits, collaboration tools, training courses, professional support, and more.
Scale to work on projects of any size and complexity with a 64-bit IDE. Code with a new Razor editor that can refactor across files. Diagnose issues with visualizations for async operations and automatic analyzers.
You can acquire the latest most secure version of Visual Studio 2019 version 16.11 by clicking one of the buttons above, by visiting the Visual Studio site, or by going to the downloads section of my.visualstudio.com. You can get updates from the Microsoft Update catalog. For more information about Visual Studio supported baselines, please review the support policy for Visual Studio 2019.
@andy2kh @zigzag
These are temporary but workable solutions. But I think there should be a permanent and sustainable solution instead. I think the problem may be related to the visual studio version. I should try with an older version of visual studio, or I can wait for the extension to be made compatible with newer versions.
Visual Studio supports running multiple instances of the environment (each with its own set of VSPackages). The instances use different registry hives (see MSDN's definition of the term "registry hive" in the sense used here) to store their configuration state and are differentiated by their AppId (Application ID). The instances are launched by an AppId-specific .exe that selects the AppId, sets the root hive, and launches the IDE. VSPackages registered for one AppId are integrated with other VSPackages for that AppId. The various product editions of Visual Studio are created using the different AppIds. The Visual Studio Express edition products are installed with their own AppIds, but the Standard, Professional, and Team Suite products share the same AppId. Consequently, one can install the Express editions side-by-side with other editions, unlike the other editions which update the same installation. The professional edition includes a superset of the VSPackages in the standard edition, and the team suite includes a superset of the VSPackages in both other editions. The AppId system is leveraged by the Visual Studio Shell in Visual Studio 2008.[19]
Microsoft first released Visual Studio (codenamed Boston,[59] for the city of the same name, thus beginning the VS codenames related to places)[59] in 1997, bundling many of its programming tools together for the first time. Visual Studio 97 came in two editions: Visual Studio Professional and Visual Studio Enterprise, the professional edition has three CDs, and the enterprise four CDs. It included Visual J++ 1.1 for Java programming and introduced Visual InterDev for creating dynamically generated web sites using Active Server Pages.[citation needed] There was a single companion CD that contained the Microsoft Developer Network library. Visual Studio 97 is only compatible with Windows 95 and Windows NT 4.0. It is the last version to support Windows NT 4.0 before SP3.
Visual Studio .NET 2003 shipped in five editions: Academic, Standard, Professional, Enterprise Developer, and Enterprise Architect. The Visual Studio .NET 2003 Enterprise Architect edition includes an implementation of Microsoft Visio 2002's modeling technologies, including tools for creating Unified Modeling Language-based visual representations of an application's architecture, and an object-role modeling (ORM) and logical database-modeling solution. "Enterprise Templates" were also introduced, to help larger development teams standardize coding styles and enforce policies around component usage and property settings.
Visual Studio 2008 is focused on development of Windows Vista, 2007 Office system, and Web applications. For visual design, a new Windows Presentation Foundation visual designer and a new HTML/CSS editor influenced by Microsoft Expression Web are included. J# is not included. Visual Studio 2008 requires .NET 3.5 Framework and by default configures compiled assemblies to run on .NET Framework 3.5, but it also supports multi-targeting which lets the developers choose which version of the .NET Framework (out of 2.0, 3.0, 3.5, Silverlight CoreCLR or .NET Compact Framework) the assembly runs on. Visual Studio 2008 also includes new code analysis tools, including the new Code Metrics tool (only in Team Edition and Team Suite Edition).[140] For Visual C++, Visual Studio adds a new version of Microsoft Foundation Classes (MFC 9.0) that adds support for the visual styles and UI controls introduced with Windows Vista.[141] For native and managed code interoperability, Visual C++ introduces the STL/CLR, which is a port of the C++ Standard Template Library (STL) containers and algorithms to managed code. STL/CLR defines STL-like containers, iterators and algorithms that work on C++/CLI managed objects.[142][143]
Visual Studio 2010 comes with .NET Framework 4 and supports developing applications targeting Windows 7.[152] It supports IBM Db2 and Oracle databases, in addition to Microsoft SQL Server.[152] It has integrated support for developing Microsoft Silverlight applications, including an interactive designer.[152] Visual Studio 2010 offers several tools to make parallel programming simpler: in addition to the Parallel Extensions for the .NET Framework and the Parallel Patterns Library for native code, Visual Studio 2010 includes tools for debugging parallel applications. The new tools allow the visualization of parallel Tasks and their runtime stacks.[155] Tools for profiling parallel applications can be used for visualization of thread wait-times and thread migrations across processor cores.[156] Intel and Microsoft have jointly pledged support for a new Concurrency Runtime in Visual Studio 2010[157]and Intel has launched parallelism support in Parallel Studio as an add-on for Visual Studio.[158]
The final release of Visual Studio 2013 became available for download on October 17, 2013, along with .NET 4.5.1.[189] Visual Studio 2013 officially launched on November 13, 2013, at a virtual launch event keynoted by S. Somasegar and hosted on events.visualstudio.com.[190] "Visual Studio 2013 Update 1" (Visual Studio 2013.1) was released on January 20, 2014.[191]Visual Studio 2013.1 is a targeted update that addresses some key areas of customer feedback.[192]"Visual Studio 2013 Update 2" (Visual Studio 2013.2) was released on May 12, 2014.[193]Visual Studio 2013 Update 3 was released on August 4, 2014. With this update, Visual Studio provides an option to disable the all-caps menus, which was introduced in VS2012.[194]"Visual Studio 2013 Update 4" (Visual Studio 2013.4) was released on November 12, 2014.[195]"Visual Studio 2013 Update 5" (Visual Studio 2013.5) was released on July 20, 2015.[196]
We've been using Visual Studio 2017 for a while now but I want to upgrade to VS2019. Looks like rptproj files are not compatible with VS 2019. I've been looking on how to do this and it looks like I'm best creating a new solution and importing the rdl files from the vs2017 version in to there. Problem is I can't find a way of creating a new project for SSRS without installing an extension. I've tried to install the Microsoft Reporting Services Projects extension but it fails stating "Microsoft Reporting Services Projects: the file is not a valid VSIX package". I think I've added the correct toolset *data storage and processing" and "Visual studion extension development" but it still doesn't work. Can someone help please? I may well be going down the totally wrong path here so if there's a better way of creating SSRS reports then please let me know.
A repair install doesn't hurt though - it could be something with an update or if your computers were built from a WSUS image (for example) with VS2019 pre-installed, the image may have some missing information. In my environment, developers are given base installs of machines when they get a new machine which comes with a bare Windows install and an Office install. It is up to the developer to install any development related tools (visual studio, git, etc). There are 2 reasons for this - licensing costs (to install a Visual Studio subscription based tool (formerly MSDN), you NEED to have a Visual Studio subscription at the same level or higher as the tool being installed), and tools required (IT has no idea what tools I require. My requirements may not match a coworkers requirements for example. I may "require" SSRS with VS2019 while a coworker in my department may no no SSRS work and may require SSIS with VS2012 to support an older system). If you and your coworker both had VS2019 installed by someone other than you, it MAY be an improper install and in need of a repair. Or it may be you lack permissions to install extensions into VS2019. I am not sure what permissions are required to install extensions. OR your antivirus may be grabbing the extension and quarantining it before VS can install it. But I'd tackle the "repair install" route first as that is the easies one to handle (my opinion).
Visual Studio Professional is a paid plan that costs around $45 a month and comes with a basic Azure DevOps plan. It's best for professionals for both individual developers and small teams who seek professional developer services and tools:
Tools and Resources: The Professional plan offers you access to core Microsoft tools for testing and development, educational courses, professional support, collaboration tools, and Monthly Azure credits.
So, if you're an individual developer, you can go for Visual Studio Community. And if you're an organization with over 250 PCs or revenue of more than USD 1 million per year, you must opt for the professional version to meet your development needs.
582128177f