Choosing the .ascx extension for a config file is a poor decision. My WebSites can't be built anymore with version 1.1.
Most of my Visual Studio solutions use the "WebSite" project. The thing with "WebSite projects" is that you cant really prevent a file residing into the projects directory from being added to the project (there are some solutions but none of them fit my needs). For that reason config.ascx is automatically added in the WebSite and guess what? config.ascx produces several build error and my Solutions cannot be built.
Moreover config.ascx prevents me from precompiling my websites. If I can't precompile my code, I have to upload the source to ftp sites which is highly undesirable.
Most of my Visual Studio solutions use the "WebSite" project. The thing with "WebSite projects" is that you cant really prevent a file residing into the projects directory from being added to the project (there are some solutions but none of them fit my needs). For that reason config.ascx is automatically added in the WebSite and guess what? config.ascx produces several build error and my Solutions cannot be built.
Moreover config.ascx prevents me from precompiling my websites. If I can't precompile my code, I have to upload the source to ftp sites which is highly undesirable.
But, looking at your problem, there should not be any issue on having ckfinder.ascx as part of the Web Site compilation. All you need, is having the CKFinder.dll file in your bin folder (being a reference in the VS project). This is in any case a requirement for CKFinder to run.
So, I would recommend you just adding CKFinder.dll in the references of your project.
Frederico Knabben
Project Lead for CKEditor
CEO at CKSource