Well, I think we can all agree that this is a problem with the HTML editor. I'm just not sure what file it's trying to access that's path is too long. Could you check your web.config file to see what HTML editor you are using? Also, while you're in there, see if you have any additional providers registered. If so, you might want to try changing to another one and see if that helps any.

---

Michael Flanakin | Microsoft Consulting Services
www.michaelflanakin.com

The error being discussed in this thread is quite common when you use the System.IO namespace and encounter paths/files that exceed the 260/248 character length limitations. Any .Net code that calls a System.IO class method will cause this error to be thrown. In the case of the editor, it is to be expected since most editors extract embedded resources either from the primary assembly or satellite resource files. Just about any System.IO action such as enumerating a directory, opening a file, writing to a file will cause the error to be thrown.

The character limitation is an artificial one that Microsoft put in .Net (no idea why). The actual Windows limit is 32,000 characters. When encountering this issue, a .Net developer can put a COM wrapper around their assembly and circumvent the error. However, this is in extreme situations and it is unlikely any developer will do this normally as the performance hit is severe and is likely to cause other grief.

As already proposed earlier in the thread, the solution for this scenario is to move the project from the VS.Net default folder into another folder with a shorter path. One far-fetched alternative is to use XP Folder Redirection but I doubt it will work very well.

Nik

 

---

Nik Kalyani
Co-founder
DotNetNuke Corporation
Blog | Twitter | FaceBook

Well, I tried moving it up in the directory again and wahlah! It works.

Thanks to everyone for their help!

-Trisha