module path

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/14/2009 3:36:02 PM
nasser.man
Gravatar
Total Posts 71
View Posts

module path

hi all,

to find root of sie can use SiteModuleControle.SiteRoot,now how i can find my module virtual path,?

for example i create my module then I put it and other controls into folder named myModuleFolder, 

I upload that folder on ~/modules/ path on server,now how I can find path of module? (I don,t want to use SiteRoot+"/module/myModuleFolder/" because it is possible i upload it in other places in future)

4/22/2009 12:33:19 PM
Rick Hubka
Gravatar
Total Posts 245
View Posts
mojoPortal Community Expert

Re: module path

Hi

If you watch and follow the 2 video's on this page:

www.mojoportal.com/settingupasolutionforcustomdevelopment.aspx

you will see that correctly adding your module in your own projects will result in path independence as well as future mojoportal upgrade independence.

This text below will also help you with post build file copies which is outlined middle of the second video.

xcopy /s /y "$(ProjectDir)Membership\*.ascx" "$(SolutionDir)Web\Membership\"
xcopy /s /y "$(ProjectDir)Membership\*.aspx" "$(SolutionDir)Web\Membership\"
xcopy /s /y "$(TargetPath)" "$(SolutionDir)Web\bin\"
xcopy /s /y "$(ProjectDir)App_GlobalResources\*.resx" "$(SolutionDir)Web\App_GlobalResources\"
xcopy /s /y "$(ProjectDir)bin\Membership.Business.dll" "$(SolutionDir)Web\bin\"
xcopy /s /y "$(ProjectDir)bin\Membership.Data.dll" "$(SolutionDir)Web\bin\"

My Module was called Membership.  Just replace my name with your module name above

Hope this helps.

Rick Hubka

 

 

4/23/2009 2:23:09 AM
nasser.man
Gravatar
Total Posts 71
View Posts

Re: module path

thank you Rick

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