Is there some way to get the last working Eclipse plug-in back ?

I'd like to be able to do work with Eclipse as I figure out how to use VS Code (tried working with multiple projects yet in VS Code???).

I understand that Eclipse is no longer supported, but is there a way to get the last plug-in back ?

Doing an update in Eclipse removed the ConnectIQ plug-in.

  • tried working with multiple projects yet in VS Code???

    https://code.visualstudio.com/docs/editor/multi-root-workspaces

    TL;DR After opening your first project, select Add Folder to Workspace to add additional projects.

    I understand that change sucks, but I think learning VS Code will serve you well if you ever want to work with other languages like Python, JavaScript or TypeScript. VS Code is the most popular IDE for developers now, and a lot of its concepts and features can be found in other modern editors (such as the command palette, multiple cursors, context-sensitive code lens etc.)

    I understand that Eclipse is no longer supported, but is there a way to get the last plug-in back ?

    Do you still have the cached plugin files?

    In Windows, open explorer and paste %userprofile%\.p2\pool\plugins into the address bar. See if you have the following files:

    IQ_IDE_4.1.2.jar
    IQ_SdkManager_4.1.2.jar

    If so, you should be able to reinstall the plugins by copying them to the dropins folder in your eclipse installation folder.

    %userprofile%\eclipse\[ECLIPSE INSTALLATION FOLDER]\eclipse\dropins

  • Thanks.

    I'm working on switching to VS Code, see the value in doing so, and largely like it. The multi project workspace issue is a real issue though. Plenty written about avoiding it to avoid problems and confusion, not to mention the setup issues I'm seeing described. I tried it and could not control which project was being built. Not fun and not a good use of time.

    I'll see if the plug-ins are cached as you describe.

    Thanks for your help.

  • I tried it and could not control which project was being built

    This part is kind of annoying.

    If you use Command Palette > Monkey C: Build Current Project, it will always build the currently selected project (e.g. the project for which a source file is currently focused). However, Run/F5 will build/run the first successfully built project until you do something to make it forget (like restarting VS Code).

    The best thing to do is probably to create a launch config for each project, so you can have direct control over which project is run.

    code.visualstudio.com/.../debugging

  • The way I do this is by tapping The highlighted icon here, gives you a list of apps to run or run in a test.  At the bottom of the list, a simple tap allows adding a new launch config/

  • Thanks Jim, but no luck with this so far.

    I selected File -> Add Folder to Workspace to add a second project directory to the workspace (a second sample project).

    Then I select View -> Run to see something similar to what you're showing but there is no icon as shown in your example, and there is no list to select from.

    When I press "Run and Debug" the first project is built and run in the simulator.

    When I open one of the source files for the second project, the same thing occurs.

    There must be some other trick.

  • There's also a dot to the right of the project that gets built and if I right click on either project the menu includes "Build Currnet Project" but it always builds the project with the dot and I see no way to change the selected or current project.

  • Click on the triage with the little bug on the left.  The one that is bold in my screen shot.  You should then see "Run App" with a down arrow.  Click the down arrow and you see the menu like I show.

    Not sure why you aren't showing the icons along the left.

    Ok, Try view>appearance>activity bar

  • There's also a dot to the right of the project that gets built

    The dot means your project has "emphasized items" (errors/warnings from the build which show up in the Problems tab in the bottom pane.) It's not surprising that the project you built has a dot since the build likely generated a few warnings. (If you manage to build the other project, you'll probably also get a dot beside that one.)

    Then I select View -> Run to see something similar to what you're showing but there is no icon as shown in your example, and there is no list to select from.

    Click on the triage with the little bug on the left.  The one that is bold in my screen shot.  You should then see "Run App" with a down arrow.  Click the down arrow and you see the menu like I show.

    Not sure why you aren't showing the icons along the left.

    Ok, Try view>appearance>activity bar

    I think he means there's no run icon (the green triangle immediately to the left of the list in your example) and no list. Here's a screenshot of what it would look like if he could see it.

    The reason he can't see it is the green triangle and the list only appear after you've created at least one launch config.

    This is what the user sees when there's no existing launch configurations:

    As mentioned in the official documentation linked above, the way to add your first launch config is to click on "create a launch.json file" as seen in the screenshot above.

    [https://code.visualstudio.com/docs/editor/debugging#_launch-configurations]

    There's also a dot to the right of the project that gets built and if I right click on either project the menu includes "Build Currnet Project" but it always builds the project with the dot and I see no way to change the selected or current project.

    That's very strange. Feels like a bug to me. I don't have that problem with Build Current Project (either in the right-click menu or the command palette.) Doesn't make a difference whether launch configs are present or not.

    Regardless, the ability to build the project of your choice is somewhat useless given that the default Run command won't run the project of your choice :/. (Unless you need to be able to build without running, which is def a valid use case.)

    I also feel like the inability to run the current project without creating a launch config is a bug. I created a multi-root workspace with 2 python projects, and VS Code doesn't have a problem running the selected project without the use of launch configs.

  • There's also a dot to the right of the project that gets built and if I right click on either project the menu includes "Build Currnet Project" but it always builds the project with the dot and I see no way to change the selected or current project.

    Actually I think I see your problem. Based on your screenshot, it looks like you may have opened the parent folder of your two project folders as a single project. This could happen if you launched Code on the parent folder (e.g. Right-click > Open in Code) or if you added the parent folder using the File > Open Folder dialog. You need to add each project folder to the workspace, as opposed to adding the parent folder.

    So in this case, VS Code thinks you have a single project, which explains why it won't let you build the other one.

    This is what a multi-root workspace with multiple projects looks like - note the circle to the left of each project (which isn't present in your screenshot):

    Try starting over.

    1) Open VS Code (with a blank workspace)

    2) File > Open Folder Add Folder to Workspace > [select WebRequest folder]

    3) File > Open Folder Add Folder to Workspace > [select BulkDownload folder]

    You can also select multiple folders in the Open Folder dialog using SHIFT-click or CTRL-click, but what you can't do is open the parent folder and expect VS Code to add all of its contents as individual projects, unfortunately.

    Another method would be to start VS Code fresh with a blank workspace, then drag and drop your project folders from File Explorer onto the VS Code window. You can also drag and drop folders onto an existing workspace.

    I still think the Run behavior for Monkey C is broken.

  • Thanks for trying to help. So far, no progress.

    Tried the approach you described... Open VS Code with blank workspace, then use File  Open Folder > WebRequest folder.

    Then File > Open Folder > BulkDownload folder.

    Upon the second command, I end up with only the BulkDownload folder opened.

    Stifling my urge to rant at this point.