Skip to content
This repository has been archived by the owner on Sep 14, 2022. It is now read-only.

EpiCode.23Video.dll contains Null Public Key Token #11

Open
Yogesh2291 opened this issue Sep 16, 2019 · 10 comments
Open

EpiCode.23Video.dll contains Null Public Key Token #11

Yogesh2291 opened this issue Sep 16, 2019 · 10 comments

Comments

@Yogesh2291
Copy link

After successful run of 23 video connector on local machine , when we trying to deploy on our testing environment then we found, only two Dlls (23API.dll and DotnetOpenAuth.dll) are deploying correctly. Third one EpiCode.23Video.dll is not going with deployment.

We analyzed the issue and found that both Dlls (23API.dll and DotnetOpenAuth.dll) have public key token value while the EpiCode.23Video.dll does not have any public key token. public key token is showing null value for EpiCode.23Video.dll.

-> does not contain public key token

Could you please let us know the EpiCode.23video.dll is private assembly or does contain any public key token value?

As EpiCode.23video.dll contains null public key token , so we can not deploy it on other environment ? is it this reason behind this issue ?

Please help to understand

@tomahg
Copy link
Contributor

tomahg commented Sep 16, 2019

So EpiCode.23Video.dll is omitted from the deployment? How are you running your deployment?

Can this be a solution?
https://stackoverflow.com/questions/2947017/reference-dll-file-not-copying-to-bin-with-deployment-project-causing-error

@Yogesh2291
Copy link
Author

Hi Tom,

Thanks for the reply!

We already tried the steps given in the link you have shared, the two dll which have public key are deployed and available in the bin folder but the one without public key (EpiCode.23Video.dll) is not deployed when deployment is done.

I'm assuming issue is related to private dll, as the other two dll having public key is deployment and the one which is private is not deployed. or it related to something else?

@tomahg
Copy link
Contributor

tomahg commented Nov 1, 2019

When you build the solution on your local computer, the dll ends up in your bin folder, right?

What kind of deployment are you doing, that makes the dll disappear? Azure DevOps Pipelines, TeamCity/Octopus deploy, xcopy...?

@Yogesh2291
Copy link
Author

Yogesh2291 commented Nov 1, 2019 via email

@tomahg
Copy link
Contributor

tomahg commented Nov 1, 2019

Do you have the Copy Local = True for EPiCode.23Video.dll?

@Yogesh2291
Copy link
Author

Yogesh2291 commented Nov 1, 2019 via email

@suwayya
Copy link
Contributor

suwayya commented Nov 1, 2019

Hi @Yogesh2291
I've added signing to the 23Video project. This will hopefully fix your problem.

@Yogesh2291
Copy link
Author

Yogesh2291 commented Nov 18, 2019 via email

@tomahg
Copy link
Contributor

tomahg commented Nov 18, 2019

@Yogesh2291 : Vidar has updated the code, so that the EpiCode.23Video.dll will be signed and thus get a public key token.

Please try again.

Regards,
Tomas

@dss-web dss-web deleted a comment from VidarMa Nov 18, 2019
@suwayya
Copy link
Contributor

suwayya commented Nov 20, 2019

@Yogesh2291 visual studio should add the public token for you when you reference it now since the dll is signed after build. If you still have problems you can open "Developer Command Prompt for VS" and use this command:
sn -Tp ./EPiCode.23Video.dll
You will then get an output containing the public key and the public key token.

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

3 participants