in

ASP.NET Weblogs

This Blog

Syndication

Tags

My Job

My stuff

Old stuff

Useful Stuff

Jeff Key

It works on my machine

Yes, it does mean everything

While doing my first ASP.NET 2.0 "publish" tonight I was presented with the following dialog box:



Assuming that apps delete as few items as possible, I assumed that "existing files" meant files that matched those that were being copied. I was wrong. It does indeed delete everything.

I've salvaged most of the site from local copies, but most of the images that I've posted to the blog (that aren't app-related) were lost. Nothing drastic, but it is kind of funny that the one thing I've never backed up was lost.

Moral of the story: Don't be a dope.
Published Nov 14 2005, 12:08 AM by jeffreykey
Filed under: , , ,

Comments

 

John Walker said:

I gotta say, this is something I don't like about the new Publish wizard. I wish they gave us an option. Here's where I got bitten by it...

I have a support site for one of our software products that contains a folder with support downloadable files. Since the content(files) in that folder gets updated frequently, I only update the files on the actual site. So, I learned the hard way to make a backup of the folder first before publishing the site. I then copy the backed up folder in. Could have been done better IMHO.
November 14, 2005 2:45 AM
 

T said:

My Publish Web Site dialog does not save my selected location. So I have gotten into the habit of just publishing to the default location. Then I just copy (xcopy) the files to the web server. That way I dont loose all my existing stuff.
November 14, 2005 11:29 AM
 

AndrewSeven said:

I've been exprimenting with a converted project and the publish (bad idea it has errors).

If there are errors, then the target folder will be deleted but nothing new will be put in it; however the output window says it was published :(

November 22, 2005 12:41 PM
 

Rocky Moore said:

When first playing around with the beta 2, this was one of the first things I wantd to check out. Since I am overly cautious, I tried it on a local test web site to be safe. It removed everything. The only way to protect something is to have it in a different virtual directory which only seemed to save it on the remote server, IIRC, the local one still got overwritten, so more caution and testing first ;)

One thing I did notice about the precompiled version was when it came to an older project of mine that used url rewriting handled in the global.asax.cs (converted from an only project). Worked fine locally, but on the remote server using the precompiled version it never hit any of the global.asax routines at all. Posted the uncompiled code to the remote server and everything was fine.

It also had a problem on a project that I used a number of custom web user controls. Other than those issues though, it was pretty handy. Great to deploy to a client's server without providing them source.
November 23, 2005 1:44 PM
 

Brian Scott said:

Rant follows… 1) Adding a new web site. If you start a new solution with a new web site, and choose...

July 27, 2006 9:00 PM
 

Offshore_MarketPlace said:

too bad, you should take frequent backups they can be life saver :)

October 2, 2006 8:42 PM
 

Yes, it does mean everything said:

Pingback from  Yes, it does mean everything

November 28, 2007 9:45 AM

Leave a Comment

(required)  
(optional)
(required)  
Add
Terms of Use