asdpnet_compiler and error 1010

[Guest]

I am trying to precompile a working website, developed using VS2005 with the
intention of deploying to an IIS webserver.

I first tried right clicking on the project, selecting "Publish Web Site" -
this asked me for the target directory which I dutifully browsed to and
clicked OK. Nothing happened. I tried several times, but NOTHING appeared in
the target directory.

So I decided to try using aspnet_compiler from the command line. Below is
the abbreviated console log. Please excuse the poor formatting.

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>aspnet_compiler -p
"C:\Documents and Settings\mhorton\My Documents\Visual Studio
2005\Projects\30Plus\" -v / C:\precomp\30plus
Utility to precompile an ASP.NET application
Copyright (C) Microsoft Corporation. All rights reserved.

error 1010: 'C:\Documents and Settings\mhorton\My Documents\Visual Studio
2005\P
rojects\30Plus" -v / C:\precomp\30plus' is not a valid path.

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>cd "C:\Documents and
Settings\mhor
ton\My Documents\Visual Studio 2005\Projects\30Plus"

C:\Documents and Settings\mhorton\My Documents\Visual Studio
2005\Projects\30Plus>


I included the cd command to show that the path is in fact accurate. Is this
a known problem with apsnet_compiler? Or am I doing something incredibly dumb
that I can't see?

I did try CD'ing to the source directory and then changing the command to:

aspnet_compiler -p ..\30plus -v / c:\precomp\30plus

This time the program "worked" in that something ended up in the /bin
directory, but I saw no .compiled files that I expected to see. What am I
missing?

Any help appreciated.

 

[Guest]

While I'm stil interested in the reason for this as an academic exercise, I
resolved the problem, I have worked around it.

I downlowsded and installed the add-in Web Deployment Project for VS2005.
This works just fine. However, I did notice in the output that the MSBUILD
ran aspnet_compiler with a RELATIVE path following the -p, i.e.,
...\..\..\..\Documents and Settings\ etc

Maybe that is the reason, but the issue is resolved and Web Deployment
Projects seems like a vastly superior solution anyway.