Web Deployment ASP.Net 2.0

  • Thread starter Thread starter joshdrew
  • Start date Start date
J

joshdrew

I am working with VS 2005 and web projects. We were set up to use
files on a UNC share that mapped to a web root for the IIS instance.
Microsoft told us that is a "no no" due to bios limitations so we
installed FPSE and are using web folders for each project.

Now that web folders are used, when we deploy / build using the Web
Deployment we get some strange results.

1. Directories named _test or anything that starts with _ does not get
copied over.
2. Updated images or files for that matter does not get deployed.

What gives? It seems the root of the issue is these web folders? Are
there better ways to do this? We have a team of 5 developers and we
have a projects drive with all projects on it that map back to
instances of IIS.

How do you do it? Any help would be great.
 
I dump FP extensions and I use the copy project deploy with UNC paths. I
would not put the files on a share separate from the server; it needs a
local drive.

Web folders are fine, but I am not fond of FP extensions (started as an FP
MVP, BTW).

I hope I am answering the question correctly, as you have me a bit confused.
:-)

--
Gregory A. Beamer

*************************************************
Think Outside the Box!
*************************************************
 
Sorry, I will try to explain it better.

We have box with IIS installed. Each web site root is
d:\projects\WEBSITENAME.com.

D:\projects on that box is shared.

Each workstation is mapped to a "P:\" drive which is D:\Projects on
that IIS box.

We originally would create a Filesystem project in VS 2k5 and use
P:\projects\websitename.com\etc... and it works great. Worked for many
years in VS 2k3. But as soon as projects become a little big we get
the UNC Share not supported error.

We called MS Tech Support and they had us install FPSE on the IIS Box
and instead of using the file system for projects, use web folders. So
we did.

Everything seems fine now, except when we perform a "build" in the web
deployment project. It does not seem to take all the files. It is
almost like it is cached locally on the developer machine or something
rather than compiling from what is in the web folder.
 
Back
Top