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

Visual Studio 2005 Web Application Projects
http://msdn.microsoft.com/asp.net/reference/infrastructure/wap/default.aspx

"Web Application Projects provide a companion web project model that
can be used as an alternative to the built-in Web Site Project in
Visual Studio 2005. This new model is ideal for web site developers who
are converting a Visual Studio .Net 2003 web project to Visual Studio
2005. (Released May 8, 2006)"

"All code files within the project are compiled into a single assembly
that is built and persisted in the \bin directory on each compile. "

"Because the Web Application Project model uses the same conceptual
semantics as the Visual Studio .NET 2003 web project model, it can make
migrating projects much easier-minimizing code changes."

-Paul

watte wrote:
Joe,

My web service project doesn't even have a bin folder. Did you have to add
one to the project?

Also, with the dll being called App_Code.dll, I'm guessing you distribute
the App_Code.dll and the asmx to the web server?

I feel your frustration!

Mark


"Joseph Geretz" wrote:

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

  • Program execution
    ... I set my Visual Studio to compile as Release. ... folder release was made available with the executable and a dll I ... then I gave the dll used also and it worked fine. ...
    (microsoft.public.vsnet.general)
  • Re: new webservices
    ... My machine does not run ZoneAlarm, ... My machine is running Visual Studio .NET 2002 and Windows XP Pro. ... I created a folder elsewhere on my machine as you said. ... > for the web service because it continues to run in the background (it ...
    (microsoft.public.dotnet.framework.webservices)
  • RE: compile errors
    ... Microsoft Online Support ... | Thread-Topic: compile errors ... I started it with Visual Studio 2005 and then moved to ... Do I have to install Visual Studio 2005 also as it was ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Event Procedures and Methods
    ... Based on my personal experience it's better to use codebehind pages (i.e. ... aspx.vb and aspx.cs) since it helps you to seperate the code and static ... And prior to Visual Studio 2005 you do not have some IDE features ... site project model with Visual Studio 2005 so that your code changes are ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Moving Files to New Location in Project
    ... Add the new file folder in Visual Studio ... Select the files you want to move to the new folder. ... home in the original project. ... Select the file you have just moved to the new folder in SourceSafe. ...
    (microsoft.public.vstudio.sourcesafe)
Loading