Add VS4Mac/macOS pivot to MAUI-Blazor tutorial#27678
Conversation
The current text seems fine.
The note and its location look reasonable to me.
Sounds like something we should follow up on, but it doesn't block this doc. Can you create a VS feedback issue for this and share the link with us?
These are problems with the Windows Forms experience, right? I'll follow up with you on these separately. |
Yes, the screenshots for those two are in that email that you responded to yesterday. The subject line is "Almost there on Blazor docs 7.0 coverage". It's the first message of that chain.
Yes. Will do. 👍
I'll get back to you in a few hours on that, too. |
|
@danroth27 ...
Should I go ahead and publish this now? WRT the two reports that I need to generate for the WinForms-Blazor app (Dock > Fill and
|
Addresses #26364
Internal Review Topic
This is in pretty much 🦖 Rex Pea-brain Dump™ 🦖 state due to the speed that I cranked it out this morning 🏃♂️. It's a bit rough, but I think it's ok to take feedback on it in this state given that I'm about out of 🕦 this week. I'll try to address feedback today (Friday) if it arrives. I'll review/edit/polish on Monday morning either way.
Check the pivot selector prompt text ("Choose a Visual Studio operating system",
aspnetcore/zone-pivot-groups.yml) to see what you want that to say.I placed an IMPORTANT note about the IDE install order and what to do if it's accidentally performed in reverse. I did it in reverse by mistake 🙈 and hit the MIA SDK error, so I'd like to head off doc repo issues by leaving this guidance in here somewhere. It could go at the end with a cross-link from the top or in the MAUI tutorial overview topic with a cross-link from the top ... or where I have it now on the PR.
I had a warning here about the Java SDK, but it didn't affect this scenario. I haven't researched it, so idk what's what with it.
WRT the WinOS pivot: I sent the remarks about the WinOS problems in the offline chat. I think that the Dock > Fill problem was present back in the 6.0 release, too. The component reference problem goes away after the app is built the first time.