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

Unable to launch Azure Functions locally in Rider 2024.3.2 + plugin v4.3.8 #989

Open
simonachmueller opened this issue Dec 17, 2024 · 3 comments
Labels
discussion Further information is requested

Comments

@simonachmueller
Copy link

Hi,

I'm facing an issue very similar to #881, but suggested workaround #944 (comment) doesn't work for me.

It can't load configurations in configuration editor
image

and displaying an error when I try to run any of the configurations:
image

Configuration looks like

<component name="ProjectRunConfigurationManager">
  <configuration default="false" name="--obfuscated--" type="AzureFunctionsHost" factoryName="Azure Functions host">
    <option name="EXE_PATH" value="$PROJECT_DIR$/src/--obfuscated--.dll" />
    <option name="PROGRAM_PARAMETERS" value="host start --pause-on-error" />
    <option name="WORKING_DIRECTORY" value="$PROJECT_DIR$/src/--obfuscated--/bin/Debug/net8.0" />
    <option name="PASS_PARENT_ENVS" value="1" />
    <option name="USE_EXTERNAL_CONSOLE" value="0" />
    <option name="USE_MONO" value="0" />
    <option name="RUNTIME_ARGUMENTS" value="" />
    <option name="PROJECT_PATH" value="$PROJECT_DIR$/src/--obfuscated--.csproj" />
    <option name="PROJECT_EXE_PATH_TRACKING" value="1" />
    <option name="PROJECT_ARGUMENTS_TRACKING" value="1" />
    <option name="PROJECT_WORKING_DIRECTORY_TRACKING" value="1" />
    <option name="PROJECT_KIND" value="RunnableProjectKind(name=AzureFunctions)" />
    <option name="PROJECT_TFM" value="net8.0" />
    <option name="FUNCTION_NAMES" value="--obfuscated--" />
    <browser url="http://localhost:7071" />
    <method v="2">
      <option name="BuildFunctionsProject" enabled="true" />
    </method>
  </configuration>
</component>

Any idea how to fix it?

@rafaelldi
Copy link
Collaborator

It looks like that you're using a run configuration from the v3 version of the plugin. Unfortunately, they are no longer supported in the v4 version. So, you could remove it and create a new one. Sorry for the inconvenience.

@rafaelldi rafaelldi added the discussion Further information is requested label Dec 18, 2024
@simonachmueller
Copy link
Author

@rafaelldi is there any tool to do it as migration? We have quite a few configuration files to fix.

@rafaelldi
Copy link
Collaborator

@simonachmueller No, unfortunately not

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants