Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NET 8 Upgrade #687

Merged
merged 18 commits into from
Nov 21, 2023
Merged

NET 8 Upgrade #687

merged 18 commits into from
Nov 21, 2023

Conversation

BenjaminZehowlt
Copy link
Contributor

@BenjaminZehowlt BenjaminZehowlt commented Nov 14, 2023

This is a very early implementation of upgrading VRCX to .NET 8 from .NET Framework 4.7.2.

@Myrkie
Copy link
Contributor

Myrkie commented Nov 14, 2023

natsumi is going to kill you.

@DubyaDude
Copy link
Member

DubyaDude commented Nov 14, 2023

Not sure if this is something to pursue when there's the winter rewrite project that plans to utilize NET 8.

also, Switching from framework -> net will also cause issues of people not having runtime installed if you don't to a self-contained build.

@BenjaminZehowlt
Copy link
Contributor Author

Not sure if this is something to pursue when there's the winter rewrite project that plans to utilize NET 8.

also, Switching from framework -> net will also cause issues of people not having runtime installed if you don't to a self-contained build.

The first part is fair, and the second one I see the concern, but Windows will prompt you to install the runtime.

@Myrkie
Copy link
Contributor

Myrkie commented Nov 14, 2023

Not sure if this is something to pursue when there's the winter rewrite project that plans to utilize NET 8.
also, Switching from framework -> net will also cause issues of people not having runtime installed if you don't to a self-contained build.

The first part is fair, and the second one I see the concern, but Windows will prompt you to install the runtime.

can confirm the second part, I was sent a test build without .net 8 installed and it brought me straight to the direct download, no fussing around on a page to find the correct one.

@DubyaDude
Copy link
Member

Not sure if this is something to pursue when there's the winter rewrite project that plans to utilize NET 8.
also, Switching from framework -> net will also cause issues of people not having runtime installed if you don't to a self-contained build.

The first part is fair, and the second one I see the concern, but Windows will prompt you to install the runtime.

Didn't know that, neat

@BenjaminZehowlt
Copy link
Contributor Author

We could always modify the installer to bundle .NET 8 if it is an issue.

@DubyaDude
Copy link
Member

Well, putting that aside, I don't think it's great to switch core tech as the rewrite is over the horizon (I took 3 weeks off in December purely for it, so progress will definitely be made by the end of the year).

The last thing I want is for a slew of new issues possibly popping up from this.

@BenjaminZehowlt
Copy link
Contributor Author

Well, putting that aside, I don't think it's great to switch core tech as the rewrite is over the horizon (I took 3 weeks off in December purely for it, so progress will definitely be made by the end of the year).

The last thing I want is for a slew of new issues possibly popping up from this.

We can always keep it on hold and see how far along we are in mid-December as there's no guarantee it'll be nowhere near ready by then.

Plus it's not even merge-ready as there are some issues I have to resolve.

@DubyaDude
Copy link
Member

LGTM, ship it to prod

@BenjaminZehowlt BenjaminZehowlt marked this pull request as ready for review November 20, 2023 21:56
@Natsumi-sama Natsumi-sama merged commit 2e9db31 into vrcx-team:master Nov 21, 2023
1 check passed
Natsumi-sama added a commit to Natsumi-sama/VRCX that referenced this pull request Nov 21, 2023
* Initial .NET8 Upgrade

* Initial GitHub Actions Cleanup

* Fix Desktop Notifications

* Fix throw warning

* Upgrade vunerable transative nuget packages

* Fix warnings with registry overflow

* Adjust async/await usage for configRepository

* Fix TTS voice name and app auto start

* Install .NET 8 with setup

I regret NSIS

* Remove no longer needed System/MS references (included in dotnet sdk)

* Surpress stackalloc in loop warning, that code scares me.

* Removed unused SharpDX packages

* Ignore WebClient warning, hopefully this project doesn't move past NET 8

* Fixed terrifying code

* GenerateAssemblyInfo

* Trimmed editor config to only silence warning.

* Fix open webpage

* Fix updater

---------

Co-authored-by: DubyaDude <ushafiq141@gmail.com>
Co-authored-by: Natsumi <cmcooper123@hotmail.com>
@Okabintaro
Copy link

Hello, just a heads up. I installed the latest nightly with this upgrade and got this on Windows 10:

image

Clicking on the link and installing the runtime doesn't fix the issue though. It keeps re asking to install it.
I also tried to install the SDK for .NET 8 but no change.

@Myrkie
Copy link
Contributor

Myrkie commented Nov 21, 2023

Hello, just a heads up. I installed the latest nightly with this upgrade and got this on Windows 10:

image

Clicking on the link and installing the runtime doesn't fix the issue though. It keeps re asking to install it. I also tried to install the SDK for .NET 8 but no change.

make sure to download the .net Desktop Runtime

https://dotnet.microsoft.com/en-us/download/dotnet/8.0

Direct: desktop runtime

@Natsumi-sama
Copy link
Member

Did you install with setup or zip? what's your Windows version? try reboot.

@Okabintaro
Copy link

make sure to download the .net Desktop Runtime

I did, that's the same thing that got linked by the dialog. Now that setup only offers me to modify or repair the install which I tried.

Did you install with setup or zip? what's your Windows version? try reboot.

Originally I used the automatic Nightly upgrade, but now also tried the zip file from commit 312519b with the same issue.

The windows version is Windows 10 Pro 22H2:
image

Tried rebooting multiple times, but the issue persists. Also tried running it from the cmd but it just pops up that window instantly.
Not sure how I could provide additional info.

@DubyaDude
Copy link
Member

DubyaDude commented Nov 21, 2023

Might be better to make this an issue rather than have it in this PR since it is now on nightly.
We'll be able to give proper support once it's in an issue.

@BenjaminZehowlt BenjaminZehowlt deleted the net8-upgrade branch November 22, 2023 02:32
@DubyaDude
Copy link
Member

@Okabintaro please create an issue for this including all the information so we can diagnose and track it. I may have a potential fix, but would rather continue that discussion on an issue.
https://github.com/vrcx-team/VRCX/issues/new/choose

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants