I publish my updates to a network location. Actually, there are two locations. The first location, which is on my local subnet, has no problems. The second, remote location does get the app published and everyone can install it and use it; however, my Visual Studio remains in a "Publishing..." state. The browser page stating the publication has been successful does show up. All of the necessary files are on the network share. VS2008 just doesn't want to finish the job. Has anyone run into this? Any VS2008 clean-up tricks I should employ?



Thanks!

Bill

"Hi. My name is Bill. I am a Visual Studio user."



When I closed the IDE this last time, a documentation update fired. I have no idea why there is suddenly a documentation update. I have not installed something new in quite a while. There have been many builds and exits since the last updates. This took quite a few minutes (as always). After that, I decided to fire up the IDE and publish locally. There were no issue. Then, I pushed the application out to the remote subnet...



There were no issues. It worked.







Go figure.



I guess the real problem might be the fact that in spite of these unusual, unsolveable problems, I am still using the IDE.



I am addicted.