I have worked on this error message for a while until i realized that it was caused by the system not having .NET 2.0 sp2 installed.
I kept getting this error message when tried running a custom exe file from a shared drive or a mapped drive.
I would however appreciate if Microsoft would have given me an error message that makes more sense though.
Migrating well established programs such as WordPress, Joomla from one server to another can be daunting task. After you make sure that all the PHP and Apache extensions are installed and your server is ready to go, you finally come to the point where you have to move the sites themselves. You have to worry about moving the files, change permissions, move the database(s) and so forth. Having a single configuration file will help you save a lot of time and frustrations since you will not have to chase connections strings all over the place.
Here is a good article on the subjects
http://www.ibm.com/developerworks/library/os-php-config/index.html
Also look at the source code of established open source projects; this will help you make decisions on how to handle the configuration variables.
Other Related Links
http://php.net/manual/en/function.define.php
1. First Download Power Shell
http://support.microsoft.com/kb/968929
2. Follow the instructions in the following website
http://www.ehow.com/how_5836904_install-windows-powershell.html
3. To launch PowerShell just click start run type "POWERSHELL"
Reference and Resources
http://technet.microsoft.com/en-us/scriptcenter/dd742419.aspx
I wrote a program recently that needed to be run from 10 different computers simultaneously. I kept on copying the source code to all 10 computers until the idea of centralizing the code hit me one night. Well instead of copying all the source why not have the source code on one location and simply call the exe from the clients. In the past, one use to just copy the source code to the network drive and did not have to worry too much about permissions and security.
With the .NET Framework one has to explicitly give permission to run program from the shared drive and here are the instructions.
1. Go to control panel -> administrative Tools -> Microsoft .net configuration …
2. Right Click on the "Runtime Security Policy" and click on "Adjust"
3. Give Full Trust to Local Intranet
4. Then Finish and Voila
One thing for sure, we will be revisiting a post such as this one to add more information as we continue to research the subject matter. Our stored procedures have always been transact-sql until about two years ago when we discovered that we could do a lot of things with CLR.
The concept is great and can be used in a lot of scenarios.
Why using one instead of the other?
For simple situations where performance is not an issue and you do not have to deal with too many DML statements, CLR should be your best choice.
For situation when you have to do complex operations (strings and others) CLR is good option.
Other than that you can continue to use Transact SQL.
Anyhow you can always use a combination of both, if you still confused.
Reference
http://msdn.microsoft.com/en-us/library/ms345136%28SQL.90%29.aspx
