Greg, the file (and all the others with errors) are all included. This little publishing routine has worked up until late last week.



While testing some changes to my application in order to resolve potential hangups in the publishing of the app, I ran into this really neat error when closing the app:







Can you say, "gobbledygook"?



As soon as I get past this error, I will try another publication to the remote server. Hope to have some results to release soon.

Is that file added to the list of published files?

Restarting the IDE did not work. I have to step out for a bit. I'll get back to this around lunch time.

I just ran a "Rebuild All" on my solution and on the first project, I got the following error:







Each project generated a similar error. I'll close VS2008 and try again.

Thanks, Keith,



This is all I am getting from the Output window:







I left this run overnight once last week, but it never finished. It is still running at the moment. I've been searching in hopes of stumbling across something before I cancel my build, again.

I had this problem and beat my head on it for a while, what helped me was to open the Output Window during the publish, VS had put errors there that would not otherwise have been displayed. Once I found that I was able to troubleshoot. Hope it helps.

Keith Chisarik

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