This project is read-only.

“Publish” does not exist on “Build” menu or in “WebCore” right-click

Jul 13, 2009 at 8:13 AM
Edited Jul 13, 2009 at 8:16 AM


I have a very frustrating issue. I finally got VS2008 to work with AtomSite (it would refuse to load WebCore because of some bogus entries in the WebCore.csproj file), and now I seem to be unable to publish to a directory on the same machine because the “publish” entry cannot be found anywhere.

I have set WebCore as the StartUp Project, to no avail.

Could someone help me figure out why I cannot find “Publish” anywhere in any menu that it’s supposed to be in??

As a final note, I can “build” the project, which causes a lot of compiling before a “build successful” appears in the status bar, but no prompt whatsoever as to where the build should dump the built files. I really have no idea where the newly built files are, or how to use them in a live site.


Jul 15, 2009 at 5:58 AM

You can try running the application from Visual Studio by pressing F5.  Also, to install AtomSite, ftp (or copy) the files to the virtual directory or website location.

Jul 15, 2009 at 6:16 AM

Discovered the problem, and it had to do with an edit I did to WebCore.csproj in order to get it to load in the first place.

When loading up the entire app (for the first time, unmodified), I always got the following problem:

The project file "C:/ … /WebCore.csproj" cannot be opened. The project type is not supported by this installation.

I “solved” it (quotes intentional) by editing the WebCore.csproj file and removing these two entries:


The problem is (pun intended), this is where my “publish problem” crept in!!!

Instead of deleting both of these, I should have replaced the second with the following:


Once I did this, not only was WebCore able to load with the rest of the AtomSite solution, but it also turned WebCore into something which presented me with a “Publish” entry on the right-click!!

If the main contributors don’t change this by the next release, I’m gonna sign up and submit it as a fix myself. Hopefully one of them will double-check this post and make the changes themselves.