I am completely stumped on a compile error I am getting after updating to the latest version.? When I have run into similar problems in the past doing a full recompile after deleting the spiswork directory has resolved the issue but this time no luck.? The module I am struggling with is the official denon heos modules, and to add to the mystery if I create a brand new program and add the modules I dont get any compile errors.

Here are the two errors I am struggling with.? Any help is greatly appreciated

ERROR? (LGCMCVT149)? Code\SPlsWork\DenonHEOS_Device_Engine_v7_1_0.cs, Line 91
??????? Code\SPlsWork\DenonHEOS_Device_Engine_v7_1_0.cs] Internal Error (Line 91) - The type 'Crestron.CRPC.MediaPlayer.IMediaPlayer' is defined in an assembly that is not referenced. You must add a reference to assembly 'MediaPlayer, Version=1.0.0.26508, Culture=neutral, PublicKeyToken=null'.
ERROR? (LGCMCVT258) ?
??????? SIMPL+: C# - Compiled with errors for \Code\SPlsWork\DenonHEOS_Device_Engine_v7_1_0.dll

Have you tried downgrading to a pre-200 database?

开云体育

I havent tried downgrading the DB since I actually upgraded to support a different module.? I have tried deleting the current module and just readding it, and get the same errors.? As I mentioned I have tried creating a new program from scratch and adding the modules and it compiles just fine.? Super weird.

I cannot speak to DB200 -- I am too chicken.? But I have had a few cases where programs have gotten corrupted in weird ways.?? You might try replacing your processor with a different type and then replacing it back again.? Don't ask me why but I believe that has solved some issues in the past.

Also, it could be your module is conflicting with another module such as a TCP server on the same port.

You also might try using Pre-200 from most of your program and then add a separate program that requires Post-200.? I've run different program versions in different slots I haven't had issues.? Shoot, I even have run SIMPL in one slot and Studio or D3PRO in another slot successfully.

This is OT (apologies) but the paranoia about DB200 is unwarranted (IMO).

Yes, it is a pain to have to migrate project modules(*) and if we didn't have to do it life would be a little bit better, but I think NOT making the move is going to be a greater headache in the long run.

For the sake of clarity:
The DB200 breaking change was a dependency update from NetwonSoft 3.5 to NewtonSoft 4.0.? This is often used in S# drivers that require JSON parsing.? If a driver doesn't have the Newtonsoft depenedency, then the move to DB200 is as transparent as any other DB update (yes, I accept that Crestron have broken things in the past, but in general DB updates are pretty solid - I'm also not drinking the Crestron Kool-aid here - believe me, I have plenty of reasons to gripe).

That's it - if your Crestron DB's are NewtonSoft 4 and your module requires 3.5, it won't compile.? If they're the same version, it will - it's no scarier than that.?

The large change in version number does NOT reflect a wholesale change as it might suggest.? I have to admit I may have some responsibility here as I discussed the forthcoming change with Crestron and suggested that a clear distinction in versioning might help identify which side of the NewtonSoft fence you were operating on - the unforeseen side-effect might be that such a big version change /suggests/ a bigger change than the reality.

There is no direct dependency on firmware here either, so you can certainly run a program compiled against one version in one slot and a different one in another slot, just as it shouldn't be a surprise that you can run SIMPL in one, SSPro in another, D3Pro in another and Studio in another.

Sorry to get a bit preachy, but I do think with a little bit of preparation moving projects to DB200 isn't as big a deal as some appear to feel it is.
Sermon over!
Ol

* That's making the assumption that updated modules have been provided by the developer - but any module developer should have done this by now (we had made ours available /before/ the DB200 release)

How does one update the Newtonsoft version within a VS2008 project to fix this in the code and recompile .clz?

You need to right click "references" under the project name on the far right tab in VS2008. Then you can add the SimplSharp NewtonSoft dll. Hit F6 to recompile and you should be good to go.