Use of Html namespace breaks @Html. Intellisense in MVC views about htmlsanitizer

[tiesont]

I'm using the NuGet package in MVC4 & MVC5 projects, and I see the normal HtmlHelper extensions in my views. Did you add the HtmlSanitizer namespace to your web.config?

[jhasselkus]

No, the HtmlSanitizer namespace isn't added to web.config. And I should also note that the problem comes and goes. I just noticed that it went back to normal after restarting Visual Studio. But I've been seeing this on and off ever since I started using HtmlSanitizer about a month ago.

[tiesont]

I'm using the Professional SKU, with Update 2 installed, and I can't recall seeing that behavior.

If @mganss doesn't have the time to look into this, or simply would prefer not to change the namespace, it's always an option to create a fork and modify the namespace. I could even create a "no conflict" NuGet package, if he didn't mind.

[mganss]

Using "Html" as the namespace name was a bad decision. I'd change it to something else right away but I'm afraid that this will break things for people already using the assembly from NuGet.

A workaround might be to use a using directive in your views or web.config, e.g.

@using XSS = Html

or

<add namespace="XSS=Html" />

I haven't tested either, so not sure if this works.

[jhasselkus]

While changing the namespace is a breaking change, it's such an easy fix that it seems worth it. But I need the change, so I'm biased. :)

Thanks for the ideas, I'll try those when it stops working again.