Has anyone managed to deploy a custom assembly that involves calls to System.Data.SqlClient and System.Configuration (to get the connection string for the database)?
I've been fighting this one for a day or two and know that the answer means finding the right mix of asserting permissions in the assembly and granting them in config files. It seems that MS have tied down the security aspects
of this so as to make the facility almost unusable! I'm using Windows 7 Professional
64, SQL Server 2008 R2 (Express) and Visual Studio 2010 for
development. Yet the documentation is sparse - to say the least.
Does anyone know of a document that will tell me what to do?
View Complete Post