Hi Adam,

The bug that the directory got deleted involves running two IDE at the same time. Here are the scenarios that we see this bug happens:

Scenario 1:
1. New IIS web1
2. In the same solution new IIS web2
3. Remove the web2 from the solution
4. Open a separate VS IDE and open the web2
5. Close the second copy of IDE
6. Close the first copy of IDE
 
The cache folders of both webs are removed, so after you open web1 the refactoring won?t work

Scenario2 (kind of hack) :
1. You manually removed one web?s cache folder let us say ?web1?
2. In IDE, open web1
3. In IDE, open web2
4. Close the first copy of IDE
5. Close the second copy of IDE
 
Web1?s cache folder is created
Web2?s cache folder is removed

Is this what you see?

Wendy

Wendy,

I'm still having this problem - and it seems to be getting worse.

I'm not sure that I follow excactly what you're reffering to in the last post, but to clarify things - I very frequently have multiple instances of IDE open (I often find myself working on more than one clients project at a time). And it is also fairly common for me to have more than one website project in a given solution (often I'll have seperate projects for the admin site and the public site).

This seems like a fairly serious bug, is it that uncommon to run under such an environment?

Adam

Hi Adam,

Unfortunately you are right. It is a serious bug in Whidbey RTM bits and occurs easily in your type of running environment. That is not what we expected. It is fixed in the current tree but I don't know when you can get the fix. Since it is in the shipping bits, it is hard for us to give you a fix without a shipping vehicle. I do want to write an addin to Visual Studio so that it can monitor and create this directory automatically in the future. I do feel your frustration and I will continue investigate possible ways to lessen the pain.

Thanks

Wendy

Wendy,

I was wondering if any progress had been made on this issue, or perhaps there's a workaround you can think of.

Currently I'm maintaining about 7 fairly complex applications in ASP.NET 2.0 - 3 of which are in constant development. This bug in VS is making it very time consuming to propagate updates from development to staging or production. Even more disturbing, is that I'm never quite sure where changes reside and what is being overwritten, because with the publishState files disappearance, so to, goes any record of the current server state.

Is there any way I can "catch" the publishState file (manually) before VS goes and kills it, so that way, perhaps I can copy it back into place when I need it next - That might be a bit of a pain, but for my less frequently updated projects, it would still be a great help.

Thanks again for your attaention to this.

Adam

Still Nothing? this bug is a serious time drain for me - I'd love a fix.

-Adam

Artforge:

Still Nothing? this bug is a serious time drain for me - I'd love a fix.

-Adam

Just so you  know, Adam, you're not the only one. I too would love a fix. It is frustrating and annoying. :(

Here's more information that I have discovered on the behavior:

in the WebsiteCache folder, I had 45 folders for my application:
MyApp
MyApp(1)
MyApp(2)

When I synchronize the site, then close the solution, it writes the cache information to the latest folder.  When I re-open the solution a new folder is created "MyApp(n+1)"

The Websites.xml file in the WebsiteCache folder is empty and seems to only contain several space characters.

(Sorry for double posting, where's the "Edit" button?!)

Deleting the "websites.xml" file seems to have helped.