Transfering old projects to VS Code Extension

Hi, I want to transfer all my projects to the VS Code Extension. I installed VS Code successfully and opened an old project (any .mc file). Then I hit F5 and get this:

Connect IQ project has not found. Be sure your project has a monkey.jungle file...

All my projects have jungle files. How can I get this beast running again?

Thanks for supporting.

jim_m_58 over 2 years ago

The way I do it is add a foler to the workspace, where that folder is the same as I had in eclipse. Right clip on the workspace window, then select "All folder to Workspace". You should the be able to select a .mc file from withing that folder.

topcaser over 2 years ago in reply to jim_m_58

Hi Jim,

thanks for that directions. But with a right click on the workspace window the item "All folder to Workspace is missing". Is there anything additional to do?

jim_m_58 over 2 years ago in reply to topcaser

If, you don't have a workspace yet, go to file>open folder and pick one of your project folders

topcaser over 2 years ago in reply to jim_m_58

OK, managed it in another way. Problem is, that my context menu doesn't look like yours if I click on my added workspace folder and the "All folder to Worlkspace" option is missing. But I clicked on File > Add Folder to Workspace and selected all project ubfolders in my workspace. That did the trick. But the compiler is more strict than before (maybe due to an updated SDK). For example I returned true in the function onUpdate(dc) - this wasn't a problem before, this time the compiler fails. Is this behavior due to VSC or the new SDK?

flowstate over 2 years ago in reply to topcaser

topcaser said:
For example I returned true in the function onUpdate(dc) - this wasn't a problem before, this time the compiler fails. Is this behavior due to VSC or the new SDK?

It's due to the default type checking behavior in the new SDK. onUpdate() is defined as returning Void, so the type checker considers it an error if you return a Boolean, even though it's harmless in practice.

You can disable type checking completely (although I probably wouldn't recommend that for new projects).

- Open the command palette: CTRL-SHIFT-P (CMD-SHIFT-P on Mac)

- Search the palette for "Preferences: Open User Settings" (fuzzy search is in effect, so you can type a partial string like "pruser")

- (optional) If you want to change this setting on a per-workspace basis, click on the "Workspace" tab

- Search the settings for "Monkey C: type check level" (fuzzy search is also supported here, so you can type something like "monkeytype")

- Set the type check level to "Off"