Have you just created a Microsoft .NET application in VB.NET or C# and deployed it to a customer. They install it over the network and all of a sudden, it crashes for no apparent reason and gives no hint as to why?
However, when you run the application locally or on a computer or the one that you developed it on, it works fine.
Granted, you may have something programmed incorrectly like a path to a database or something.
But before pulling your hair out trying to figure out what you did wrong in the programming one thing you may want to check first is the security policy of the .NET framework.
Without the correct permissions, .NET applications may give you a very hard time when running over the network.
Here is Part 1 of the article. For Part 2 of the article Click Here