Template10: Microsoft.Xaml.Interactivity - strongly-named assembly

[mvermef]

Could not load file or assembly 'Microsoft.Xaml.Interactivity, Version=1.1.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. A strongly-named assembly is required. (Exception from HRESULT: 0x80131044)

Seeing this on building projects off the code in git..

[callummoffat]

So, you're only seeing this when building from the Git code?

Have you tried getting the latest code? I believe there was a strong-naming fix at some point recently.

[mvermef]

its the absolute latested code, and it was happening yesterday source as well. First time since the initial

[callummoffat]

I think I know what the problem might be. I'm no expert, but is it possible that a strong-named assembly isn't being created when you compile the code from Github? It would explain the error (which I'm not receiving using 1.1.10 Nuget).

[mvermef]

you are saying with respect to the Template10 strong name?
tried that as well and to no avail.

[mvermef]

I hard reset my source and it has it selected with the key in the root of the library

[callummoffat]

Not quite following. Are you saying that you are having this issue with the new Nuget package as well?

[mvermef]

yes

[callummoffat]

I think it might be to do with your app, and not Template10 itself. Like I say, I'm having no issues with it.

[callummoffat]

Take a look in the project.json for your app. Have you updated the Behaviors SDK reference to 1.1.*? Because T10 1.1.10 now supports this as the baseline, and if you're basing your app of an older template, it won't have this configured correctly.

[mvermef]

yes

[callummoffat]

So you have updated the reference, and that's not the cause of the problem?

Well, I'm stumped. @JerryNixon, do you have any ideas?

[mvermef]

went back to project to 1.1.10 and it updated latested without issue and no warnings about strong name, but compiled source not so lucky

[callummoffat]

Still having trouble following, so correct me if I'm wrong, but when you use the 1.1.10 Nuget package, you have no problems, but using the Github sources, you get a strong name error?

[mvermef]

ok, so the nuget compiles without warnings or errors
Neither build without that warning...
Source on git doesn't

[mvermef]

1>C:\Program Files (x86)\MSBuild\Microsoft.NetNative\x86\ilc\IlcInternals.targets(936,5): warning : ILTransform_0000: MCG : warning MCG0006: Unresolved P/Invoke method 'sysctl!libc' in assembly 'Microsoft.Extensions.PlatformAbstractions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' because it is not available in UWP applications. Please either use an another API , or use [DllImport(ExactSpelling=true) to indicate that you understand the implications of using non-UWP application APIs.
1>C:\Program Files (x86)\MSBuild\Microsoft.NetNative\x86\ilc\IlcInternals.targets(936,5): warning : ILTransform_0000: MCG : warning MCG0006: Unresolved P/Invoke method 'uname!libc' in assembly 'Microsoft.Extensions.PlatformAbstractions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' because it is not available in UWP applications. Please either use an another API , or use [DllImport(ExactSpelling=true) to indicate that you understand the implications of using non-UWP application APIs.
1>C:\Program Files (x86)\MSBuild\Microsoft.NetNative\x86\ilc\IlcInternals.targets(936,5): warning : ILTransform_0000: MCG : warning MCG0006: Unresolved P/Invoke method 'RtlGetVersion!ntdll' in assembly 'Microsoft.Extensions.PlatformAbstractions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' because it is not available in UWP applications. Please either use an another API , or use [DllImport(ExactSpelling=true) to indicate that you understand the implications of using non-UWP application APIs.
1> Generating serialization code

native tool chain warnings...

[darshanrampatel]

I'm seeing this as well with the Nuget version - I've updated my project.json to "Microsoft.Xaml.Behaviors.Uwp.Managed": "1.1.*",

I get an exception when it first runs:
Exception {"Layout cycle detected. Layout could not complete.\r\nLayout cycle detected. Layout could not complete."} System.Exception {Windows.UI.Xaml.LayoutCycleException}

[darenm]

@darshanrampatel I suspect that is caused by an instance of EllipsisBehavior in your initial view - remove that behavior from your PageHeader control if you have it and try again.

[darenm]

So I also see an issue with the error related to strong-named assembly for the Behaviors. It manifests as "blue wigglies" in the designer - mousing over gives the error:

[darshanrampatel]

@darenm Yes, that was exactly it! Thanks.

[Ahaituka]

I am also having the same problem with the nuget version of template 1.1.10. .But when i updated all my packages Earlier it was working fine but now its giving me blue underline over any control and when hovered the intellisense displays:
Could not load file or assembly 'Microsoft.Xaml.Interactivity, Version=1.1.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. A strongly-named assembly is required. (Exception from HRESULT: 0x80131044)

But weird thing is that my app is deployed and its running!

[mvermef]

YES!!!, now I am also seeing namespaces for the Template10 being blue wiggled... Saying it doesn't exist, I cleaned and recompiled (release) the 1.1.10 source code. Controls, Behaviors, Common, etc.

[darenm]

Ultimately I suspect this is an issue caused by the Behaviors team electing to StrongName - there is a thread here on their repo: Behavior Strong Naming Thread

[JerryNixon]

Good work. I am closing this, though I have money on how many hours until an identical one is opened :)

[dubstylee]

Why is this closed? It isn't fixed to my knowledge? I am having the same issue and do not have EllipsesBehavior, am referencing the correct 1.1.0 Behaviors, and have cleaned/rebuilt/refresh/restarted/re-added reference to Behaviors, and still having the same issue. The application works fine, but basically makes the Designer useless for any pages with a PageHeader.

[callummoffat]

This is closed because it isn't actually a Template 10 issue. It's to do with the Behaviors package, and a decision they made recently. They enabled strong-naming for behaviors for some reason, and it's causing issues. There's not much we can do about it, except hope that the Behaviors team resolves this somehow.

[IIARROWS]

I disagree: Template 10 1.1.10 requires Behaviors 1.1.0, so I cannot update Template 10 without this really unpleasant collateral effect.

I still have to use 1.1.8 and Behaviors 1.0.3, if I want an header on my views.

[dubstylee]

The header still works fine in the application at runtime, you just cannot get a preview in the designer is all.

On Apr 24, 2016, at 11:39 AM, IIARROWS [email protected] wrote:

I disagree: Template 10 1.1.10 requires Behaviors 1.1.0, so I cannot update Template 10 without this really unpleasant collateral effect.

I still have to use 1.1.8 and Behaviors 1.0.3, if I want an header on my views.

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub

[IIARROWS]

Yes, I understand that, but is very annoying to read a XAML view when everything has that wiggly underline and it's hard to make changes.

It's not a blocking issue, but I still consider it an issue that is not unrelated to Template 10 until it's used and forced by Template 10.

[mvermef]

One other thing to look at is that XamlBehaviors is also built on the lower dependency of 5.0 for Microsoft.NETCore.UniversalWindowsPlatform, not that it make much difference. The other question to ask was there a pressing need or I missed the conversation to actually pushing forth to 5.1 and 1.1.0 respective? Everything seem to function correctly as we would have expected from the lower versions.

[JerryNixon]

This behavior SDK thing is making me so frustrated.

[mvermef]

What is even more infuriating is that it is not occurring any longer at least on my 2 projects, it's very strange.

[aline-almeida]

I've started a new project with Nuget & hamburguer template. project.json looks right as described in

856 , cleaned & rebuilt. Still seeing this error and designer is blank...

[callummoffat]

I've started getting this too. Curse you, Behaviors Nuget 1.1.0!

[alexdresko]

Just FYI, if I click this button, the designer appears again, albeit without design time data...

I assume that button's purpose is to disable design time data, although the tool tip isn't extremely helpful in that regard. It was a totally random fluke that I stumbled across that button and it's affect on the designer related to this problem.

Hope that helps someone. In the meantime, I'm going back to the old T10.. Design time data makes the other devs jealous.

[affans]

So does anyone have a temporary solution to this? I just started learning UWP and its difficult to go through the code.

[callummoffat]

Try turning off design-mode data, and see if it helps.

_Callum Moffat_
App Developer
Windows 10 Enthusiast

---

Keep track of the costs of your vehicles with Petrolhead!
https://www.microsoft.com/en-us/store/apps/petrolhead/9nblggh1rjqt?cid=phmailsig

On Fri, Apr 29, 2016 at 11:12 AM, Affan [email protected] wrote:

So does anyone have a temporary solution to this? I just started learning
UWP and its difficult to go through the code.

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/Windows-XAML/Template10/issues/860#issuecomment-215589415

[callummoffat]

OK, I'm getting really annoyed. I realize this problem was not intentional, and that there are real benefits to using Behaviors 1.1.0. But I have to say, this strong-naming issue is really working my last nerve.

[jonwchu]

It looks like with a recent commit strong naming was turned on in T10, however strong naming was turned off with the latest release of Behaviors (v 1.1.0). Is it possible this might be causing some of the issues?

[callummoffat]

That could be it, actually. Brilliant!

_Callum Moffat_
App Developer
Windows 10 Enthusiast

---

Keep track of the costs of your vehicles with Petrolhead!
https://www.microsoft.com/en-us/store/apps/petrolhead/9nblggh1rjqt?cid=phmailsig

On Fri, Apr 29, 2016 at 12:36 PM, Jon W Chu [email protected]
wrote:

It looks like with a recent commit
https://github.com/Windows-XAML/Template10/commit/501ff9d1b6427d2c2d29b7c6c0445e9548d283c3
strong naming was turned on in T10, however strong naming was turned off
with the latest release of Behaviors (v 1.1.0). Is it possible this might
be causing some of the issues?

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/Windows-XAML/Template10/issues/860#issuecomment-215602021

[IIARROWS]

@affans in the meantime, downgrade to template 10 1.1.8 and download behavior 1.0.3.

[sebfrie]

In this case, could someone please revert the mentioned commit asap (and upload a new nuget package)?

[callummoffat]

Hey @JerryNixon,

Looks like a new thread has been opened on this topic (#904). Took longer than I thought it would, actually.