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

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Try using Web Application Projects:

Introduction to Web Application Projects
http://msdn.microsoft.com/vstudio/default.aspx?pull=/library/en-us/dnvs05/html/WAP.asp#wapp_topic4

This allows you to transfer a project from VS2003 to VS2005 and
maintain the original organization. You have to install a couple extra
things, but once I did that my project compiled fine without
reorganization.

-Paul


Jon Miller wrote:
I didn't have old projects to convert, so, I didn't have as painful
experience as you. I agree though that I like the way standard projects are
organized. I don't like the way projects are organized differently between
standard Windows application projects and Web projects.

Jon

"Joseph Geretz" <jgeretz@xxxxxxxxxx> wrote in message
news:ONvX7rpqGHA.4424@xxxxxxxxxxxxxxxxxxxxxxx
http://msdn.microsoft.com/asp.net/reference/migration/upgrade/default.aspx?pull=/library/en-us/dnaspp/html/webprojectsvs05.asp

Looks like the pain of upgrading is 'by design' :-\

"Be prepared to spend the better part of a day completing the entire
process."

What's wrong with Microsoft? I'm not saying that Microsoft doesn't have
legitimate issues in wanting to restructure, but don't they have a
responsibility to make this process as smooth as possible for their
customers??!!

:-\

- Joseph 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