First Time After Clone The Project, Cannot Run

[dhik-4]

Hello all...
I have clone this project. then i open the file Ocelot.sln with visual studio 2022

currently startup project is Ocelot.Testing. when i try to debug, i got popup error

then i ask the chatgpt, got advise to set another startup project that executeable. i try set startup project to Ocelot.ManualTest

when i try to debug, i get exception in Program.cs

i have read the readme.md, then i install the Ocelot nuget. but still not solving.

is there anyone can give me advise ?

[raman-m]

Hello, Dhika!

I have clone this project. then i open the file Ocelot.sln with visual studio 2019

You must open solutions in Visual Studio 2022 or 2026, since the 2019 edition is outdated. It might not support the latest TFMs (SDKs 8, 9, 10).
So, don't use Visual Studio 2019, and install Visual Studio 2026, which supports .NET 10 and the new solution .slnx format.

then i ask the chatgpt, got advise to set another startup project that executeable. i try set startup project to Ocelot.ManualTest

Actually, the startup project should be Ocelot! 😄

Good luck!

[dhik-4]

Oh sorry..

My VS currently version 2022. Not 2019

[raman-m]

Upgrade to VS 2026 and enjoy the full capabilities of the .NET 10 SDK. What are you waiting for?
Upgrading to VS 2026 takes 15-20 minutes if internet bandwidth is good. .NET 10 is a major long-term support (LTS) version, the next version after LTS .NET 8. It's time to upgrade everything: SDK, IDE, tools, etc.

FYI, I will remove the old solution files, aka .sln, after the official Ocelot release of .NET 10 milestone. To be honest, I don't want to maintain the old solution format. There's no point in keeping them since we now have the new .slnx format for SDK 10.

For cross-platform, cross-OS development on Linux or macOS, other IDEs such as JetBrains Rider or Visual Studio Code are able to open .sln(x) files. Thus, for example, Visual Studio Code on Ubuntu OS just works fine.

Wish you wonderful adventures with Ocelot. 🐈‍⬛

[dhik-4]

i already upgrade the VS to 2026.
and also set the startup project to Ocelot.

but still get this popup error when start to debug

[raman-m]

You can't just debug a library! In theory, it is possible, but the approach is a cumbersome one for senior developers (need to attach a symbol file containing debug symbols, need to run a process in debug mode, then attach the process in Visual Studio). This is quite a complicated approach that is not for junior developers. It is better to debug a web app!

Sorry for the confusion about making Ocelot start up — so it must be a web app, aka Ocelot.ManualTest.

The projects being debugged are web apps, which are ASP.NET Core applications. Ocelot is a library that should be referenced from a web application.
We have two solutions, and the best one is Ocelot.Samples.slnx, so I recommend opening it and debugging any sample.

So, projects being debugged in the Ocelot.slnx solution:

• Ocelot.ManualTest

But this project is not ready for presentations, since it should be used by experienced developers to debug and develop customizations to the Ocelot project. I recommend switching to the Ocelot.Samples.slnx solution and debugging the Basic sample app.

[dhik-4]

owh...

so it means, i must open directly to Ocelot.slnx (file number 2),

or rename the file number 1 to another name, then rename file number 2 into .sln file (delete the x ) ?