I am using Expression Web 2 working on websites that are many years old and were developed in Front Page. It seems to really struggle with network drives.
Depending on how I open my site it will misbehave. If I open the website on a shared network drive (we will call it S:) then I have trouble using the Save As feature. If I open a file and try to Save as to make a second similar page it will save the file but open a second Expression Web window with the same site but the network reference will be \\server\site instead of S:. So I close this second instance and referesh the site that was opened from the S: drive so that I can see the second file that I just created.
So to resolve this problem I thought that I would just work with the site from the network path instead of a shared network drive. Now the problem I have discovered is that whenever I go to add a hyperlink it ads it as an absolute reference to my file system rather than a relative reference. A link on page 2 to my home page shows up as: file://server/site/index.htm instead of index.htm If I go back to opening my site from using the netowrk drive S: then the references seem to make more sense.
Another problem I am having is that find and replace works differently depending on if I opened my site as S:\site or \\server\site. It is hit and miss but if I cannot search and replace a particlar string when my site is opened from S: I will close the site and open it from \\server\site and then the find and replace will work.
Is there a know issue using Expression Web 2 on a network drive? By the way...my server is Windows 2003 SBS and my client is running Windows XP Pro
That might have something to do with it. The one thing that is strange is that if I open a site on my local drive (C:\site) I don't have any of the same problems. I also don't have the problems if I work with the site directly off the web server (http:\\site). That is why I think that it has something to do with the network drives.