Asked — Edited
Resolved Resolved by DJ Sures!

Failed Into Install Windows Sdk From Nuget Package Manager

Hi all,

Trying to install the Windows .NET SDK in the NuGet package manager and I am unable to. My project targets .NET 4.5. I get the following message below. Anyone seen this?

Install-Package : Could not install package 'EZ_B.dll 2015.5.20'. You are trying to install this package into a project that targets '.NETFramework,Version=v4.5', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author. At line:1 char:1

  • Install-Package EZ_B.dll -Version 2015.5.20
  •   + CategoryInfo          : NotSpecified: (:) [Install-Package], Exception
      + FullyQualifiedErrorId : NuGetCmdletUnhandledException,NuGet.PackageManagement.PowerShellCmdlets.InstallPackageCommand
    


ARC Pro

Upgrade to ARC Pro

Subscribe to ARC Pro, and your robot will become a canvas for your imagination, limited only by your creativity.

PRO
Synthiam
#1  

The nugget package is outdated. Install the sdk from the software tab of this website

However, the sdk is much less useful than creating a plugin. I recommend creating a plugin over the sdk

#2  

Hey @dj-sures,

Thanks for answering. How come the NuGet package is out of date, would it be easy to update it?

Why plugin over SDK? How is a plugin more useful? I prefer to code than to use the ARC, it's great but its not what I'd rather use.

#3  

Hi Mr. @dj-sures,

Using the package from the site directly fixed my problem. Though I'd still like to know your thoughts on plugin vs SDK. Basically I want to make sure the SDK is still going to be supported.

#4  

I think I gave you a pretty good answer to this question in this thread https://synthiam.com/Community/Questions/11765

Basically, ARC does 99% of what a robot builder would need. The plugin framework allows you to add functionality without re-creating everything ARC does as well.

If you want to program everything yourself, than the SDK is great. There is also a documented communication protocol, so you can really do it all from scratch.

However, if you are looking for community assistance, you will find many more users of ARC and a few plugin developers. Very few SDK users except DJ himself participate here, and I can count on half of one hand the number of discussions about the communication protocol.

Alan

#5  

@thetechguru You actually did answer my question in the other post. Sorry, still new so will take awhile to take everything in (just the way I learn). Though I should of remembered your post.

I do feel a bit of negativity towards the SDK though. I'll continue hacking away and learning and add back when I can.

Cheers

PRO
Synthiam
#6  

The sdk is always supported. the community prefers ARC because it’s easier to share and exchange ideas through plugins. That way we all leverage from each other’s efforts. Stronger as many! So they say :D

#7  

Quote:

I do feel a bit of negativity towards the SDK though.

I wouldn't say negativity so much as most users don't need that much power. It got a lot more use before DJ added the plugin framework, but most users still used it alongside ARC, mostly for passing variables and commands between ARC and third party apps, something that the plugin framework makes easier.

A good current use of the SDK is if you already have an application thst you want to add some EZ-B functionality to rather than adding some functionality to a mostly ARC robot. For instance RoboRealm uses the SDK to tell an EZ-B to navigate. It can be used independently of ARC, or along with it depending on what else you want the robot to do, but the core application in that case is RoboRealm.