Re: Upgraded Web Service from VS2003 to VS2005 and all Hell breaks loose!

Additional info:

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
Code\WSL Components\).

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?

<rant>
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
helping matters!
</rant>

Anyway, if you can help me out with this, I'll be immensely grateful to you!

Thanks!

- Joe Geretz -

"Joseph Geretz" <jgeretz@xxxxxxxxxx> wrote in message
news:OSdldVpqGHA.3820@xxxxxxxxxxxxxxxxxxxxxxx
OK, I'll admit it up front - I just don't get it.

Here's our previous VS2003 development model. Developers develop the WS
solution on their own workstations, using their own IIS web servers mapped
to the local devleopment folder. Project compiles to a subfolder .\bin. To
deploy, the asmx page and bin subfolder are copied to the production
server.

So now I upgrade to VS2005. OK, so except for the name, everything is
changed. No more project file, codebehind pages are moved into a
subfolder, causing the conversion itself to hiccup. OK, I can get by that.
But where the hell is the binary file being built???

Here's my target path in the .sln file:

Release.AspNetCompiler.TargetPath = "C:\VBProjects\SRSDev\Source Code\WSL
Components\bin"

So I hit Build | Rebuild Solution:

Rebuild All started...
Rebuild All succeeded

But where's the output file??? The bin folder is empty!!!

Please help if you can. Thanks!!!

- Joe Geretz -




.

Relevant Pages

  • Re: Upgraded Web Service from VS2003 to VS2005 and all Hell breaks
    ... My web service project doesn't even have a bin folder. ... Joe Geretz 0 ... When I compile in batch from Visual Build Pro, ... ASPNETCOMPILER: error ASPRUNTIME: The precompilation target directory ...
    (microsoft.public.dotnet.framework.webservices)
  • Re: Upgraded Web Service from VS2003 to VS2005 and all Hell breaks loose!
    ... So the DLL for a Web Service is now called App_Code.dll? ... When I compile in batch from Visual Build Pro, ... ASPNETCOMPILER: error ASPRUNTIME: The precompilation target directory ... structure the project so that the project folder is the same folder mapped ...
    (microsoft.public.dotnet.framework.webservices)
  • Re: Build your own Forth for Microchip PIC (Episode 837)
    ... inappropriate on a limited target, ... So it reverts back to the traditional compile ... platform for your target by using the host to implement your words. ... In short create enough Forth to execute the inner interpreter and you ...
    (comp.lang.forth)
  • Problem with obj files in sysgen phase
    ... seems to be missing. ... BUILD: Compile and Link for x86. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Build your own Forth for Microchip PIC: Design thoughts
    ... Embedded systems hardware I don't plan to buy. ... Advanced work would be a distributed model where the PIC and host work ... All the code on the target would be headerless. ... compile once and copy the code to the PIC, ...
    (comp.lang.forth)
Loading