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

PFX signing not supported on .NET Core for .Net Core 3.1 #9

Closed
DiegoAndreColli opened this issue Feb 28, 2020 · 8 comments
Closed

PFX signing not supported on .NET Core for .Net Core 3.1 #9

DiegoAndreColli opened this issue Feb 28, 2020 · 8 comments

Comments

@DiegoAndreColli
Copy link

I'm trying to make it compile in my machine, I have .Net Core 3.1 installed, and I'm receiving the following errors... I tried some workaround but without success, do you know the cause? Thanks for your work.

Microsoft.Common.CurrentVersion.targets(3222, 5): PFX signing not supported on .NET Core
NuGet.Build.Tasks.Pack.targets(198, 5): [NU5026] The file 'C:\projects\Grabber\src\SharpGrabber\bin\Debug\netstandard2.0\SharpGrabber.dll' to be packed was not found on disk.

@javidsho
Copy link
Contributor

Please clarify whether you are having problems with the SharpGrabber library or the desktop application.

@DiegoAndreColli
Copy link
Author

It is an application problem, since I can remove the project, delete desktop folder and the error is the same.

@javidsho
Copy link
Contributor

javidsho commented Feb 29, 2020

I could not reproduce your problem, but I think you can easily get rid of this error.
In Visual Studio, navigate to project properties for SharpGrabber. Go to Signing section and uncheck "Sign the assembly". You should be good to go.

If it didn't solve your problem, please provide me with steps to reproduce.

P.S. Also don't forget to set SharpGrabber.Desktop as the startup project.

@javidsho
Copy link
Contributor

I guess it was a configuration problem. I have updated the repo. If you pull or check out again, the problem should be solved.

@DiegoAndreColli
Copy link
Author

Oh, sorry for not mentioning it before, but I'm using rider not visual studio, maybe that is the reason

@javidsho
Copy link
Contributor

javidsho commented Feb 29, 2020

No problem. It's exactly the same for Rider. I just checked out the repo again and I saw no problem at all. You just make sure that the "sign the assembly" option in SharpGrabber project properties is not checked.

@javidsho
Copy link
Contributor

So, did it work after all?

@DiegoAndreColli
Copy link
Author

DiegoAndreColli commented Mar 1, 2020

Well. Yes I guess, now I have Microsoft.Common.CurrentVersion.targets(1175, 5): [MSB3644] The reference assemblies for .NETFramework,Version=v4.6.1 ... bla bla bla... Rider does not work well with global.json (In order to use the correct version when compile) so to be honest, I ended using another library, but thank you anyway, sorry if I was not of great help.

@javidsho javidsho closed this as completed Jul 1, 2020
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

2 participants