Project path names

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.
10/24/2012 6:10:54 AM
Gravatar
Total Posts 10

Project path names

i read this article where some guy explained how to create new module which is in new project. I would like to know what does he mean for "project path names" what names to write on XXX places.

thank you

The purpose of this section is so that your code from your UI project will be automatically copied into the mojoportal project with each build. If you haven't used these, $(ProjectDir) and $(SolutionDir) are macros that Visual Studio recognizes. For more info about post-build events,see this article.

Copy the commands below into the text box labeled "Post-build event command line:" and replace XXX with your project path names and YYY with your project names:

xcopy /s /y "$(ProjectDir)bin\YYY.UI.dll" "$(SolutionDir)Web\bin\"

xcopy /s /y "$(ProjectDir)bin\YYY.Business.dll" "$(SolutionDir)Web\bin\"

xcopy /s /y "$(ProjectDir)bin\YYY.Data.dll" "$(SolutionDir)Web\bin\"

xcopy /s /y "$(ProjectDir)XXX\*.ashx" "$(SolutionDir)Web\XXX\"

xcopy /s /y "$(ProjectDir)XXX\*.ascx" "$(SolutionDir)Web\XXX\"

xcopy /s /y "$(ProjectDir)XXX\*.aspx" "$(SolutionDir)Web\XXX\"

xcopy /s /y "$(ProjectDir)XXX\Controls\*.ascx" "$(SolutionDir)Web\XXX\Controls\"

xcopy /s /y "$(ProjectDir)App_GlobalResources\*.resx" "$(SolutionDir)Web\App_GlobalResources\"

xcopy /s /y "$(ProjectDir)Setup\*" "$(SolutionDir)Web\Setup"

Save after you have replaced the paths, right click your Web project and choose Properties. In the Build Events tab, click the Edit Post-build... button and you can paste this there.

 

10/24/2012 11:33:12 AM
Gravatar
Total Posts 18439

Re: Project path names

If you are working with the mojoPortal source code I recommend study the post build events for WebStore and/or mojoPortal.Features.UI to get the idea how it works and notice how the features are organized into folders within their projects, ie the WebStore feature has all its pages and user controls in the /WebStore folder within the project and that needs to land at "$(SolutionDir)Web\WebStore\"

Hope that helps,

Joe

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