Using C# in VS 2005 Pro.
Background:
1. There are 3 of us working on a software project. The project will have
at least 5 separate web services, in addition to web and desktop clients.
2. We are using Subversion for version control. Therefore "flat
directories" are desirable, versus VS's propensity to throw Solutions in a
completely different folder structure than the web service source code.
3. The previous release of the software was Windows Desktop only. We used
C# in VS 2003. I was looking for an excuse to move to VS 2005 for the next
release, and IIS and Virtual Directories were up to the task. I spent many
hours messing with permissions etc. but I could never keep working for more
than 5 to 10 minutes before Internet Explorer and/or FireFox would wait
forever for /localhost/... to return anything. I'd reboot and get another 5
to 10 minutes of work before IIS no longer played well with my code.
4. However, in VS 2003 it was a piece of cake to move the web service to a
web host. /localhost/... was impossible but e.g.
www.markjerde.com/zzztest/Webservice1/Service1.asmx was a piece of cake.
(Fake URL ;-)
5. In VS 2005 working locally is easy, but so far I have not been able to
get a single "Hello World" web service working on any .NET 2.0 web server.
I'm no doubt missing something simple, but I've looked through MSDN, a
couple .NET 2.0 books, and googled extensively. Frustration is mounting....
;-)
I have messed around with "Blank Solution" and can successfully create a
project with the .sln in the same folder as the .asmx file. It works when I
test it on my development computer. How can I publish this to a web
server?
Thanks.
-- Mark
Mark Jerde - 06 Sep 2006 20:13 GMT
Sorry for the duplicate post. OE burped...
Peter Ritchie [C# MVP] - 07 Sep 2006 20:42 GMT
Before you get too much further you might want to have a look at the Web
Application Project add-in for VS2005 [1]. In VS2005 web services and web
sites are handled through the Web Developer functionality of Visual Studio.
This, while value-added, is essentially a view of an external web site. This
means it doesn't support version control, and gets a bit hairy if you're
planning on deploying as part of another deployment or part of an automated
build.
The Web Application Project add-in restores the VS2003-like functionality of
a "web project" (the Web Developer projects are really part of the solution,
not the project.)
[1]
http://msdn.microsoft.com/asp.net/reference/infrastructure/wap/default.aspx

Signature
Browse http://connect.microsoft.com/VisualStudio/feedback/ and vote.
http://www.peterRitchie.com/blog/
Microsoft MVP, Visual Developer - Visual C#
> Using C# in VS 2005 Pro.
>
[quoted text clipped - 35 lines]
>
> -- Mark
Mark Jerde - 07 Sep 2006 22:14 GMT
Peter -- Good information. Thanks.
(Please have a look at my soon-to-be-posted laptop configuration problem
too... <g> )
-- Mark
> Before you get too much further you might want to have a look at the Web
> Application Project add-in for VS2005 [1]. In VS2005 web services and web
[quoted text clipped - 15 lines]
> [1]
> http://msdn.microsoft.com/asp.net/reference/infrastructure/wap/default.aspx