By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
449,314 Members | 1,772 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 449,314 IT Pros & Developers. It's quick & easy.

Is "www2" a sort of reserved word for path of web projects ? ("Publish website" failing without errors)

P: n/a
I can't believe what is happening on my computer right now.

I have a web project, file-system based on something like
c:\Projects\ProjectX\www\.
I had to make some changes and testing in a separate new directory so I
created c:\Projects\ProjectX\www2\ copied all the content and build. I
made the changes I wanted and test, everything worked fine.
I'm using the Development Webserver, not IIS.
But when I hit "Publish website", it failed without errores, just said
"Build failed.".
I closed and reopen the project and same thing. Both directories were
almost identical, but for a couple of files with 2 lines of difference.

I created another solution and put both projects there, same thing. The
one in www could be "published", the other don't. "Build failed"
without no other error. Please, note, that the project was building
file using "Build website", or Ctrl-Shift-B.
I struggled with this for hours.

Now, just for fun I made a copy-paste of the same "www2" project and
created "wwwtest". Guess what? it worked !
No more ghost "Build failed" error. Made that process several times and
the new copy-pasted projects just build and "publish website" worked
without errors.

I checked the registry to see if that path was used by something, but
see nothing. Also, using Process Explorer I searched to see if some
hidden process was holding that directory, but it doesn't.

So, now I just renamed www2 to wwwanothertest and yes, it worked again
and the renaming went without problems so, it was not locked files.

So, I want to supposed, that simply there's something obscure with
having "www2" in the path.
What else could it be?

Jan 19 '07 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Not my expert area DNS, but www2 is usually used as a root level DNS
pattern, normally associated with redirection of URL's. So it may be that
wherever your resolve DNS at has that setup somewhere and you using it for a
web project is causing conflict.

--
--
Regards

John Timney (MVP)
VISIT MY WEBSITE:
http://www.johntimney.com
http://www.johntimney.com/blog
<cr************@hotmail.comwrote in message
news:11**********************@a75g2000cwd.googlegr oups.com...
>I can't believe what is happening on my computer right now.

I have a web project, file-system based on something like
c:\Projects\ProjectX\www\.
I had to make some changes and testing in a separate new directory so I
created c:\Projects\ProjectX\www2\ copied all the content and build. I
made the changes I wanted and test, everything worked fine.
I'm using the Development Webserver, not IIS.
But when I hit "Publish website", it failed without errores, just said
"Build failed.".
I closed and reopen the project and same thing. Both directories were
almost identical, but for a couple of files with 2 lines of difference.

I created another solution and put both projects there, same thing. The
one in www could be "published", the other don't. "Build failed"
without no other error. Please, note, that the project was building
file using "Build website", or Ctrl-Shift-B.
I struggled with this for hours.

Now, just for fun I made a copy-paste of the same "www2" project and
created "wwwtest". Guess what? it worked !
No more ghost "Build failed" error. Made that process several times and
the new copy-pasted projects just build and "publish website" worked
without errors.

I checked the registry to see if that path was used by something, but
see nothing. Also, using Process Explorer I searched to see if some
hidden process was holding that directory, but it doesn't.

So, now I just renamed www2 to wwwanothertest and yes, it worked again
and the renaming went without problems so, it was not locked files.

So, I want to supposed, that simply there's something obscure with
having "www2" in the path.
What else could it be?

Jan 19 '07 #2

This discussion thread is closed

Replies have been disabled for this discussion.