What are the contents of "this file" and its dependencies?
This is script for generate string (access key for program). I must connect to C# class (dll files). (On my computer all is ok)
But first I want to test .NET integration on my server.I had implemented simple script (display all drives info from computer: use System.IO.DriveInfo .NET class). (but none of them works on the server).
Content of "this test file":
<!--- Create a .NET System.IO.DriveInfo object. --->
<cfobject type=".NET" name="sidiClass" class="System.IO.DriveInfo">
<!--- Get the drives. --->
<!--- Loop through drives. --->
<cfloop from="1" to="#ArrayLen(drives)#" index="i">
<!--- Add a row to the query.--->
<!--- Get the drive name, type, and ready flag. --->
<cfset QuerySetCell(result, "name", drives .Get_Name())>
<cfset QuerySetCell(result, "type",
<cfset QuerySetCell(result, "isready", drives .Get_IsReady())>
<!--- Get extra details ONLY if the drive is ready. --->
<cfset QuerySetCell(result, "format", drives .Get_DriveFormat())>
<cfset QuerySetCell(result, "label", drives.Get_VolumeLabel())>
<cfset QuerySetCell(result, "totalsize", drives .Get_TotalSize())>
<cfset QuerySetCell(result, "freespace",
Some things to check or try
1. Permissions, verify that the account the ColdFusion services run as have permissions to the files and directories containing the .NET framework.
2. Paths. I notice that your production server has web code on a different drive. You might try using the assembly attribute of cfobject to specify the full path to the DriveInfo class. I realize that since it is part of the global assembly cache this shouldn't be required, but I would try it.
I tryed it and nothing....
ColdFusion server and ColdFusion .NET integration services launched with administrator permissions.
I tryed connect to another class, connected to dll and exe files with .NET class.
Even, I tryed install ColdFusion on another computer and all was OK only on my server is something wrong. (I can't reinstall ColdFusion on the server).
When you installed the .NET framework on the new server, was there already an earlier version of the .NET framework on the server? Also did you install the CF/.NET integration service before or after installing .NET v. 3.5? I ran into this problem before on a server that had the .NET integration service installed and .NET framework v 2.0...upgrading the .NET version to 3.5 caused the problem, since the ColdFusion .NET integration service had configured itself to use the earlier version of the .NET framework. Uninstalling and then reinstalling ColdFusion .NET integration service fixed the problem in my case.