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
Editing of the IAR-project seetings still needs to be done from the IAR-Workbench. It would be nice to support the editing of the *.eww configuration within Visual Studio, thus reducing the needed switch between both tools.
The text was updated successfully, but these errors were encountered:
Any chance we could eventually have "common" parts of the configuration (to edit independent of Debug/Release) to simplify setting up Debug/Release/Bootloader builds, and easier file overrides in the future?
Maybe it could be easiest (for IAR devs) to trial a new alternate xml project file format, maybe with its own file extension?
We are increasingly doing things in various projects (with tools from other vendors) that we can't do with our IAR project files.
Any chance we could eventually have "common" parts of the configuration (to edit independent of Debug/Release) to simplify setting up Debug/Release/Bootloader builds, and easier file overrides in the future? Maybe it could be easiest (for IAR devs) to trial a new alternate xml project file format, maybe with its own file extension?
We are increasingly doing things in various projects (with tools from other vendors) that we can't do with our IAR project files.
Work is going on to improve project option handling in the IAR Embedded Workbench IDE and in the future, the plan is to open up for option settings also from VSCode. The project file format will remain common so that you can move between the two environments.
Editing of the IAR-project seetings still needs to be done from the IAR-Workbench. It would be nice to support the editing of the *.eww configuration within Visual Studio, thus reducing the needed switch between both tools.
The text was updated successfully, but these errors were encountered: