Problem with relative path #1461

File.Exists("Logo/C_agora-new-logo-200x200.png") returns False because relative paths resolve against the current working directory, not against your project folder. When you run from Visual Studio the working directory is the build output folder — BddPDF\bin\Debug\net10.0\ — and Logo\ was never copied there.

Add these two lines above your check to see it:

Debug.WriteLine($"CWD:  {Environment.CurrentDirectory}");
Debug.WriteLine($"Base: {AppContext.BaseDirectory}");

Both point into bin\Debug\..., and that is where File.Exists is looking. The tutorial's Assets/logo.png works because it is configured to be copied to the output; yours is currently only sitting in the project directory.

1. Make the file land in the output folder

In BddPDF.csproj:

<ItemGroup>
  <None Update="Logo\C_agora-new-logo-200x200.png">
    <CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
  </None>
</ItemGroup>

Or in Solution Explorer: select the file, press Alt+Enter, set Copy to Output Directory to Copy if newer (in a French VS: Copier dans le répertoire de sortie → Copier si plus récent).

After a rebuild, bin\Debug\net10.0\Logo\C_agora-new-logo-200x200.png will exist.

2. Anchor the path to the assembly rather than the working directory

string imagePath = Path.Combine(AppContext.BaseDirectory, "Logo", "C_agora-new-logo-200x200.png");

AppContext.BaseDirectory is documented as the containing directory of the host executable, so it stays correct even when the working directory is something else — which happens as soon as the app is started from a shortcut, a scheduled task, a service or IIS. Environment.CurrentDirectory gives no such guarantee.

Step 1 alone makes it work today; step 2 keeps it working.

About the net10.0-windows you saw

That came from the commented-out Assembly.GetExecutingAssembly() line. If TargetFramework is net10.0-windows the output goes to bin\Debug\net10.0-windows\; if it is plain net10.0 it goes to bin\Debug\net10.0\. Don't assemble that string by hand — AppContext.BaseDirectory returns the real path either way.

If you'd rather not ship a loose file next to the executable, the other option is Build Action Embedded Resource and loading it as a stream, but the two steps above are the straightforward fix.