.NETStandard NuGet packages
I am trying to download a package that will allow me to encrypt and decrypt passwords. However, I can not find a package that is compatible with my project as I am working in .NETStandard.
Is there a way to make a package that is not fully compatible still work?
When I try to change my project to a .NETFramework I do not get the option of any .NETFrameworks...
Despite another project in the same solution being targeted to .NETFramework v4.6.1
Solutions:
Are there any .NETStandard password encryption packages?
Is there a way to search for .NETStandard compatiable packages?
Can I make my project target a .NETFramework even though it is not an option, but is downloaded?
c#
asked Nov 22 at 14:22
NodeCode
205
add a comment |
I am trying to download a package that will allow me to encrypt and decrypt passwords. However, I can not find a package that is compatible with my project as I am working in .NETStandard.
Is there a way to make a package that is not fully compatible still work?
When I try to change my project to a .NETFramework I do not get the option of any .NETFrameworks...
Despite another project in the same solution being targeted to .NETFramework v4.6.1
Solutions:
Are there any .NETStandard password encryption packages?
Is there a way to search for .NETStandard compatiable packages?
Can I make my project target a .NETFramework even though it is not an option, but is downloaded?
c#
asked Nov 22 at 14:22
NodeCode
205
2
Uh...what kind of passwords are you encrypting?
– John
Nov 22 at 14:23
5
Uh... Why would you want to decrypt passwords?
– Deblaton Jean-Philippe
Nov 22 at 14:25
Uh... to create a login form
– NodeCode
Nov 22 at 14:40
Asking for recommendation (packages) is off-topic. You cannot change target frameworks freely, as different project types have their own options, blog.lextudio.com/…
– Lex Li
Nov 22 at 15:28
add a comment |
I am trying to download a package that will allow me to encrypt and decrypt passwords. However, I can not find a package that is compatible with my project as I am working in .NETStandard.
Is there a way to make a package that is not fully compatible still work?
When I try to change my project to a .NETFramework I do not get the option of any .NETFrameworks...
Despite another project in the same solution being targeted to .NETFramework v4.6.1
Solutions:
Are there any .NETStandard password encryption packages?
Is there a way to search for .NETStandard compatiable packages?
Can I make my project target a .NETFramework even though it is not an option, but is downloaded?
c#
asked Nov 22 at 14:22
NodeCode
205
I am trying to download a package that will allow me to encrypt and decrypt passwords. However, I can not find a package that is compatible with my project as I am working in .NETStandard.
Is there a way to make a package that is not fully compatible still work?
When I try to change my project to a .NETFramework I do not get the option of any .NETFrameworks...
Despite another project in the same solution being targeted to .NETFramework v4.6.1
Solutions:
Are there any .NETStandard password encryption packages?
Is there a way to search for .NETStandard compatiable packages?
Can I make my project target a .NETFramework even though it is not an option, but is downloaded?
c#
c#
asked Nov 22 at 14:22
NodeCode
205
asked Nov 22 at 14:22
NodeCode
205
asked Nov 22 at 14:22
NodeCode
205
asked Nov 22 at 14:22
NodeCode
205
asked Nov 22 at 14:22
NodeCode
205
205
2
Uh...what kind of passwords are you encrypting?
– John
Nov 22 at 14:23
5
Uh... Why would you want to decrypt passwords?
– Deblaton Jean-Philippe
Nov 22 at 14:25
Uh... to create a login form
– NodeCode
Nov 22 at 14:40
Asking for recommendation (packages) is off-topic. You cannot change target frameworks freely, as different project types have their own options, blog.lextudio.com/…
– Lex Li
Nov 22 at 15:28
add a comment |
2
Uh...what kind of passwords are you encrypting?
– John
Nov 22 at 14:23
5
Uh... Why would you want to decrypt passwords?
– Deblaton Jean-Philippe
Nov 22 at 14:25
Uh... to create a login form
– NodeCode
Nov 22 at 14:40
Asking for recommendation (packages) is off-topic. You cannot change target frameworks freely, as different project types have their own options, blog.lextudio.com/…
– Lex Li
Nov 22 at 15:28
2
2
Uh...what kind of passwords are you encrypting?
– John
Nov 22 at 14:23
Uh...what kind of passwords are you encrypting?
– John
Nov 22 at 14:23
5
5
Uh... Why would you want to decrypt passwords?
– Deblaton Jean-Philippe
Nov 22 at 14:25
Uh... Why would you want to decrypt passwords?
– Deblaton Jean-Philippe
Nov 22 at 14:25
Uh... to create a login form
– NodeCode
Nov 22 at 14:40
Uh... to create a login form
– NodeCode
Nov 22 at 14:40
Asking for recommendation (packages) is off-topic. You cannot change target frameworks freely, as different project types have their own options, blog.lextudio.com/…
– Lex Li
Nov 22 at 15:28
Asking for recommendation (packages) is off-topic. You cannot change target frameworks freely, as different project types have their own options, blog.lextudio.com/…
– Lex Li
Nov 22 at 15:28
add a comment |
2 Answers
2
active
oldest
votes
The warning itself is just a warning but the library might still work fully well, especially when you are actually targeting .NET Framework 4.6.1 with your project.
Basically when you create a .NET Standard library, it targets a specific version of .NET Standard and you can imagine .NET Standard as a set of interfaces a platform that supports that version of .NET Standard must support. In this case, if you are targeting .NET Framework 4.6.1 with the app, the .NET Standard library will run on .NET Framework 4.6.1 anyway, so there shouldn't be any problem.
Problems could occur if you built another client targeting a different implementation of .NET like .NET Core or Mono, which wouldn't support some of the APIs that the library is using internally. In such case the application would crash once such API was accessed because the platform does not offer any implementation of it.
In case you don't require cross-platform support, you could just use classic .NET Framework library, instead of .NET Standard and the warning would disappear.
answered Nov 22 at 14:27
Martin Zikmund
22.8k33159
Yes, I have just updated my answer with this point. However, you may still use a library targeting full .NET if it does not do anything "malicious" - meaning it does not access any non-Standard APIs. If you can be sure of that, the library will have no issues running against any other .NET implementation supporting the same .NET Standard version.
– Martin Zikmund
Nov 22 at 14:31
The package does not work unfortunately - Eramake.eCryptography.
– NodeCode
Nov 22 at 14:53
Even when you target the same .NET Framework version as the package itself?
– Martin Zikmund
Nov 22 at 14:55
add a comment |
I'm personally using RSACryptoServiceProvider
from System.Security.Cryptography. This is available in .NET standard. Doesn't need any nuget packages either.
using System.Security.Cryptography;
Edit:
I should add to this that encrypting/decrypting password is never a good idea. Password should be stored as a hash width a strong one way hasing algorithm and should never be encrypted for decryption for later use.
answered Nov 22 at 15:17
fstam
366213
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53432999%2fnetstandard-nuget-packages%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
The warning itself is just a warning but the library might still work fully well, especially when you are actually targeting .NET Framework 4.6.1 with your project.
Basically when you create a .NET Standard library, it targets a specific version of .NET Standard and you can imagine .NET Standard as a set of interfaces a platform that supports that version of .NET Standard must support. In this case, if you are targeting .NET Framework 4.6.1 with the app, the .NET Standard library will run on .NET Framework 4.6.1 anyway, so there shouldn't be any problem.
Problems could occur if you built another client targeting a different implementation of .NET like .NET Core or Mono, which wouldn't support some of the APIs that the library is using internally. In such case the application would crash once such API was accessed because the platform does not offer any implementation of it.
In case you don't require cross-platform support, you could just use classic .NET Framework library, instead of .NET Standard and the warning would disappear.
answered Nov 22 at 14:27
Martin Zikmund
22.8k33159
Yes, I have just updated my answer with this point. However, you may still use a library targeting full .NET if it does not do anything "malicious" - meaning it does not access any non-Standard APIs. If you can be sure of that, the library will have no issues running against any other .NET implementation supporting the same .NET Standard version.
– Martin Zikmund
Nov 22 at 14:31
The package does not work unfortunately - Eramake.eCryptography.
– NodeCode
Nov 22 at 14:53
Even when you target the same .NET Framework version as the package itself?
– Martin Zikmund
Nov 22 at 14:55
add a comment |
The warning itself is just a warning but the library might still work fully well, especially when you are actually targeting .NET Framework 4.6.1 with your project.
Basically when you create a .NET Standard library, it targets a specific version of .NET Standard and you can imagine .NET Standard as a set of interfaces a platform that supports that version of .NET Standard must support. In this case, if you are targeting .NET Framework 4.6.1 with the app, the .NET Standard library will run on .NET Framework 4.6.1 anyway, so there shouldn't be any problem.
Problems could occur if you built another client targeting a different implementation of .NET like .NET Core or Mono, which wouldn't support some of the APIs that the library is using internally. In such case the application would crash once such API was accessed because the platform does not offer any implementation of it.
In case you don't require cross-platform support, you could just use classic .NET Framework library, instead of .NET Standard and the warning would disappear.
answered Nov 22 at 14:27
Martin Zikmund
22.8k33159
Yes, I have just updated my answer with this point. However, you may still use a library targeting full .NET if it does not do anything "malicious" - meaning it does not access any non-Standard APIs. If you can be sure of that, the library will have no issues running against any other .NET implementation supporting the same .NET Standard version.
– Martin Zikmund
Nov 22 at 14:31
The package does not work unfortunately - Eramake.eCryptography.
– NodeCode
Nov 22 at 14:53
Even when you target the same .NET Framework version as the package itself?
– Martin Zikmund
Nov 22 at 14:55
add a comment |
The warning itself is just a warning but the library might still work fully well, especially when you are actually targeting .NET Framework 4.6.1 with your project.
Basically when you create a .NET Standard library, it targets a specific version of .NET Standard and you can imagine .NET Standard as a set of interfaces a platform that supports that version of .NET Standard must support. In this case, if you are targeting .NET Framework 4.6.1 with the app, the .NET Standard library will run on .NET Framework 4.6.1 anyway, so there shouldn't be any problem.
Problems could occur if you built another client targeting a different implementation of .NET like .NET Core or Mono, which wouldn't support some of the APIs that the library is using internally. In such case the application would crash once such API was accessed because the platform does not offer any implementation of it.
In case you don't require cross-platform support, you could just use classic .NET Framework library, instead of .NET Standard and the warning would disappear.
answered Nov 22 at 14:27
Martin Zikmund
22.8k33159
The warning itself is just a warning but the library might still work fully well, especially when you are actually targeting .NET Framework 4.6.1 with your project.
Basically when you create a .NET Standard library, it targets a specific version of .NET Standard and you can imagine .NET Standard as a set of interfaces a platform that supports that version of .NET Standard must support. In this case, if you are targeting .NET Framework 4.6.1 with the app, the .NET Standard library will run on .NET Framework 4.6.1 anyway, so there shouldn't be any problem.
Problems could occur if you built another client targeting a different implementation of .NET like .NET Core or Mono, which wouldn't support some of the APIs that the library is using internally. In such case the application would crash once such API was accessed because the platform does not offer any implementation of it.
In case you don't require cross-platform support, you could just use classic .NET Framework library, instead of .NET Standard and the warning would disappear.
answered Nov 22 at 14:27
Martin Zikmund
22.8k33159
answered Nov 22 at 14:27
Martin Zikmund
22.8k33159
answered Nov 22 at 14:27
Martin Zikmund
22.8k33159
answered Nov 22 at 14:27
Martin Zikmund
22.8k33159
22.8k33159
Yes, I have just updated my answer with this point. However, you may still use a library targeting full .NET if it does not do anything "malicious" - meaning it does not access any non-Standard APIs. If you can be sure of that, the library will have no issues running against any other .NET implementation supporting the same .NET Standard version.
– Martin Zikmund
Nov 22 at 14:31
The package does not work unfortunately - Eramake.eCryptography.
– NodeCode
Nov 22 at 14:53
Even when you target the same .NET Framework version as the package itself?
– Martin Zikmund
Nov 22 at 14:55
add a comment |
Yes, I have just updated my answer with this point. However, you may still use a library targeting full .NET if it does not do anything "malicious" - meaning it does not access any non-Standard APIs. If you can be sure of that, the library will have no issues running against any other .NET implementation supporting the same .NET Standard version.
– Martin Zikmund
Nov 22 at 14:31
The package does not work unfortunately - Eramake.eCryptography.
– NodeCode
Nov 22 at 14:53
Even when you target the same .NET Framework version as the package itself?
– Martin Zikmund
Nov 22 at 14:55
Yes, I have just updated my answer with this point. However, you may still use a library targeting full .NET if it does not do anything "malicious" - meaning it does not access any non-Standard APIs. If you can be sure of that, the library will have no issues running against any other .NET implementation supporting the same .NET Standard version.
– Martin Zikmund
Nov 22 at 14:31
Yes, I have just updated my answer with this point. However, you may still use a library targeting full .NET if it does not do anything "malicious" - meaning it does not access any non-Standard APIs. If you can be sure of that, the library will have no issues running against any other .NET implementation supporting the same .NET Standard version.
– Martin Zikmund
Nov 22 at 14:31
The package does not work unfortunately - Eramake.eCryptography.
– NodeCode
Nov 22 at 14:53
The package does not work unfortunately - Eramake.eCryptography.
– NodeCode
Nov 22 at 14:53
Even when you target the same .NET Framework version as the package itself?
– Martin Zikmund
Nov 22 at 14:55
Even when you target the same .NET Framework version as the package itself?
– Martin Zikmund
Nov 22 at 14:55
add a comment |
I'm personally using RSACryptoServiceProvider
from System.Security.Cryptography. This is available in .NET standard. Doesn't need any nuget packages either.
using System.Security.Cryptography;
Edit:
I should add to this that encrypting/decrypting password is never a good idea. Password should be stored as a hash width a strong one way hasing algorithm and should never be encrypted for decryption for later use.
answered Nov 22 at 15:17
fstam
366213
add a comment |
I'm personally using RSACryptoServiceProvider
from System.Security.Cryptography. This is available in .NET standard. Doesn't need any nuget packages either.
using System.Security.Cryptography;
Edit:
I should add to this that encrypting/decrypting password is never a good idea. Password should be stored as a hash width a strong one way hasing algorithm and should never be encrypted for decryption for later use.
answered Nov 22 at 15:17
fstam
366213
add a comment |
I'm personally using RSACryptoServiceProvider
from System.Security.Cryptography. This is available in .NET standard. Doesn't need any nuget packages either.
using System.Security.Cryptography;
Edit:
I should add to this that encrypting/decrypting password is never a good idea. Password should be stored as a hash width a strong one way hasing algorithm and should never be encrypted for decryption for later use.
answered Nov 22 at 15:17
fstam
366213
I'm personally using RSACryptoServiceProvider
from System.Security.Cryptography. This is available in .NET standard. Doesn't need any nuget packages either.
using System.Security.Cryptography;
Edit:
I should add to this that encrypting/decrypting password is never a good idea. Password should be stored as a hash width a strong one way hasing algorithm and should never be encrypted for decryption for later use.
answered Nov 22 at 15:17
fstam
366213
answered Nov 22 at 15:17
fstam
366213
answered Nov 22 at 15:17
fstam
366213
answered Nov 22 at 15:17
fstam
366213
366213
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53432999%2fnetstandard-nuget-packages%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
Uh...what kind of passwords are you encrypting?
– John
Nov 22 at 14:23
5
Uh... Why would you want to decrypt passwords?
– Deblaton Jean-Philippe
Nov 22 at 14:25
Uh... to create a login form
– NodeCode
Nov 22 at 14:40
Asking for recommendation (packages) is off-topic. You cannot change target frameworks freely, as different project types have their own options, blog.lextudio.com/…
– Lex Li
Nov 22 at 15:28