Error 30 The tag 'BrokenRuleSeverityConverter' does not exist in XML namespace in version 3.6.0 compile

dennism posted on Thursday, January 15, 2009

Error 30 The tag 'BrokenRuleSeverityConverter' does not exist in XML namespace 'clr-namespace:Csla.Wpf'. Line 9 Position 18. C:\cslacs\Csla\Themes\Generic.xaml 9 18 Csla

when compiling version 3.6.0

but intellisense on csla: shows the class BrokenRuleSeverityConverter

anyone have solution?

have vs 2008 with 3.5 sp1 installed...

RockfordLhotka replied on Friday, January 16, 2009

I don't know the cause of this. I do remember seeing it from time to time while we created 3.6, but it was usually due to some other code issue that caused a compilation failure, and this was an erroneous message. I suspect Microsoft has some work to do in terms of how the build process incorporates XAML and C# together.

MTmace replied on Wednesday, February 04, 2009

I am getting the same error.
I just installed .net 3.5 with service pack one so I can build the CSLA 3.6 framework and got a build error.
The tag 'BrokenRuleSeverityConverter' does not exist in XML namespace 'clr-namespace:Csla.Wpf'.
The error is occurring in Generic.xaml in the Themes directory.

I think the error may have to do with the fact the CSLA.dll files does not exist. Once I remove the Generic.xaml file from my project I get a different error the prevents me from compiling the project. Cryptographic failure while signing assembly.
So I think the solution is to create a new key using sn.exe.

RockfordLhotka replied on Wednesday, February 04, 2009

This exception typically occurs for one of two reasons:

1. You don’t have VS 2008 SP1 and/or .NET 3.5 SP1 properly installed

2. There’s some other build issue in the solution, and this is an erroneous error

Rocky

MTmace replied on Thursday, February 05, 2009

I just installed VS 2008 sp 1 and I still have the Cryptographic failure while signing assembly.
Do I need to create a new key or can I remove the key?

MTmace replied on Thursday, February 05, 2009

Actual error:
Cryptographic failure while signing assembly '' Access is denied

I found a solution to the problem:
http://blog.devstone.com/aaron/archive/2005/12/01/1365.aspx

I had to open an explorer window and navigate to following directory:
C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\MachineKeys

Then select Tools - Folder Options
Select the "View" tab
Scrolled to the bottom of the page and deselected "Use simple file sharing".

This gave me a security tab when I right clicked on the "MachineKeys" folder and went to properties.
When the security tab is selected I gave the Administrators group full access to the "MachineKeys" directory.

Then I was able to build the cslacs project.

MTmace

v3rt1g0 replied on Friday, March 20, 2009

I'm not sure if this will help you, but it helped me.

We have some legacy CSLA code (1.x era) that we use with ASP.NET 2.0 and to allow simple debugging we needed to workaround an authentication issue we were having. The workaround involved modifying c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\config\machine.config file to include a <developmentMode developerInstallation="true" /> line. While this is "true" and the matching system variable was set to a path containing the old version of CSLA.dll, we would get this exact BrokenRuleSeverityConverter error when trying to compile the new DLLs. Simply setting this back to "false" (the default), made the issue go away for me.