Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Web sites on alternate www ports in ASP.Net 2.0 won't build

0 views
Skip to first unread message

J. Walker@discussions.microsoft.com Christopher J. Walker

unread,
Dec 21, 2005, 12:30:03 PM12/21/05
to
Hello,

I am trying to create a website on port 8888 with VisualStuidio 2005. When
I go to create a new project or migrate from an old one, everything seems to
work fine, but when I go to build I get an error on every .aspx page like:

ASP.NET runtime error: '/www.website.com:8888/' is not a valid virtual path.
page.aspx 1 1 http://www.website.com:8888/

This always worked fine in VS.NET 2003 and earlier. I found another user on
this newsgroup who had the same problem (Subject: Is not a valid virtual
path, 12/9/2005 2:57 AM PST, By: Federico), but never was answered. So is
there any way to solve this problem.

Thanks for your help,

-Christopher J. Walker

OpticTygre

unread,
Dec 26, 2005, 8:09:29 PM12/26/05
to
I'm having the same issue. Does anyone have a fix for this yet?

-Jason


"Christopher J. Walker" <Christopher J. Wal...@discussions.microsoft.com>
wrote in message news:FAB92ED1-C663-44F3...@microsoft.com...

Dave

unread,
Dec 28, 2005, 1:35:01 AM12/28/05
to
What I think I'm going to do, once I'm done pissing and moaning, is convert
all my sites that use alternate ports on the same IP, to still share the same
IP, but use host headers to differentiate the sites. That means that, even
though these are development sites that really don't need dns entries, I'll
have to set them up anyway. So site1.dev.site.com, site2.dev.site.com; I
think that will work since I'm guessing the problem is because VS 2005 is
looking for a local folder and it doesn't like the colon(:) in the path name.
I tried playing around with the SLN file in my Visual Studio Projects folder
under My Documents, but it didn't really work for me and I'm not sure where
else I might have to modify. So much for backwards compatible.

gerry

unread,
Dec 28, 2005, 6:41:47 AM12/28/05
to
Can you let us know how you make out with this ?
I went the host header route and have had no problems
creating/building/browsing the site but have been unable to get debugging to
work.
Debugging does work fine for disk based sites and the iis web sites in and
under the default site but not for iis sites that use host headers.

Gerry


"Dave" <Da...@discussions.microsoft.com> wrote in message
news:4B5445EF-DA07-4364...@microsoft.com...

Dave

unread,
Dec 28, 2005, 3:16:07 PM12/28/05
to
I sorta went ahead and built my own debugger which emails me various things.
So instead of inserting breakpoints and the like, I just insert my custom
debugger. However, this might point you in the right direction:

http://groups.google.com/group/microsoft.public.inetserver.iis/browse_thread/thread/ae9c169adfd0533b/ee81f7cf26dabf27?lnk=st&q=asp.net+remote+debugging+host+headers&rnum=1&hl=en#ee81f7cf26dabf27

0 new messages