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? What's the sense in
this? How would I deploy two web service pages (.asmx) to the same web site,
if both of their DLL's are named App_Code.dll?

Thanks for your help,

- Joe Geretz 0


"Joseph Geretz" <jgeretz@xxxxxxxxxx> wrote in message
news:%23O5$yfpqGHA.2304@xxxxxxxxxxxxxxxxxxxxxxx
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: Asynchronous Web Service Method Failure
    ... >When a session begins, I create a folder for that session in a virtual ... To open a stream, I use ... >the URL of the file is returned by the web service method. ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • RE: Asynchronous Web Service Method Failure
    ... When a session begins, I create a folder for that session in a virtual ... When the user requests a report, sometimes a stream is opened to load some ... the URL of the file is returned by the web service method. ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • Re: WS Works Locally but not on Web Server
    ... where page.aspx is in the subfolder. ... The web Service is in essence its own stand-alone ... > would you want to have it in a sub folder below a particular project. ... Both Interface and WebService are in the same folder, well, the WS ...
    (microsoft.public.dotnet.framework.webservices)
  • Re: Big-Picture Question (Web Services, RegNow)
    ... When you use the VS2005 website model, you can publish your web service ... with total control on the DLL. ... The compilation model is exactly the same as ... the DLLs must be placed in the "bin" folder under the root of ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Upgraded Web Service from VS2003 to VS2005 and all Hell breaks loose!
    ... 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)