The previous version we use the Embedding resources to deploy the files. At run-time, when the first hit comes to the page, CuteEditor control will check for the needed files,images, and as it won't be there, it will create the folder and extract files from assembly.

 

In order to save files on the server, the ASPNET account must have disk write permissions on the destination folder. We received lots of feedbacks and compaints about the feature because it needs to give ASPNET account write permission to the server. If the ASPNET account doesn't have disk write permissions on the destination folder, the user will get an Access is denied error message.

We abandoned the Embedding resources idea completely in the version 3.0. Now the CuteEditor can be installed by simply copying the required files to the target machine.