I recently updated to Visual Studio 2022 Preview 2.1 but it constantly hangs when editing razor files.
I would use Visual Studio 2019 but it is not so simple as I have made extensive use of the global using directive.
I was wondering if there was a way to downgrade to the earlier preview of Visual Studio 2022 Preview 1.1 which worked very well.
I found a site where one could find all previous releases of VS2019 however that is not of much use to me.
I want to try out Blazor and it wants Visual Studio 2019 Preview. Now, I already have Visual Studio 2019 (Professional) on my machine. It is safe to install the Preview version side-by-side?
Tried to find any help on forums, but didn't find any advice.
Ok, I'll answer my question myself. Visual Studio 2019 Preview works fine side-by-side with released Visual Studio 2019. And I only got Blazor to install after I installed VS 2019 Preview.
Link to official Blazor Getting Started Documentation which specifically requires the Preview version (as of today)
I have installed Crystal report 2011 SP4 on my system where VS 2012 and 2013 are already isntalled. I dont see Crystal Report showing up in Add New Item -> Reporting dialog box.
According to this document https://www.tektutorialshub.com/install-crystal-reports-visual-studio/#Visual-Studio-2013-VS-2013 you might need a newer version of CR:
Visual Studio 2012 (VS 2012)
You can install SP 7 or higher.
Visual Studio 2013 (VS 2013)
Any version above the SP 9 is allowed
Is there a reason why the references count (code lens) is missing in Visual Studio Community edition?
Is is possible to enable it in the options?
Here is a screenshot of Visual Studio 2015 and 2017 Community edition:
Here is a screenshot of Visual Studio 2013:
source: dailydotnettips.com
I installed the latest SSDT preview for Visual Studio 2015 from the link below on 2 machines I have with VS 2015 Community edition (Update 1), and CodeLens started working for all my projects.
https://msdn.microsoft.com/en-us/library/mt204009.aspx
This isn't a generic reference counting feature, it's just one of the features of CodeLens. CodeLens is only available in Visual Studio 2015 Pro and above. In Visual Studio 2013 it was a Ultimate-only feature.
UPDATE
As others have noted, installing SSDT or SSMS 2016 may enable CodeLens as well. That's because VS 2015 Community is Pro, with a different license and some missing extensions like CodeLens. As long as an extension's binaries and settings are installed, Community will activate the extension.
UPDATE 2019
"CodeLens has been a feature found only in Visual Studio Enterprise, but that will change in an upcoming preview of Visual Studio 2019, when it will also be available for the Community edition, likely in 2019"
What's New in Visual Studio 2019
I have Visual Studio 2015 Community edition and it originally did NOT have CodeLens.
However, after going to Tools -> Extensions and Updates -> Product Updates and then downloading SSDT and installing all options within the SSDT package, my VS 2015 Community Edition now miraculously has access to CodeLens.
On the Tools tab choose Options.
In the open window choose like bellow, and then press ok.
Good Luck!!!
This feature has been disabled in Visual Studio Community 2017, although it sounds like it was temporarily available in pre-release versions.
The Visual Studio Team issued this statement on the 14th of March 2017:
An authoring error in the SQL Server Data Tools resulted in the
capability temporarily showing up incorrectly in Visual Studio
Community when installed; the change you see is a result of correcting
that mistake.
Also, on the Compare Visual Studio 2017 Offerings page CodeLens appears to not be available in the Community edition.
I'm not allowed to Comment on R. Richards answer above, so posting this as a separate answer: CodeLens references disappeared for me too when I upgraded my VS Pro to 2017. But only on my Desktop ("same" upgrade behaved differently on my laptop, where CodeLens settings apparently unaffected). Anyway, very easy to resolve just Enable CodeLens under Text Editor : All Languages
An alternative is to just right-click the member and select 'Find All References' or the hot key shift + F12*. Not only you will find the count of references grouped by project, but also the underlying code lines and their classes.
* As per Visual Studio 2017 Community.
I have a Visual Studio solution developed in VS 2013. The solution included a setup project bu InstalledShield Limited Edition. Visual Studio 2015 says the setup project is not compatible. I reinstalled InstallShield which didn't didn't help. I don't see anything on Flexera's site about InstallShield which works in VS 2015. Are there plans for one or does Microsoft now want us to use something else for installation projects?
While you could theoretically register the extension manually, as in our initial testing that's the minimum required to get ISLE 2013 up and running, we have now released ISLE 2015, so you should update. This release includes support for Windows 10, Visual Studio 2015, .NET 4.6 (including a fix for the 1001 error from installing .NET 4.6), and other enhancements and bug fixes since the 2013 release.