Upgraded Web Service from VS2003 to VS2005 and all Hell breaks loose!
- From: "Joseph Geretz" <jgeretz@xxxxxxxxxx>
- Date: Tue, 18 Jul 2006 14:10:48 -0400
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 -
.
- Follow-Ups:
- Re: Upgraded Web Service from VS2003 to VS2005 and all Hell breaks loose!
- From: Joseph Geretz
- Re: Upgraded Web Service from VS2003 to VS2005 and all Hell breaks loose!
- From: Joseph Geretz
- Re: Upgraded Web Service from VS2003 to VS2005 and all Hell breaks loose!
- Prev by Date: Can an XmlDocument type be used by a Java client
- Next by Date: Re: Upgraded Web Service from VS2003 to VS2005 and all Hell breaks loose!
- Previous by thread: Can an XmlDocument type be used by a Java client
- Next by thread: Re: Upgraded Web Service from VS2003 to VS2005 and all Hell breaks loose!
- Index(es):
Relevant Pages
|