I installed Visual Studio Preview and it works fine but recently I saw this in their release notes and it says
This release is not "go-live" and not intended for use on production
computers or for creating production code. For instructions on
installing and updating Visual Studio 2019, see this documentation on
updating Visual Studio 2019 to the most recent release.
so if I want to write production code do I need to install another stable version too(it takes more space)? and I'm happy with this version cause it's cool and sometimes can try preview versions of new technologies/frameworks.
and What I'm not able to do exactly with this preview version?
The not having the "go-live" just means that Microsoft is not guaranteeing support if used in production environments, because it contains pre-release/beta features and/or libraries. Meaning if you deploy production code from a non "go-live" preview version of VS, you're on your own and can't call Microsoft for support/issues.
Occasionally, Microsoft will issue a "go-live" preview version (particularly with Release Candidates) that they will support.
Related
I'm currently facing some issues with the latest Visual Studio 2019 version (16.7.0) and I want to go back to a previous version, specifically 16.6.2. However on the VS website I can't find a place where to download a specific version of Visual Studio, so is there a way (even non official) to download this version?
Officially, Microsoft provides older installer for VS 2019, but only the Enterprise, Professional, and Build Tools. Meanwhile Community edition
is only supported on the recommended latest release of the latest minor version of Visual Studio
So if you expect to be needing VS Community older version in the future, I suggest backing up the offline installer when they're released.
In case you need to install a specific version of the Community Edition you can download VS 20XX Professional Edition with the desired version and then, during installation, just select the Community Edition.
Steps:
Download the installer with the required version (release history for VS2022)
Open the installer and when the Workloads screen appears, close it to view the setup screen behind.
On the setup screen go to the "Available" tab
Choose the Community Edition (or the one you need...)
you can download the older version of Visual studio 2019:
https://learn.microsoft.com/en-us/visualstudio/releases/2019/history#installing-an-earlier-release
For VS2022, the list is here:
https://learn.microsoft.com/en-us/visualstudio/releases/2022/release-history
I have a Microsoft Visual Studio solution that I have been using for many years for producing a new release of our software application. One of the projects has recently stopped loading.
It looks like the problem may be similar to:
Visual Studio 2013/2015 Can't Load Azure Project
However in that case it was a new installation of Visual Studio.
Looking in add/remove programs it appears that 'Microsoft Azure Tools for Microsoft Visual Studio 2013' has an installed date of 19th May this year and version number 2.5.21104.1601.
What is the simplest way for me to fix this problem? Should I uninstall the Azure Tools and see if I can download and install V2.4? or do I need to install a new version of Azure SDK, as the other question suggests?
Another option I have, might be to upgrade to Visual Studio 2017. I have been reluctant to do this, as am not sure what things might break.
EDIT: I notice in Extensions and Updates there is Microsoft Azure SDK 2.9 available. Should I install this?
Any suggestions appreciated.
Thanks
Phil.
As you said you could try installing Microsoft Azure SDK 2.9.
Here is the Microsoft Release summary for Azure SDK 2.9.
Before installing Azure SDK 2.9 you should read this document whether your project having all the support in this SDK. If not then you should upgrade to, VS 2017.
From a developer word, I'd say upgrade to VS 2017 where you get/support all the latest features in your hand.
I have VS2017 (15.5.4) Professional already installed and today I installed .Net Core SDK 2.1.4 but I cannot see any Core templates in the New Project dialog in VS.
If I run dotnet --version in Powershell, it correctly shows me 2.1.4 installed
I have removed all Core installations on my windows 10 machine, reinstalled 2.1.4, run the repair on VS and also tried devenv /installvstemplates but nothing seems to work.
Can anyone help please?
For .NET Core 2.1, you need Visual Studio version 15.7 or higher. (check it from Help menu > About Microsoft Visual Studio). So, first ensure you have update your visual studio.
Now, to add .NET Core 2.1 (or other newer templates) to visual studio, you need to install the Latest .Net Core SDK from here.
For any templates: Make sure VS has the necessary components, make sure that the cross platform development workload is installed through the Visual Studio Installer.
The SDK 2.1.* only contains the 2.0.* runtimes. At the time of writing, there has been no public preview release for .NET Core 2.1.
You can download 2.2.0 SDK previews from https://github.com/dotnet/cli.
Note that the naming may change in the near future in order to avoid confusion and keep the SDK and Runtime major and minor versions in sync - see https://github.com/dotnet/designs/pull/29.
Update Visual Studio to version 15.6.0.
I have installed full version licensed Visual Studio 2010 Professional, .Net 4.0 on my system. Now I am trying to install Active Reports 6 on it and facing the error "no compatible version of visual studio net found on system". My Active Reports build is 6.0.1.1797.0.
So, do I need to install framework 3.5 before installing? I have not installed Service Pack for visual Studio for now.
Thanks.
Active reports 6.0.1797.0 does not support Visual Studio 2010. Active reorts 6.1.2577 or later supports Visual Studio 2010. And any how, Express edition of visual studio does not support active reports.
So my solution, enhances...I installed the later versions...but unfortunately I am getting some errors in my application because of Active reports version change as my application was made in previous version of Active Reports. So, what I did is, installed the latest version, uninstalled it and again installed 6.0.1797.0 version, and it was installed successfully and my application was also working fine.
#rapsalands...You are correct in understanding that support for Visual Studio 2010 started only after build 6.1.2577.0 was released. Also express edition of Visual Studio is not supported. The first thing to note here is that whenever you install/uninstall ActiveReports 6 from your machine, there should be no running instance of Visual Studio as it affects proper integration of ActiveReports with itself.
Also the errors which you were getting are more likely appearing because of the incorrect references in your project. Whenever you open an existing project after upgrading ActiveReports build, you should remove all the ActiveReports references from the project, re-add them (making sure they point to the version currently installed) and finally rebuild your project.
I think you can also check the blogs for ActiveReports as you might find some useful information about different topics there.
I downloaded VS 2010 RC and want to try it out.
Can I use it to create commercial software?
When will the final version be released?
The final version of Visual Studio 2010 will probably be released on April 12th, 2010.
However, you can already use the release candidates of Visual Studio 2010 and .NET Framework 4 which both are go live releases (since Beta 2). This means that there will be no breaking changes in the final release versus RC that will make your software unusable, and that they are licensed for developing and deploying production applications.
As with all Visual Studio versions, it is possible to target another earlier .NET framework version, that is you can still develop for .NET 2.0 as an example.
It is also possible to – and in fact a good idea – install Visual Studio 2010 Release Candidate side-by-side with other versions of Visual Studio.
All in all I see no risk in trying out Visual Studio 2010 Release Candidate. It is obvious that it is not the most stable piece of software at this moment, but certainly usable.
You can still target previous Framework versions so if you want to develop applications there is no reason why it should be any different. The issue would come if you tried to develop .Net 4 solutions as there will not be many people using that yet, especially commercially
Believe the final version will be released end of March. Until then you can't distribute it to customers as the .NET 4.0 installer won't be made available to them.
Is it wise to do so? Well it probably depends on your product. If it's mission critical I'd wait till it's been used for a bit and any bugs are ironed out of .NET 4.0 via service packs. For normal applications I don't really see why not, it's had some pretty rigorous testing internally and by dev's I'm sure.
As long as you're not targeting the 4.0 runtime, you can use it to develop and deploy applications today.
Visual Studio 2010 can target previous versions of the .NET framework, so that's not a problem. However, projects or solutions that were created or modified with Visual Studio 2010 cannot be opened by Visual Studio 2008 without manually editing the project files. So I would definitely not recommend upgrading to VS2010 if you work on a team and your teammates still use VS2008.
I tried vs 2010 beta 2 with a MFC application. The intelisense is improved but the compilers has some problems - sometimes it just freezes and I have to restart VS. Maybe this was fixed in the RC version that was released a few days ago.
Take in consideration that you might have to pay a price (instability) for new technologies.
Work on whatever you want, but I think you should study your customers, as to what OS do they use, are they looking to upgrade, the effects of net 4.0 on your application, etc...
Whenever these things come out, there should always be a phasing plan in place. Although, it's more work, I personally think that it's a great approach
VS2010 is not yet released for commercial use. So if you are using it for commercial use, it is not appropriate. Though it was planned for March 2010 release, you can expect it with some possible delay.