Skip to content
This repository has been archived by the owner on Feb 11, 2023. It is now read-only.

Compile issue #33

Open
HaiyanDu7 opened this issue Dec 18, 2017 · 1 comment
Open

Compile issue #33

HaiyanDu7 opened this issue Dec 18, 2017 · 1 comment

Comments

@HaiyanDu7
Copy link

I have visual studio 2017 installed. I am sure have .NET 4.7.1 installed but your project still complain .net framework missing. I really like your software, It is better that your software can be compiled to .net 4.0 which will be compatible most of old software. If you target .net 4.7.x, you will be competitor of IdenityServer4.

image
image

@alekseynemiro
Copy link
Member

alekseynemiro commented Dec 30, 2017

Thank you for your message!

The package does not have assembly for .NET 4.7.1.

The latest version (v1.13) has assemblies for .NET 3.5, 4.0, 4.5, 4.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2 and 4.7.

The project is also targeted at all versions of .NET from 3.5 to 4.7 inclusive.

Need to build assemblies for new versions of .NET and add to package. But I do not see any good reasons for this.

You can add the assembly for .NET v4.7.1 to the package yourself and use the package from the local source (for example, from a folder).

I can not do this because I will have to conduct a full cycle of testing and this will take a very long time, which I do not have now.

The presence of v4.7.1 does not guarantee that projects aimed at v4.7 will work correctly in Visual Studio. Maybe you need to install something. Or the problem with dependent packages. Or in the configuration.

It is better that your software can be compiled to .net 4.0 which will be compatible most of old software.

The assembly for .NET v4.0 is exists.

As for the source code, unfortunately it is impossible to make it fully working in all situations. There are problems with dependencies, system configuration, and various versions of the .NET Framework.

If you do not need any versions of .NET, just delete them from the source code of the project file (.csproj,
for example Nemiro.OAuth.csproj).

If you have a problem with the source code, it's better to use the Nemiro.OAuth package.

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

No branches or pull requests

2 participants