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

Do we have strong named version of Neutronium ? #89

Open
Bjaris opened this issue Oct 4, 2018 · 3 comments
Open

Do we have strong named version of Neutronium ? #89

Bjaris opened this issue Oct 4, 2018 · 3 comments

Comments

@Bjaris
Copy link

Bjaris commented Oct 4, 2018

Hi,

I faced a nasty issue trying to integrate Neutronium HTMLViewControl control in a WPF user control. I Could not compile due to an error in my XAML => CS0234 The type or namespace name 'WPF' does not exist in the namespace ...).
I finally tried a work around by defining a HTMLViewControl derived class defined in my assembly to help WPF in namespace resolution.
I realized then that Neutronium assemblies are not strong named and my assemblies are (cyber security constraint)
I have rebuilt and strong named with my own key a Neutronium subset (without tests & samples) and succeed to compil but still no luck with native class.
May be I did not properly strong named Neutronium assemblies and I am still not sure if the root cause is linked to that.
The application sample is just working fine with the same user control even if the application is strong named.

  • Any idea on the root cause ?
  • Do you think it makes sense to have nuggets with strong named assemblies ?

Regards

@Bjaris Bjaris changed the title Is it possible to have nuggets with strong named version of Neutronium ? Do we have strong named version of Neutronium ? Oct 5, 2018
@Bjaris
Copy link
Author

Bjaris commented Oct 11, 2018

Answering to myself only for the XAML error aspect.
Seems it is a WPF bug linked to namespace i.e. 2 files are generated a .g.cs & .g.i.cs. Seems my namespace was ambigous and the generated code contained the wrong using.
Changing my wpf control namespace so it does no more collide with Neutronium.WPF namespace solved this issue i.e. the using was correctly generated.
However I still need strong named assemblies. For the moment I justed make my assembly non strong named.
Regards

@David-Desmaisons
Copy link
Member

Hello @Bjaris , regarding the strong named assemblies, this is not something I intend to do in the short/mid-term.
Why do you need this feature?

@Bjaris
Copy link
Author

Bjaris commented Oct 16, 2018

Hi David,
reasons are similar to the ones exposed in this article
https://joshuachini.com/2017/07/12/how-to-assign-a-strong-name-to-unsigned-3rd-party-assemblies-during-the-build-process/
I did not test this StrongNamer nugget package and if it works it can be a solution.
However I have the feeling that for mere cyber security reasons the Nugget should be sign with your snk as you are the author.
For the moment this feature is not urgent as :

  • I am still trying to have Neutronium working as a web control in a WPF view.
  • We have some alternate solution i.e. Gecko, CefSharp but Neutronium has more potential !!!
    Anyway many thanks for all your works.
    Regards

@Bjaris Bjaris closed this as completed Oct 16, 2018
@Bjaris Bjaris reopened this Oct 16, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants