Hi,

I consider this more a developer issue than an installation issue since its related to custom packaging of custom builds and not related to installation packages I have released.

This issue comes up from time to time primarily due to the fact that I don't use the Publish feature in Visual Studio myself and therefore never notice these problems myself until someone points them out. I use and recommend UnleashIt for packaging files for deployment. UnleashIt packages files based on their extension whereas VS Publish only packages files that are included in the VS project. So I think what happened here is that I forgot to add some new images to the web project and therefore they didn't get deployed when you used the VS Publish feature. I have added the images now so if you do svn update it may work better for you now. I do try to remember to add files to the web project but I sometimes forget so if you are using the publish feature frequently, feel free to let me know whenever you notice issues like this and I will add the files. These issues happen typically with image files or javascript files if I forget to include them in the VS project.

However there is another problem with using the VS publsih feature for which I have no solution and therefore I still recommend you use UnleashIt. The problem is the way we use external projects for some features like Poll, Survery, WebStore and post build events copy the needed files into the correct locations under the main Web project. Since these files are not part of the Web VS project they do not get packaged by the publish feature. Packaging with UnleashIt works much better because it doesn't care about project membership of files and only about file extensions so it packages all the needed files without concern of whether they are included in the project.

Hope it helps,

Joe

The javascript problem is probably also a packaging issue where file(s) that were not included in the VS project but were on disk were not deployed. If you disagree then tell me step by step exactly how to produce the script error(s) using demo.mojoportal.com and I will investigate.

As mentioned in the Deployment Documentation, you do need to add some file masks for some file extensions so that all the needed files get deployed. This is partly because UnleasIt was released back in the 1.1 .NET days so it doesn't know about new 2.0 files like .Master, .skin, .browser, etc, but they can easily be added.

UnleashIt can deploy via ftp, but I always deploy to a local folder first then I use FileZilla to ftp files. After deploying to the local folder you need to edit the Web.config and set <compliation debug="false"...

You just set the source folder to the Web folder where you build mojoPortal (Release build for deployment) and set the destination folder to where you want the files to be deployed.

Its very easy.

Best,

Joe