-
Jul 13th, 2021, 02:43 PM
#1
Thread Starter
Hyperactive Member
[RESOLVED] Upgrading Framework 4.8 to 5.0 -- x64 or x86 version?
I would like to upgrade from the Framework 4.8 to 5.0 and would like to know how to find out which platform I should download (32-bit or 64-bit).
I have a Windows 10 Pro O/S (64-bit). I am running Visual Studio Community 2019 version 16.9.4.
I thought this information would be shown in the Help menu ("About Visual Studio") but the Framework platform is not included there.
-
Jul 13th, 2021, 02:51 PM
#2
Re: Upgrading Framework 4.8 to 5.0 -- x64 or x86 version?
You'd want the 64 bit Visual Studio. Whether you want to target 32 bit, 64 bit, or somewhere in between should be an option that you can set for each project.
My usual boring signature: Nothing
-
Jul 13th, 2021, 02:52 PM
#3
Thread Starter
Hyperactive Member
Re: Upgrading Framework 4.8 to 5.0 -- x64 or x86 version?
@Shaggy -
Originally Posted by Shaggy Hiker
You'd want the 64 bit Visual Studio.
Do you mean the 64-bit version of the Framework?
https://dotnet.microsoft.com/download
-
Jul 13th, 2021, 02:55 PM
#4
Thread Starter
Hyperactive Member
Re: Upgrading Framework 4.8 to 5.0 -- x64 or x86 version?
I can see where I'm getting confused. The link in my post #3 shows .Net 5.0 and Framework 4.8. I don't think there is a more recent version of the Framework other than v4.8.
-
Jul 13th, 2021, 02:56 PM
#5
Re: Upgrading Framework 4.8 to 5.0 -- x64 or x86 version?
No, I didn't. I meant the 64-bit version of Visual Studio. I'm not sure that you get a choice as to which version of the framework you have, as that will be part of the OS. You get a choice of which bitness you target, but I've never seen any choice for which bitness you happen to have.
My usual boring signature: Nothing
-
Jul 13th, 2021, 02:58 PM
#6
Thread Starter
Hyperactive Member
Re: Upgrading Framework 4.8 to 5.0 -- x64 or x86 version?
-
Jul 13th, 2021, 03:23 PM
#7
Re: [RESOLVED] Upgrading Framework 4.8 to 5.0 -- x64 or x86 version?
The first 64 bit version of Visual Studio is 2022 and it is still in early preview. Bits are not important as Visual Studio (I assume 2019 as latest stable release and still runs as 32-bit app itself) can create apps that can run as 32 or 64 bits or whatever is available (AnyCPU).
The bigger problem is that .NET Framework 4.8 is the last framework version. .NET 5 is based on .NET Core and that confusion put many people in troubles selecting the proper version. So it is not just to change the version in project properties from 4.8 to 5.0. It will be required some work to create the new .NET Core style project files.
There are some other specific differences between .NET Framework and Core projects and libraries but nothing so special that cannot be fixed with some refactoring of code.
-
Jul 13th, 2021, 04:06 PM
#8
Thread Starter
Hyperactive Member
Re: [RESOLVED] Upgrading Framework 4.8 to 5.0 -- x64 or x86 version?
@peter -
that confusion put many people in troubles selecting the proper version
Yes sir...
Thanks for your input!
-
Jul 13th, 2021, 04:50 PM
#9
Addicted Member
Re: [RESOLVED] Upgrading Framework 4.8 to 5.0 -- x64 or x86 version?
It depends a lot on the criteria you want to bring a friend, taking into account your code and project selections if it was made for 32 or 64 then upgrade to 64x VS 2019 and 64x .net then you can choose whether you want to compile your project to 32 bits or 64 bits now if you want to focus on disk space use VS2019 in 32bit and dot net too, but this will slow you down as it will have to be simulated by the Windows SysWow system, making everything slower and consuming more momoria.
Well seeing all this I recommend using the 64x version of both. and if possible control the ram consumption of visual studio.
and make some improvements to your computer if necessary, but since we're talking about software my advice is: Use 64x
-
Jul 13th, 2021, 04:58 PM
#10
Thread Starter
Hyperactive Member
Re: [RESOLVED] Upgrading Framework 4.8 to 5.0 -- x64 or x86 version?
@Liwis -
Do you know if MS has published a "FAQ" or tip sheet for end-users that discusses how to go about the upgrade process?
Thanks for your input!
-
Jul 13th, 2021, 06:48 PM
#11
Addicted Member
Re: [RESOLVED] Upgrading Framework 4.8 to 5.0 -- x64 or x86 version?
Originally Posted by Mark@SF
@Liwis -
Do you know if MS has published a "FAQ" or tip sheet for end-users that discusses how to go about the upgrade process?
Thanks for your input!
I don't know any faq or article but you can see the program requirements and always make comparisons and look up the performance of the program on old and new hardware and find the best version. in addition to searching in forums.
Now about updates I don't know from microsoft but I did it as follows:
1) I copied my projects in the folder C:\Users\%user%\source\repos
2) saved to a desktop folder but can also save to cloud, pendrive cd or dvd, any save media.
3) I uninstalled visual studio through unistaller.
3) I installed the new version of the visual studio 2019 installer.
4) I installed it selecting what I wanted (desktop development,vb,c#,f#,c++)
5) then I created a project with the name of my old project.
6) copied the file. slin of the new project.
7) I pasted the new slin with the project name in the old folder of my project, now it has the id of VS2019 and can be compiled as such.
8) I clicked on the slin project from vs2019 and that's it it opens my old files, as if they were from the new visual studio 2019 and when I compile it says it's from vs2019 with no errors.
-
Jul 13th, 2021, 06:57 PM
#12
Re: [RESOLVED] Upgrading Framework 4.8 to 5.0 -- x64 or x86 version?
There are some things that are not 64-bit, and never will be. For example, if you work with the JET database engine, that is 32-bit and won't be updated. In the past, MS didn't handle these as well as might be hoped. If you developed for AnyCPU, and were on a 64-bit system, your program would look for the 64-bit version of JET, which doesn't exist, so it would just fail.
I'm also not sure that there is ANY performance loss to using 32-bit over 64-bit. 64-bit allows you to directly address a much larger memory space, but very few programs need that.
My usual boring signature: Nothing
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|