Thanks Brett for your reply -
I was at the “bouncing ball” page when I started last week and here are the steps I took
from that page:
1)I started at step 2 since I already have V studio., I followed the tip on step 2 so I
uninstalled the previous SDK. Then I installed .NET Micro Framework 4.3(QFE1).
- I installed the Microsoft .NET Gadgeteer Core 2.43.900.
In my project, from the place to Add References, I see under Assemblies.
Framework … Targeting .NET Micro Framework 188.8.131.52 and a list of 23 items , all with version 184.108.40.206.
Extensions… Targeting .NET Micro Framework 220.127.116.11 with a list of stuff with different versions. Among those, I see Gadgeteer 18.104.22.168, Gadgeteer.Serial 22.214.171.124,
Gadgeteer.SPI 126.96.36.199, …GHI.Hardware 188.8.131.52, GHI.Premium.Hardware 184.108.40.206,
GHI.Premium.IO220.127.116.11, GHI.Premium.Net 18.104.22.168…GHI.Usb 22.214.171.124, etc…
I think pretty much all of that came up checked already.
But, if we take one error I’m getting during build - as describe below -
Cannot resolve type Gadgeteer.SocketInterfaces.AnalogOutput from assembly
I can see that I have GTM.GHIElctronicsExtender 126.96.36.199 checked.
I go to the definition of AnalogOutput and see this
public AnalogOutput CreateAnalogOutput(Socket.Pin pin);
Then from my code → GT.SocketInterfaces.AnalogOutput ao; I go to definition and see
this abstract class in the namespace Gadgeteer.SocketInterfaces from Assembly Gadgeteer.dll, v188.8.131.52. I don’t see this assembly in my references but don’t know if I should or not.
I will try to create a new project as you suggest, and I’m trying to follow the documentation but it all seems very complicated and not sure what to do to tell you the truth. I had analog output working before I went to the new SDK.