VS Publish

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

Please do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.

This forum is for discussing mojoPortal development

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

You can monitor commits to the repository from this page. We also recommend developers to subscribe to email notifications in the developer forum as occasionally important things are announced.

Before posting questions here you might want to review the developer documentation.

Do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.
This thread is closed to new posts. You must sign in to post in the forums.
2/6/2013 11:01:30 AM
Gravatar
Total Posts 1204
Proud member of the mojoPortal team

Help support mojoPortal!
Add-on modules

VS Publish

Hey Joe, I'm finally looking into customizing the VS Publish feature. The scenario is that when I develop locally, I've copied the database and sites file structure down from the production server for local testing. Needless to say, I don't want to publish back any of those files during upgrades.

I noticed that Data\Sites\1\media is in the ExcludeFoldersFromDeployment section. But really, for most developers, wouldn't it be better to exclude Data\Sites completely, assuming a separate webmaster is maintaining skins and other site content, there may be entries in SharedFiles, etc.?

It's unfortunately that the settings are right within the csproj file. I'd prefer not to customize mojoPortal.Web.csproj, but if my needs are incompatible with yours I can certainly do that. For instance, I know it may be important to you to publish skins along with your updates, if you're working on those locally.

Also, I've noticed that there are a handful of XML files under Data\Sites\1 that are under source control. How critical are those files to proper site operation, and how often are they updated?

Thanks,

Jamie

2/7/2013 10:21:37 AM
Gravatar
Total Posts 18439

Re: VS Publish

Hi Jamie,

I think we can probably exclude the /Data/Sites folder from the publishing.

Those xml and xsl files are needed for the XML feature but I can probably just add them to my package template folders so they are included in releases that I package.

I think this will be ok for most developers but have a feeling it will confuse a few of them, especially the ones who populate site content on their local machines and then migrate. I don't recommend people to do that but some people do. I guess we'll see how it goes. I'll look into making this change soon.

Best,

Joe

2/7/2013 11:14:22 AM
Gravatar
Total Posts 1204
Proud member of the mojoPortal team

Help support mojoPortal!
Add-on modules

Re: VS Publish

Hi Joe, sounds good. I think it makes sense that the non-recommended deployment method will be the one needing to use a workaround. I'll keep an eye out for any confused developer posts here and help to educate as needed.

Jamie

You must sign in to post in the forums. This thread is closed to new posts.