1
Vote

Prism.Interactivity break IntelliSense

description

Repro :
  • add the Interactivity reference to your project (for example a class library).
  • in a XAML file (for example a UserControl), try to add the namespace by typing xmlns...
  • you will not have intellisense to complete the path of the namespace (like the prism one : clr-namespace:Microsoft.Practices.Prism;assembly=Microsoft.Practices.Prism)
  • delete the reference to Interactivity and Rebuild
  • retry typing xmlns...
  • you have your intellisense back!
     
    Maybe the Prism.Interactivity 4.1.0.0 wasn't correctly built ?

file attachments

comments

DCherubini wrote Mar 5, 2012 at 7:05 PM

Hi,

We tried to reproduce the error you are mentioning using the latest release of Prism 4.1 in both Silverlight and Desktop applications without success.

It would be helpful if you could provide us with more information regarding the scenario in which this behavior appears: for example, the Silverlight runtime and SDK versions, the Microsoft.Practices.Prism.Interactivity version (you can find it in the Add Reference dialog), any exception or error that appears when building the solution, etc.

Thanks,

Damian Cherubini
http://blogs.southworks.net/dcherubini

Bejarid wrote Mar 6, 2012 at 8:41 AM

Hi,

Thanks for you answer.

I use VS10SP1 and WPF on .Net 4.0. The Prism.Interactivity version is the 4.1.0.0 and I have no error, warning or message when I build my project.

I have try with a new solution, just add a WPF project, try to add a xmlns, no problem I see all the differentes namespaces. I add the reference with interactivity, the xmlns intellisens is broken, I remove the reference, rebuild and the xmlns intellisens is back.

I join my test solution with the interactivity dll (maybe it's corrupted ?), and in my work I use the old way of PRISM 4.0, with the Blend interactivity dll without a problem. But the PRISM one is way lighter and simpler so I would prefere to use it :) And not only the intellisens is broken, the xaml using the ActionCommandInvoke won't compile (VS don't recognize the xml tags).

aadami wrote Mar 7, 2012 at 3:49 PM

Hi,

I could reproduce the issue you are mentioning in a Silverlight application. So far, this problem seem to appear intermittently. Also, I couldn't reproduce the issue using your sample, so it seems that the problem is not related with it.

On the other hand, I found that this behavior was also reported in Prism v4, as you can find in the following thread:

Intellisense not working for Prism Namespaces (http://compositewpf.codeplex.com/discussions/262472)

I my case, when the problem appeared, I could fix it by adding the Microsoft.Expression.Interactions and System.Windows.Interactivity libraries into my project.

I hope you find this helpful,

Agustin Adami
http://blogs.southworks.net/aadami

Sign in to add a comment or to set email notifications