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

MS build pair to mac optimization #22352

Open
Serge-N opened this issue May 12, 2024 · 3 comments
Open

MS build pair to mac optimization #22352

Serge-N opened this issue May 12, 2024 · 3 comments
Labels
area-tooling XAML & C# Hot Reload, XAML Editor, Live Visual Tree, Live Preview, Debugging proposal/open s/move-to-vs-feedback Tells automation to ask the person to use VS Feedback to report the issue

Comments

@Serge-N
Copy link

Serge-N commented May 12, 2024

Description

It would be faster to check if dotnet is already installed on that machine before downloading the SDK. In this case the sdk was already installed directly on the target machine.

image

Public API Changes

Check that the installed SDK matches the lastest.

Intended Use-Case

Improve developer experience.

@jsuarezruiz jsuarezruiz added the area-tooling XAML & C# Hot Reload, XAML Editor, Live Visual Tree, Live Preview, Debugging label May 13, 2024
@drasticactions drasticactions added the s/move-to-vs-feedback Tells automation to ask the person to use VS Feedback to report the issue label May 13, 2024
Copy link
Contributor

Thanks for the issue report @Serge-N! This issue appears to be a problem with Visual Studio, so we ask that you use the VS feedback tool to report the issue. That way it will get to the routed to the team that owns this experience in VS.

If you encounter a problem with Visual Studio, we want to know about it so that we can diagnose and fix it. By using the Report a Problem tool, you can collect detailed information about the problem, and send it to Microsoft with just a few button clicks.

  1. Go to the Visual Studio for Windows feedback tool or Visual Studio for Mac feedback tool to report the issue
  2. Close this bug, and consider adding a link to the VS Feedback issue so that others can follow its activity there.

Copy link
Contributor

Thanks for the issue report @Serge-N! This issue appears to be a problem with Visual Studio (Code), so we ask that you use the VS feedback tool to report the issue. That way it will get to the routed to the team that owns this experience in VS (Code).

If you encounter a problem with Visual Studio or the .NET MAUI VS Code Extension, we want to know about it so that we can diagnose and fix it. By using the Report a Problem tool, you can collect detailed information about the problem, and send it to Microsoft with just a few button clicks.

  1. Go to the Visual Studio for Windows feedback tool or .NET MAUI VS Code Extension repository to report the issue
  2. Close this bug, and consider adding a link to the VS Feedback issue so that others can follow its activity there.

@drasticactions
Copy link
Contributor

The MAUI UI Team does not maintain the Pair To Mac tooling, so it would be better to direct this to VS Feedback than here.

That said, I believe they specifically provision builds of dotnet that are siloed from the ones installed on your Mac, specifically so they won't conflict with ones installed on your system. Say you have a newer dotnet installed on Windows than on your Mac. If it installed globally on your Mac, that could introduce new issues on your Mac that you wouldn't know of until you went back and saw the version change. Matching the version of dotnet you are running on Windows and provisioning that specifically for Pair To Mac cuts down on those issues, albeit with the side effect of needing to download another dotnet build even if you have that installed.

So IMO, I think the current system is fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-tooling XAML & C# Hot Reload, XAML Editor, Live Visual Tree, Live Preview, Debugging proposal/open s/move-to-vs-feedback Tells automation to ask the person to use VS Feedback to report the issue
Projects
None yet
Development

No branches or pull requests

3 participants