Alan.raceQs said:

FlowState said:

you just install the Money C extension (from Garmin)

As I'm not familiar with the VSC UI, I don't know what that means.

your link https://marketplace.visualstudio.com/items?itemName=garmin.monkey-c took me here:

Like I said, install it from the extensions tab or use the link. Obviously the link worked fine for you.

And if you don't know what the extensions tab is in Visual Studio Code, you will probably want to learn eventually. I searched "vs code extensions tab" in google and this was the first hit (it includes a video):

https://code.visualstudio.com/docs/introvideos/extend

Using extensions in Visual Studio Code

Alan.raceQs said:

I was concerned by the message highlighted that it was in Alpha state. I really don't want to be testing Garmin's software when I'm already testing my own!

I think it was made clear above that Monkey C in VS Code isn't finished.

Alan.raceQs said:

Stop 1 Install extension. I assumed that meant press the green Install button, so I did. It opened VSC - with no further instructions.

Yeah, "install extension" means press Install. I was hoping that would be clear from context.

Alan.raceQs said:

crashes Safari and

It's not the VS Code Monkey C Extension which "crashes" Safari, it's the Connect IQ SDK link which is misconfigured by Garmin -- clicking the link should cause the SDK manager file to be downloaded instead of trying to render the file as a web page. I've already filed a bug about this:

forums.garmin.com/.../macos-safari-connect-iq-sdk-dmg-is-rendered-as-text-instead-of-being-downloaded

Logically, this would be a problem whether you use Eclipse or VS Code, since both of them require the SDK manager, so I'm not sure why you think this is only a problem with VS Code.

I also don't understand why you needed to install the Connect IQ SDK Manager again when you said you already had it installed.

Alan.raceQs said:

I think I have followed steps 3. and 4, but what does 5. mean?

'Run "Monkey C: Verify Installation" command' means that you use the command palette to run the command in question:

CMD-SHIFT-P > "Monkey C: Verify Installation"

(You can type a partial command, and the palette will do a fuzzy search)

All due respect, there are some things which you might want to try to figure out for yourself from context, by experimenting with VS Code, or failing that, by doing a search.

Given that the docs from Garmin (produced by paid employees) are apparently insufficient, you can't expect that volunteer help on a forum is always going to have 100% of the details.

Alan.raceQs said:

What are the instructions for importing an Eclipse project for a watch app into VSC?

Just select the project folder in Finder, option-click (or two-finger-click) and select Open with Code.

Or in VS Code, you can use File > Add Folder to Workspace (so you can have multiple projects in one workspace, just like eclipse.)

Alan.raceQs said:

So, what with the prospect of:

1. using an Alpha version of a Garmin plugin to a
2. foreign IDE, which 
3. crashes Safari and
4. requests credentials I'm not aware of,

I'm struggling to move to VSC. 

You don't have to move to VS Code immediately if you don't want to, but eventually you'll have to. There's nothing anyone on this forum can do or say to prevent that. (Unless there's a huge outcry which causes Garmin to reverse its decision. But according to Alpha Monkey himself -- in one of the videos from last year's conference -- the switch to VS Code was done because it's more popular and because Eclipse is considered to be a high barrier of entry.)

Alan.raceQs said:

requests credentials I'm not aware of,

I know you already resolved this (based on your deleted comment), but once again, the Connect IQ SDK manager is required whether you use Eclipse or VS Code (*), so I'm not sure why this complaint is being made in reference to using VS Code. 2 out of the 4 issues in your list are specific to the SDK manager and not VS Code.

(* Unless you continue to use an old SDK in Eclipse forever.)

I'm also not sure how you're able to log into your developer dashboard to upload app updates if you were (previously) unaware of your developer credentials....

Thanks for that. I think I'll put it back on the back burner till Garmin gets it into production.

As the SDKmanger seems new to you (t's been around since 3.2), what I'd suggest is keep using Eclipse for now.  Download the SDK and devices, and there is a 4.0.1 Eclipse plugin.  Get things working there and then start looking into VS Code.  As you noted, the extension is still alpha.

With the 4.0.1 eclipse plugin, it's clear eclipse will be around for at least some time, and that will give you time to get a handle on VS Code, while still having access to devices from the last few months, porting to the 4.x devices like the venu 2, etc.

Alan.raceQs said:

Thanks for that. I think I'll put it back on the back burner till Garmin gets it into production.

Sounds good to me. I will say that I'm a lot more productive in VS Code compared to Eclipse, and I enjoy using VS Code a lot more, but that's just my subjective opinion (which happens to be shared by a lot of ppl.)

I personally wouldn't use Eclipse for anything except Garmin development with app settings. Even when I work on a project with app settings, sometimes I use Eclipse for the app settings / build, and use VS Code to edit the code.

Hopefully when you get a chance to get familiar with VS Code (it really doesn't take that long), you'll end up liking it.

Use the SDK manager in your first screen shot (the one with 4.0.1).  You must also click on the devices tab and download those.  And in eclipse, make sure you update it's plugin - the current one is also 4.0.1.

Alan.raceQs said:

I'm returning to your earlier comments and am not sure why you made that assumption.

The only SDK Manager I have resides inside Eclipse. The SDK Manager app I downloaded with connectiq-sdk-manager.dmg is a totally new interface. 

Sorry! My mistake -- I assumed you were using a fairly recent Connect IQ SDK with Eclipse -- every SDK starting around 3.2.x requires the new Connect IQ SDK Manager which is the one you just downloaded.

Sorry about that! Definitely bad instructions on my part.

Like Jim said, if you update the Connect IQ plugin in Eclipse, it will use the new SDK manager (just like VS Code does.)