Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NuGet package does not install on .NET v4.5.2 #73

Open
dhaddad355 opened this issue Apr 7, 2020 · 3 comments
Open

NuGet package does not install on .NET v4.5.2 #73

dhaddad355 opened this issue Apr 7, 2020 · 3 comments

Comments

@dhaddad355
Copy link

It seems as if EvilDICOM 2.0.6.5 is not able to add package on .NET v4.5.2.

Error
Could not install package 'EvilDICOM 2.0.6.5'. You are trying to install this package into a project that targets '.NETFramework,Version=v4.5.2', 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.

@jazb83
Copy link
Contributor

jazb83 commented May 27, 2020

You need to install the .NET Framework 4.7.2 Development Tools because evilDICOM 2.0.6.5 requires NetFrameWork Version 4.7.2 to work.

image

you can just download and install the Framework 4.7.2 Developer Pack: From this link: https://dotnet.microsoft.com/download/dotnet-framework/net472 (the location could change in the future).

Then, just change the target framework for your app: Solution Explorer -> right Click -> Properties -> Application -> Target framework from the pop-up list.

image

You can install evilDicom now

@Erhushenshou
Copy link

But Esapi and varian eclipse seemed only worked on version before 4.6.

@crazywill32
Copy link

Just to provide the information, the ESAPI will work on versions of 4.7.2. This was true for ESAPIv13.7 and ESAPIv16.1. You just need to change the library targeted framework as described above.

It should be noted that single-file scripts must only contain functions within the framework version provided by Eclipse. This is because their compiler won't understand the new framework features.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants