Sometimes these strange error messages occur because the ASPNET worker process does not have the proper permissions to access a DLL which may reside in a different directory. I would recommend checking this by stepping through the code and check the System.Security.Principal.WindowsIdentity.GetCurrent().Name property. And then make sure that id has proper permission to access the directory where the DLL resides.

In the webconfig file, you may also try setting identity impersonate to true.

The object model of .Net can be overwhelming at times – so overwhelming that quite trivial tasks often take hours of research. In this case, the task at hand was to populate the datagrid from SQL Server database in Visual Studio 2008 Windows applica…

Recently while returning home from work my wife (another .NET developer) was murmuring something. On further poking she said that she has been assigned a task where she has to serialize and deserialize objects and she is afraid of serialization. Wha…

Access reports are powerful and flexible. Learn how to create a query and then a grouped report using the wizard. Modify the report design after the wizard is done to make it look better. There will be another video to explain how to put the final p…

This video demonstrates how to create an example email signature rule for a department in a company using CodeTwo Exchange Rules. The signature will be inserted beneath users' latest emails in conversations and will be displayed in users' Sent Items…