When I compile in batch from Visual Build Pro, I get the following error:
ASPNETCOMPILER : error ASPRUNTIME: The precompilation target directory
(C:\VBProjects\SRSDev\Source Code\WSL Components\bin\) cannot be in the same
tree as the source application directory (C:\VBProjects\SRSDev\Source
Now presumably, this is the same error which is preventing the production of
the binary output from the interactive compile. You'd expect the interactive
compile to give the same feedback as the batch compile does! :-\
OK, so what's the deal here? Are they saying that with VS2005 we can't
structure the project so that the project folder is the same folder mapped
as the virtual folder for the web service? Why would they change this?
What's the new best practices? All I want to do is get this upgrade from
VS2003 to VS2005.
Fine, so I'm not going to fight this thing. I change the target path to
Release.AspNetCompiler.TargetPath = "..\WSL Precomp\SRSFreedom". OK, the
build succeeds, but what's this? It looks like the there's an entire replica
of my solution at the target location, including the application DLL's
(who's names have all changed by the way). So I'm really confused about
this. Is this where my web site is supposed to be mapped? If so, why to they
call this a 'precompilation taget directory'? (Talk about an oxymoron - is
this the target (implies the end point, or is this a pre-compilation
folder?) What is this all about?
Why does Microsoft seem to have a vested interest in making this so !@#$^%#
difficult for its customers???!!! I mean do they want the developer audience
or don't they? I have other issues to wrestle with here and this $@%$^ isn't
Anyway, if you can help me out with this, I'll be immensely grateful to you!
- Joe Geretz -