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

Update to Visual Studio 2019+ #165

Open
Ed-Price opened this issue Oct 2, 2020 · 2 comments
Open

Update to Visual Studio 2019+ #165

Ed-Price opened this issue Oct 2, 2020 · 2 comments
Assignees
Labels
pri/2 Priority 2 - Should be done for current release, but it isn't as critical

Comments

@Ed-Price
Copy link
Member

Ed-Price commented Oct 2, 2020

We need to change project dependencies in order to be compatible with VS2019. Currently we have to install/use VS2017, which slows down the development onboarding and process. (VS2017 is supported through April 2027.)

Blazor has some dependencies. We're using an incompatible set of components and are facing an error when compiling with VS 2019.

ERROR:

7>------ Build started: Project: SmallBasic.Editor, Configuration: Debug Any CPU ------

7>C:....nuget\packages\microsoft.aspnetcore.blazor.build\0.7.0\targets\RazorCompilation.targets(236,5): error : rzc discover exited with code 1.

@Ed-Price Ed-Price added the pri/2 Priority 2 - Should be done for current release, but it isn't as critical label Oct 2, 2020
@kmelmon kmelmon self-assigned this Oct 27, 2020
@kmelmon
Copy link
Contributor

kmelmon commented Oct 27, 2020

Converting will likely require upgrading to latest version of Blazor. Daniel Roth says:

"This project is on a really old version of Blazor from back when Blazor was still experimental. There have been a lot of changes since 0.7.0.

For experimental & preview releases we publish upgrade guidance as part of the Blazor release announcement blog posts. So you’d have to go back and find all of the posts starting with 0.7.0 to the latest. There been probably a dozen or so releases since 0.7.0, so that’s probably not worth it.

An alternative approach is to start with a new Blazor WebAssembly 3.2 project and restructure your app to match. That’s probably what I would do."

@kmelmon
Copy link
Contributor

kmelmon commented Oct 28, 2020

Daniel Roth followed up with this comment:

"Instead of starting with Blazor WebAssembly 3.2, I actually think you should go ahead and start working with Blazor WebAssembly in .NET 5 RC2. .NET 5 will release in about two weeks, and the RC2 bits are really close to the final version."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pri/2 Priority 2 - Should be done for current release, but it isn't as critical
Projects
None yet
Development

No branches or pull requests

2 participants