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 Core Tools to detect unsupported in-proc workloads #3816

Closed
fabiocav opened this issue Sep 6, 2024 · 2 comments · Fixed by #3825
Closed

Update Core Tools to detect unsupported in-proc workloads #3816

fabiocav opened this issue Sep 6, 2024 · 2 comments · Fixed by #3825
Assignees

Comments

@fabiocav
Copy link
Member

fabiocav commented Sep 6, 2024

The Core Tools version using the OOP host should be updated to detect unsupported in-proc scenarios and provide information about the required SDK version (recommend update to latest) if that is triggered.

@mattchenderson
Copy link
Contributor

This work should follow Azure/azure-functions-vs-build-sdk#657

@surgupta-msft surgupta-msft self-assigned this Sep 6, 2024
@mattchenderson
Copy link
Contributor

Specifically, this should be for the versions distributed to VS which are used by the isolated worker model as well. This change should not be present in the versions that are in-proc only. It is also not needed for scenarios in which the Core Tools is to be run via the command line or in Visual Studio Code, for example. In those cases, we can use the standard probing logic and launch the right version as a new process.

The message should include a short link which will be updated to point at the documentation tracked by #3817. Proposed: https://aka.ms/functions-core-tools-in-proc-sdk-requirement

This detection could be introduced into the current Core Tools structure, and it likely should be from a release tactics perspective. We will need to make sure it is preserved going into the new structure (#3744), though.

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

Successfully merging a pull request may close this issue.

3 participants