I have noticed that if I open a completely new work space estudio remembers that a sample project has been imported earlier and denies an import in the new fresh workspace.
That is not handy for upgrades which require the latest estudio and sdk like the current upgrade.
How is that issue be best addressed, a new SDK location for each independent project ?
Thanks
Ralph
update
It seems that this issue affects all sample projects even those I have not imported before.
I will try on a virgin machine to see if I can import according to the documentation.
Even when I completely uninstall estudio, delete all work spaces and reinstall estudio this problem remains
Let us know what kind of path is given as workspace.You could also try using "Existing Projects into Workspace" but uncheck "copy projects into workspace", or use "Projects from Folder or Archive".
I assumed this before as I was using a workspace in programdata path which might create permission issues, however I am as administrator on the machine. However, I then selected a workspace in my user path here C:\Users\ralph\e2_studio\waterwatch_I . I tried various workspace names.
to make it clear:
starting e-studio
creating a NEW AND EMPTY workspace
importing >General>Dialog SDK project
selecting ANY sample project
gives this result
please read the whole threat if you feel like answering
and you should know that importing "Existing Projects into Workspace" does NOT WORK. It has a bunch of unresolved identifiers as ALREADY MENTIONED EARLIER IN THIS THREAT
May be you come up with something that helps, I need a solution to follow the recommendation to always use the latest versions. I just starting a new project, so yes it would make sense to use the latest