I tried Rebuild, but no luck. At least we have a workaround.

>Pertti,
>
>>I am getting EXACTLY the same error after updating MM.NET from 1.1 to 1.2. As long as we know what the fix is, I guess it is ok albeit annoying.
>
>After giving it some thought, I'm wondering if Rebuilding (vs. Building) the project would also have solved the problem. When you Build a project, it only builds what's been changed. When you Rebuild, it compiles everything.
>
>>I am getting an apparently security related error, though, which I haven't been able to track down, yet (not enough hours in a day to debug an app that used to work fine until framework version update happened...)
>
>By looking at the stack trace it looks like you have specified security for an mmDataGrid control but have not set the form's RequiresSecurity<\b> property to true.
>
>The previous version of MM .NET masked this error (marking controls as secure but not setting the page RequiresSecurity property to true). Would you (lurkers welcome to respond here) prefer that we:
>
>1. Mask the error as in the previous version of MM .NET
>
>2. Provide a more descriptive exception
>
>Regards,