I know that, officially, Portability Analyzer does not support Visual Studio 2022.
But is it possible to somehow get an analysis of the migration from .Net Framework to .Net 6?
Is it possible somehow in the Visual Studio 2019 to get a portability analysis of the .net 6?
Will it be enough that porting to .Net 6 will have the same compatibility as .net 5 or .Net Standart 2.0?
i am trying to learn .net core with VS 2017. i dont have any basic idea about .NET Core development. Can any one suggest how can i start my first sample development in Visual Studio 2017?
To start with ASP.NET core, you must have visual studio 2017 installed and download the .Net Core SDK from: https://dotnet.microsoft.com/download/dotnet-core. I recommend that you download version 2.2 for VS 2017.
And have the web development package installed through Visual Studio Installer.
But, it would be better if you already started your studies with the VS 2019.following the same steps above.
VS 2019 already comes with SDKS for .Net core development
Can I work in my ASP.NET Core 2.1 Preview 1 project in Visual Studio 2017 (15.6.3) which is released today? https://learn.microsoft.com/en-us/visualstudio/releasenotes/vs2017-relnotes#15.6.3
I've been using Visual Studio 2017 Preview version to work on my ASP.NET Core 2.1 project up until now -- as this article suggests: https://blogs.msdn.microsoft.com/dotnet/2018/02/27/announcing-net-core-2-1-preview-1/
I want to know if I can switch back to the stable version of Visual Studio 2017 now.
When launching a solution that contains a .NET Core 2.1 project with Visual Studio 15.6.3, there will be the following message:
The link there goes to this page:
.NET Core 2.1 Preview 1
To create or open applications targeting .NET Core 2.1, Visual Studio 2017 15.7 or newer is recommended. Right now 15.7 is only available as a preview, so please use the latest Visual Studio 2017 Preview.
Visual Studio 2017 15.6 supports creating and opening applications targeting .NET Core 2.1, but it contains known issues so 15.7 or newer is recommended.
Visual Studio 2017 15.5 does not support creating or opening applications targeting .NET Core 2.1.
So you can absolutely use VS 15.6 for .NET Core 2.1 projects. In fact, just today I was working on a .NET Core 2.1 project (actually using a daily build), and I did not encounter any issues with my non-preview Visual Studio.
But there may be issues, e.g. with tooling related to scaffolding, so you should be prepared that things might break. But for normal work on an existing code base, there shouldn’t actually be any problems. And you could always fall back to the dotnet CLI for the things that don’t work.
tl;dr With the 15.6.3 update, there is still no official support for .NET Core 2.1 projects but there may be very few issues that will prevent you from actually working with it.
i am a c# web developer and vb.net project is not familiar for me.
i have a project in .net 2.0 that i want to upgrade it to .net 4.0 with using visual studio 2010.
when i open that project with visual studio 2010 every thing is normal and it seems it is working in .net 2.0.
i created a new project with visual studio and added all .net 2.0 project files to the new project.
but after that i had many errors like below :
'List' is not declared. It may be inaccessible due to its protection
what did i do wrong and how can i upgrade that project?
also where can i find the project's .Net framework ver for VB language (in c# we can change it by right clicking on project and properties, but here there is no such a properties)?
thanks in advance
You have "Visual Studio Conversion Wizard"
http://msdn.microsoft.com/en-us/library/dd483478(v=vs.100).aspx
.NET 4.5 is an in-place-upgrade and therefore replaces .NET 4.0. Consequently when I install .NET 4.5 with Visual Studio 2012 I can no longer develop applications for .NET 4.0.
As .NET 4.5 is not supported under Windows XP, how can I maintain my existing .NET 4.0 applications which still have to run under Windows XP after I installed Visual Studio 2012?
Until now I could always devlop .NET applications for every version, even .NET 1.1, as long as VS2003 was installed. I don't have a problem with Microsoft not supporting .NET 4.5 on XP, I think it's allright to cut off old stuff.
But as we have still customers using Windows XP, we need to be able to create .NET 4.0 programs at the same time as .NET 4.5.
EDIT:
I just had my first incompatibility issue: I installed VS 2012 on a Windows Server 2012. I created a project targeting .NET 4.0. In blend 4.0 I create a copy of a control template of a checkbox. The generated template contains references on colors which are available only under .NET 4.5. The solution cannot be compiled any longer. However the same case works fine on my Windows 7 installation.
I assume that the installation of .NET 4.5 has replaced the control templates for my standard controls. Therefore I cannot create copies any longer.
Ironically, it seems Mono supports much of the .NET 4.5 functionality, and that it can be installed on Windows XP.
If your need C# 5.0's async and your client refuses to upgrade it's OS, this can be an option.
I have run into some serious issues developing .NET programs for 4.0 against computers with 4.5 installed. One issue, for instance, is that if you are doing WPF development and have a private setter on a property - if you're binding to that property with Mode=TwoWay, you will not get an exception if you're developing against .NET 4.5! You should get an exception and you will if you're in an environment with only .NET 4.0 installed (even though you're developing to target 4.0 in Visual Studio). Now obviously you should not have Mode=TwoWay and a private setter, but maybe you had originally intended for the property to be only OneWay. The point is that this is just one of many examples of issues that are simply swept under the rug by 4.5 and has caused me to go back to developing in Windows 7 with Visual Studio 2010 and .NET 4.0 for anything targeting .NET 4.0.
In the meantime I have found a great blog of Scot Hanselman which answers my concerns: http://www.hanselman.com/blog/NETVersioningAndMultiTargetingNET45IsAnInplaceUpgradeToNET40.aspx
.NET 4.5 is an in-place-upgrade and replaces the .NET 4.0 CLR, but it will still be possible to create .NET 4.0 applications with Visual Studio 2012.
EDIT: I now installed the final release of VS2012. My existing .NET 4.0 projects compile and run, no problems so far. The only drawback is, it doesn't support Windows Installer Projects any longer. You can switch forward and backward between VS2010 and VS2012.
BIG EDIT: We should wait until Microsoft announces the final decision, it's not clear yet, only conclusions.
But, I think that Microsoft won't drop support for XP and Vista that easy, it appears that the matter of decreasing support is just for speed-purposes to show it to the developers.
Also, if the it comes true and Microsoft Stopped the support for XP and Vista, then you have the virtual machine as an excellent choice!
Best wishes