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
I'm not entirely sure if this is a bug, but even if it isn't, this isn't ideal behavior: App.LastBuildPath is reset to blank after you've run from the IDE. IMHO, running from the IDE should not count as a build for the purposes of 'Last Build Path'-- the principal utility of this property, as I see it, is to query the last exe. If the intention was to be able to infer the last run being from the IDE from it being blank, perhaps an additional variable is in order, or a flag.
The text was updated successfully, but these errors were encountered:
I'm not seeing this behaviour. From the looks of it, the only time it would get reset to blank is if the compiler gets restarted (either manually, or automatically upon a hard crash).
Usually have to restart the compiler to be able to build after running it from the IDE. With the ribbon project it's been 100%; run or compile, won't run or compile again until manual compiler restart (either generic build failed or 'can't find form1'). Or editing it for a while. But I'd argue that scenario is even less appropriate for clearing it.
I'm not entirely sure if this is a bug, but even if it isn't, this isn't ideal behavior:
App.LastBuildPath
is reset to blank after you've run from the IDE. IMHO, running from the IDE should not count as a build for the purposes of 'Last Build Path'-- the principal utility of this property, as I see it, is to query the last exe. If the intention was to be able to infer the last run being from the IDE from it being blank, perhaps an additional variable is in order, or a flag.The text was updated successfully, but these errors were encountered: