Hi I have a requirement to apply security filtering (column and row level) above and beyond the capabilities of SSRS Model security. in 2005 and 2008 I achieved this by creating a data Extension and tweaking the Command text and execute reader methods, and all was Well with the world. Now all I wanted was a bit of customisation of the SQL data Extension (SQL Connection Wrapper)... of course its Sealed so couldn't inherit, so I composite / wrapped it... and all was well with the world...... Now along comes SQL2008 R2 .... and someone has discovered the internal Keyword ! now everything is locked down. the Constructor of SQL Connection Wrapper is internal. Luckily my code is not yet producion code, and I know Microsoft are completely within their rights ... but why!!! ... all is not good with the world, I doubt I am alone in this !
Any suggestions how to implement a minor customisation to SQL data Extension, without reimplementing the whole of the dataExtensions DLL !
Any chance the decison might be reversed ?
View Complete Post