Deployment questions

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.
4/7/2014 12:43:37 AM
Gravatar
Total Posts 23

Deployment questions

Hello,

Some time ago I deployed an older version of mojoPortal with 2 custom extensions, however the extensions were not done the recommended way, but were rather created within mojoPortal. I have most of my programs in a folder in the web project and also 1 other program in the mojoPortal.Data.MSSQL project (which is my data layer).

I haven't had time to correct the forked code issue, but did recently do an enhancement to my extension and now need to deploy it to the same live site I deployed to originally. This site is deployed to the root folder of a hosting account on Arvixe.

I originally thought that all I had to do was make the needed changes to the live database (SQL Server) and copy over the new source files of my extension only. I mistakenly expected ASP.NET to recompile my programs after recognizing that the source changed the way Visual Studio does, but after trying this I found the programs weren't recompiling as I got errors due to new markup with new event handler methods that ASP.NET said did not exist (therefore my new code behind files were not getting recompiled).

I realized after that this approach was incorrect, especially since I forked mojoPortal, so my extension must not be creating separate dll files anyway.

I have deployed this enhancement successfully to a new (empty) subfolder at my staging host by simply publishing it via Visual Studio. I actually have several versions of this project running on my staging host account, each one in it's own subdirectory and I used Visual Studio web deploy publishing to deploy each one.

So my question is: how do I deploy to the live site on Arvixe (that is now and needs to stay in the root folder) so that mojoPortal (with my extension in it) gets recompiled? For my first (and only deployment of this so far), I copied all the files over from the staging version and that worked with no problems. I actually tried using web deploy from a local development version first, but had trouble with getting web deploy to work on Arvixe for some reason. What do you guys recommend this time?

Thanks again for all the help,

Dan

4/7/2014 7:27:53 AM
Gravatar
Total Posts 18439

Re: Deployment questions

Hi,

The thing to understand is that all the code has to be compiled by visual studio and that compilation results in the dll files in the bin folder.

The dlls produced by VS are basically the source code compiled to msil (microsoft intermediate language I think that stands for).

The ASP.NET compiler then further compiles the dlls and the .ascx, ,aspx files etc into native instructions for the given processor of the machine. Those files live down under windows folder in the temporary folder for asp.net files. So the code you compile in VS is portable to any machine but is then compiled for that machine by the asp.net compiler.

So if you make changes in the source you must recompile in VS and then re-deploy, the updated dlls and other modified files (.aspx .ascx etc).

The best thing to do is remove your custom code from mojoPortal projects and refactor it into separate projects of your own so that is is not compiled into the mojoPortal dlls by VS. 

Hope that helps,

Joe

4/7/2014 9:23:01 AM
Gravatar
Total Posts 23

Re: Deployment questions

Yes, thanks that helps a lot. I think I'm going to try just ftping the files from my staging site for now as that site has the same changes which I published to it using VS, so all the dlls I need should still be there. This worked the first time I deployed it, and this way I avoid trying to get web deploy working on Arvixe. If that doesn't make sense please let me know.

I understand what your saying about segregating the extensions into their own project but right now I have to get this up there right away, but I'll try to come back later and get that done.

Thanks again,

Dan

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