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 RC1 #5271

Merged
merged 2 commits into from
Jul 20, 2021
Merged

Update to RC1 #5271

merged 2 commits into from
Jul 20, 2021

Conversation

RussKie
Copy link
Member

@RussKie RussKie commented Jul 19, 2021

/cc: @ryalanms

Microsoft Reviewers: Open in CodeFlow

@RussKie RussKie requested a review from dreddy-work July 19, 2021 04:58
@RussKie RussKie requested a review from a team as a code owner July 19, 2021 04:58
@ghost ghost assigned RussKie Jul 19, 2021
@dreddy-work
Copy link
Member

dreddy-work commented Jul 19, 2021

hmm. are the unused namespace removals indirect impact of bumping to rc1? assuming all the changes here are non-functional. I can't open them, too big :)

@RussKie
Copy link
Member Author

RussKie commented Jul 19, 2021

are the unused namespace removals indirect impact of bumping to rc1?

Yes, the result of dotnet/sdk#18459

@RussKie RussKie merged commit 81774ab into dotnet:main Jul 20, 2021
@ghost ghost added this to the 6.0 rc1 milestone Jul 20, 2021
@RussKie RussKie deleted the bump_to_rc1 branch July 20, 2021 23:13
@kirsan31
Copy link
Contributor

kirsan31 commented Jul 21, 2021

@RussKie after this commit, build with VS2019 is not working (lots of errors). .\build.cmd seems to work.
Last working in VS commit is 54c7297

P.S.
Any side Net6 WinForms project also not build with this SDK 6.0.0-rc.1.21369.7 (with 6.0.0-preview.7.21370.10 too) with very strange erors:
image

@RussKie
Copy link
Member Author

RussKie commented Jul 21, 2021

What VS version? What .NET versions do you have installed?

@kirsan31
Copy link
Contributor

hat VS version?

16.10.4. The only remaining after experiments with VS2022. P.s. I am still fixing the lost settings in stable 2019 after this...

What .NET versions do you have installed?

For now:

  2.1.816 [C:\Program Files\dotnet\sdk]
  5.0.202 [C:\Program Files\dotnet\sdk]
  5.0.204 [C:\Program Files\dotnet\sdk]
  5.0.302 [C:\Program Files\dotnet\sdk]
  6.0.100-preview.6.21355.2 [C:\Program Files\dotnet\sdk]

Was trying SDK 6.0.0-rc.1.21369.7 and 6.0.0-preview.7.21370.10.
I am understand that problems with c#10. Apparently 16.10 can't handle it even with <LangVersion>preview</LangVersion>.

@RussKie
Copy link
Member Author

RussKie commented Jul 22, 2021

I am understand that problems with c#10. Apparently 16.10 can't handle it even with <LangVersion>preview</LangVersion>.

Yes, you need to have .NET 6.0 P7+ (?) and the latest VS.

@kirsan31
Copy link
Contributor

Yea thanks. I am done with experiments on VS2022 for a while. Perhaps I will try on 11.16p. when I clear up the consequences of 2022 installing...

@RussKie
Copy link
Member Author

RussKie commented Jul 22, 2021 via email

@kirsan31
Copy link
Contributor

Have you found any specific issues in VS 2022 that stop you from using it?

Yes:

  1. I was not able transfer my settings from VS2019. Export from VS2019 and Import to 2022 wasn't help and there were some errors during import.
  2. Possibility to align minimized MDI child to default location (TOP LEFT) #5221 (comment). But I was not trying .Net5 projects.
  3. I don't like New ikons and color scheme. I am using 2017 Blue scheme through extention (that need to be updated to 2022).
  4. Other extensions that need to be updated.

@ghost ghost locked as resolved and limited conversation to collaborators Jan 27, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants