Securety exception on browse

Thank for your post: it keept me from trouble while deploying a .net site that uses the FCK editor at godaddy.com. Nevertheless, I feel your original post lacked detailed steps to achieve its proposed solution. Therefore, I'd post the steps I followed to solve this issue. The main tasks involded to solve this issue are:

- Edit the source code of the FCKEditor .NET dll
- Recompile the FCKEditor .NET dll
- Refresh the FCKEditor .NET dll in the project that is giving problems

To accomplish these tasks the following is required:

- Access to the source code of the FCKEditor .NETdll (In my case C#)
- Means to compile .NET assemblies (In my case Visual Studio 2005 and Visual Studio 2003)

At the time of this writing the current version of the .NET source files for the FCKEditor is 2.2. Open the Project file FredCK.FCKeditorV2.csproj with VS 2003 (If a security message appears, simply disregard it). Open the file Util.cs and comment out or delete lines 30 and 31; that is :

[DllImport("msvcrt.dll", SetLastError=true)]
private static extern int _mkdir(string path) ;

Next comment out or delete from lines 54 to 78 inclusive, that is:

ArrayList oDirsToCreate = new ArrayList() ;

         // Create the directory info object for that dir (normalized to its absolute representation).
         DirectoryInfo oDir = new DirectoryInfo( Path.GetFullPath( path ) ) ;

         // Check the entire path structure to find directories that must be created.
         while ( oDir != null && !oDir.Exists )
         {
            oDirsToCreate.Add( oDir.FullName ) ;
            oDir = oDir.Parent ;
         }

         // "oDir == null" means that the check arrives in the root and it doesn't exist too.
         if ( oDir == null )
            throw( new System.IO.DirectoryNotFoundException( "Directory \"" + oDirsToCreate[ oDirsToCreate.Count-1 ] + "\" not found." ) ) ;

         // Create all directories that must be created (from bottom to top).
         for( int i = oDirsToCreate.Count - 1 ; i >= 0 ; i-- )
         {
            string sPath = (string)oDirsToCreate[i] ;
            int iReturn = _mkdir( sPath ) ;

            if ( iReturn != 0 )
               throw new ApplicationException("Error calling [msvcrt.dll]:_wmkdir(" + sPath + "), error code: " + iReturn );
         }

Then Insert the following line of code right after the above code and just before the return statement of the function:

System.IO.Directory.CreateDirectory(path);

In my case the new Util.cs file looks like this:

/*
 * FCKeditor - The text editor for internet
 * Copyright (C) 2003-2005 Frederico Caldeira Knabben
 * 
 * Licensed under the terms of the GNU Lesser General Public License:
 *       http://www.opensource.org/licenses/lgpl-license.php
 * 
 * For further information visit:
 *       http://www.fckeditor.net/
 * 
 * "Support Open Source software. What about a donation today?"
 * 
 * File Name: Util.cs
 *    Useful tools.
 * 
 * File Authors:
 *       Frederico Caldeira Knabben (fredck@fckeditor.net)
 */

using System ;
using System.Runtime.InteropServices ;
using System.IO ;
using System.Collections ;

namespace FredCK.FCKeditorV2
{
   public sealed class Util
   {
      private Util()
      {}

      public static DirectoryInfo CreateDirectory( string path )
      {
         System.IO.Directory.CreateDirectory(path);
         return new DirectoryInfo( path ) ;
      }
   }
}

Save changes to the file and then rebuild the solution. You will then find a new dll in the bin directory of the FCKEditor application. Depending on the mode the FCKEditor solution was rebuilt on the new dll will either be found in the bin's Release or the Debug directory. Grab that dll and replace the previous version that was being used in the problematic project. A simple cut and paste should do the trick .

IMPORTANT: the custom CreateDirectory function is there to counter attack on a known issue with the System.IO.Directory.CreateDirectory function. Therefore, this solution might have secondary effects.

Hope this info saves someone some time and effort.

Cheers and happy programming,