Matthew Endsley
Matthew Endsley
Looks like this is the main culprit https://github.com/premake/premake-core/blob/d842e671c7bc7e09f2eeaafd199fd01e48b87ee7/modules/vstudio/vs2005_dotnetbase.lua#L236-L242 I'm guessing that should be looping over each configuration and adding the configuration's condition with something like: `p.push('', dotnetbase.condition(cfg))`
It looks like the CI workflow failed due to a network issue. Is there a way to re-run it? https://github.com/premake/premake-core/actions/runs/9273887065/job/25514966115?pr=2215
Hi @nickclark2016! I guess I was under the assumption this only affected C# project file generation. What did you have in mind for the C++ side?
Just checking back in to see if there is anything remaining to be actioned on this
Does the icon stay there if YNAB is refreshed/reloaded? (trying to figure out if it's an update thing, or a general account state issue)
My current guess is I'm accidentally picking up an imported transaction that was rejected. Investigating if that's something I can reproduce