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
As it is now the deployment does it's thing and reports back the success of deploying the assembly(es) to the target device.
If there is a mismatch on any of the assembly(es) version (or not being available at all) the execution is not possible and the developer has no clue about the reason for the app not executing or the debug session not starting.
This is not good at all and doesn't provide a good user experience.
The deployment has to have means of checking for the availability of the required assembly(es) and provide a clear and helpful message when those conditions aren't meet.
The text was updated successfully, but these errors were encountered:
- Update WPF test app to use the new command
- Enable the build of the test app projects
- Addresses nanoframework/Home#329
Signed-off-by: josesimoes <jose.simoes@eclo.solutions>
As it is now the deployment does it's thing and reports back the success of deploying the assembly(es) to the target device.
If there is a mismatch on any of the assembly(es) version (or not being available at all) the execution is not possible and the developer has no clue about the reason for the app not executing or the debug session not starting.
This is not good at all and doesn't provide a good user experience.
The deployment has to have means of checking for the availability of the required assembly(es) and provide a clear and helpful message when those conditions aren't meet.
The text was updated successfully, but these errors were encountered: