You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
dotnet run issue is still present but doing dotnet run --project solves the issue. I have reached out to some people to understand why the "default" gesture isn't working.
Ok, it finds both the sln and the csproj. Normally they are never in the same folder, so this makes sense. I tested by removing the sln file, and then it works.
So I'll move the sln to one level up, and use that for both csprojs, for use with VS. Then people can test using simple dotnet run inside each folder
Trying to run the dll directly:
![image](https://private-user-images.githubusercontent.com/203432/328140699-ec4e2881-a174-48bc-83f5-f8525627be62.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjI5MzU1MjYsIm5iZiI6MTcyMjkzNTIyNiwicGF0aCI6Ii8yMDM0MzIvMzI4MTQwNjk5LWVjNGUyODgxLWExNzQtNDhiYy04M2Y1LWY4NTI1NjI3YmU2Mi5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwODA2JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDgwNlQwOTA3MDZaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1jMGEzMWFkNzc0MzdkNDQzMjZkMGM2NTBjYTU5NGNiMzJkMDVkMDAyMWQ0MWVmMDYxNTlkZWY0NzM5ZWFhOTY2JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.-LM_VOjQF6mjP3FkFKYaf2arb9rdg_NvrYXvNhRJ7_s)
using
![image](https://private-user-images.githubusercontent.com/203432/328139374-45889a2e-d82d-482f-aede-1ef069f6a75b.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjI5MzU1MjYsIm5iZiI6MTcyMjkzNTIyNiwicGF0aCI6Ii8yMDM0MzIvMzI4MTM5Mzc0LTQ1ODg5YTJlLWQ4MmQtNDgyZi1hZWRlLTFlZjA2OWY2YTc1Yi5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwODA2JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDgwNlQwOTA3MDZaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT03MDU5Y2FkMGEwMmQzNzdiYmUxN2FhNDFmMGZhZGZhZmVhNmEzMmIxNmJkOTA3MGE5MTVjOWU5OTBkYWY1MWQ3JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.zRrz7elIim1VRa_V4qRF94dUs-Lukj4wCYyKODZAOK4)
dotnet run
I believe these two have the same root cause, but the message from the latter may be misleading.
The text was updated successfully, but these errors were encountered: