I have a big problem, after working for several weeks on a new module, I was very happy because it is almost complete. My development environment has been working flawlessly until I tried to publish the Web site to package the module without sources. I do development on my Toshiba tablet with WinXP Pro, it has 1GB of Ram and plenty of disk space. I started with the Dev Kit for 4.3.4 and upgraded along the way to 4.3.5. I have been doing development with IIS locally (instead of Cassini). Like I said before, everything is working great, I can build, debug, etc. without a problem, only when I try to Publish is that I see the error, which displays the following in the Output window:

------ Build started: Project: C:\Inetpub\DNN434Kit\, Configuration: Debug .NET ------
Pre-compiling Web Site

Building directory '/DNN434Kit/App_GlobalResources/'.
Building directory '/DNN434Kit/App_Code/'./: Publication (web): The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.

Pre-compilation Complete
------ Skipped Publish: Project C:\Inetpub\DNN434Kit\, Configuration: Debug .NET ------

========== Build: 0 succeeded or up-to-date, 1 failed, 0 skipped ==========
========== Publish: 0 succeeded, 0 failed, 1 skipped ==========


I have searched everywhere for the file name or path too long error and I did not find anything related to the publish or compilation processes. I did find a couple of references to this error at runtime but nothing at build/compile time. One reference I found (here http://www.eggheadcafe.com/forumarchives/netframeworkaspnet/sep2005/post24135784.asp) mentions a problem introduced in a Windows service pack to prevent attacks via long URLs. I don’t know how this can be related to the Build process but the magic string length number is suspicious, which is 260.

I ran the Publish process while monitoring the file activity with the Sysinternals Filemon tool to see what was going on and found that some paths accessed by VS go up to 200 characters in length, these are the temporary directories located under my profile name in “Documents and Settings”. I also tried to publish after removing many of the big modules from my development install of DNN (like the forums, blog, etc.) but the error still occurred.

Have anybody seen this??? This is kind of critical for me at this moment.

Carlos

Michael:

I am glad you answered. I was actually following your procedure to create the PA with the DLLs instead of the sources. The first part, that you suggested below, worked fine actually. The problem arises when you continue to create the compiled assemblies in VS2005. Do you have any ideas/suggestions on how to diagnose or fix the problem???

Thank you for all your great work.

Carlos

Michael:

I guess I was not clear enough, I meant the part starting with the sub-title "Protect Your Source Code" and then after that "Create the compiled assemblies", first step, "From the Build menu, select Publish Web Site". That last part is what is failing for me really bad. I'm going to try later tonight the compile from the command prompt using the aspnet_compiler from the command line, I'll report the results later.

I'm going to install the PA with source code for testing but would like to deploy the version without the code for production. If you have any ideas I could try I'll appreciate it.

In any case, anybody else seen the path too long error??? I refuse to believe that I'm the first person to experience this.

Carlos