launchSettings no longer working in 2024 and above

Hello Tlarson,

Would it be possible to share the affected solution (or a sample solution with a similar project structure) so we could look into this further?

If you cannot share the entire project, could you share some solution files with us so we could investigate this further? Specifically, could you share with us your:

• .slnx
• .csproj
• launchSettings.json

• If you are using any manually created Run Configurations, please share those using Store as project file checkbox in the Run configuration dialog 

  

You can share this information with us privately via the Upload Service and let me know the Upload ID in this thread.

Hi Kirill, 

here is the upload ID: 

Upload id: 

2025_08_11_qJfRK7TsYLAHsmRApiKxDE

 (files: launchSettings.json and 2 more)

Hello Tlarson,

Thank you for the information. Regrettably, I was not able to reproduce this behavior in a testing environment using a similar project structure and launchSettings.

Could you try clearing IDE-specific settings to regenerate run configurations for this solution in Rider and let me know if the issue persists? Please follow the steps below:

• Close your solution in Rider
• Navigate to the solution directory and remove (or rename if you want to keep a backup for any reason) .idea directory
• Reopen the solution in Rider

If the issue is still reproducible, could you share the .csproj of AppServerApi? This might help us identify what causes this behavior.

Here's the csproj for AppServerApi. 
Upload id: 2025_08_13_mzU1Mk8HpsniphzaxCKgMx (file: AppServerApi.csproj)

Here's the deps.json
Upload id: 2025_08_13_bxpwQ9TZMx2MxjXtDNLUsW (file: AppServerApi.deps.json)

Deleting the .idea folder did not solve the issue for me.

As noted above the issue points to the presence of an AppServerApi.dll and an AppServerAPi.exe.

Here's the exact text of the error:
Error:
 An assembly specified in the application dependencies manifest (Tcp.AppServerApi.deps.json) has already been found but with a different file extension:
   package: 'Tcp.AppServerApi', version: '1.0.0'
   path: 'Tcp.AppServerApi.dll'
   previously found assembly: 'D:\Work\core\tcp-we-71\server\Src\Interface\AppServerApi\bin\Debug\net8.0\Tcp.AppServerApi.exe'
One or more errors occurred. (Started a process for debugging, but it has exited before any CLR were loaded into that process.)
 

Hello Tlarson,

Unfortunately, the project files so far do not point to a clear issue in Rider, and this behavior is still not reproducible with similar launch settings profiles. Is there a chance that one of the projects in your solution somehow runs the equivalent of the following launch configuration? 

      "commandName": "Executable",
      "executablePath": "dotnet",
      "commandLineArgs": "{...}Tcp.AppServerApi.exe",

No, this is the standard launch settings that get “templated” out for each new class library project. 

For clarity, this issue only arises when selecting the “Debug” option and only for the Core profile, running the Core profile in the Release configuration works just fine but I cannot debug. The Admin profile runs just fine in all scenarios and is agnostic to Rider versions and Release or Debug configurations. 

Is there any other information that may help? My current workaround is to use a 2023 ver. of Rider and open the individual .csproj's to avoid the .slnx incompatibility, but atleast I am able to debug by giving a fully qualified path to the .exe. 

{
  "profiles": {
    "Core": {
      "commandName": "Executable",
      "executablePath": "$(SolutionDir)..\\..\\..\\core\\tcp-we-71\\server\\Src\\Interface\\AppServerApi\\bin\\Debug\\net8.0\\Tcp.AppServerApi.exe",
      "commandLineArgs": "../../../../cfg .",
      "workingDirectory": "$(SolutionDir)..\\..\\..\\core\\tcp-we-71\\server\\Src\\Interface\\AppServerApi\\bin\\Debug\\net8.0"
    },
    "Admin": {
      "commandName": "Executable",
      "executablePath": "$(SolutionDir)..\\..\\..\\core\\tcp-we-71\\server\\Src\\Interface\\AdmServerApi\\bin\\Debug\\Tcp.AdmServerApi.exe",
      "commandLineArgs": "../../../cfg .",
      "workingDirectory": "$(SolutionDir)..\\..\\..\\core\\tcp-we-71\\server\\Src\\Interface\\AdmServerApi\\bin\\Debug"
    }
  }
}

Tlarson, would it be possible to create a sample project affected by the same issue (but without any sensitive information) in your environment and share it with us?