Telerik OpenAccess in MasterPage

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.
9/15/2014 3:48:27 PM
Gravatar
Total Posts 42

Telerik OpenAccess in MasterPage

Hello,

I have a question how to properly implement Telerik OpenAccess in mojoportal.  It seems that the best scenario is to place it in OnInit of the MasterPage and dispose it while disposing this page. (As explained HERE)

If the layout.Master.cs would be a partial class I could expand it (but it is not). Is there a simple way of achieving this goal?

Thank you in advance for any suggestions,

Tomasz

9/16/2014 8:20:58 AM
Gravatar
Total Posts 18439

Re: Telerik OpenAccess in MasterPage

for that kind of situation what I would do is copy the code from our App_MasterPages/layout.master.cs into your own project with a new namespace, modify as needed and compile it into your own dll in the bin folder then make the layout.master file inherit from your own instead of ours

9/16/2014 8:40:29 AM
Gravatar
Total Posts 42

Re: Telerik OpenAccess in MasterPage

That is exactly what I did :) But the problem is that when I synchronize changes from the server I have to remember to copy it again and again - every synchronization. If the class would be partial (why it can not be?) - I could just expand it.

9/16/2014 8:48:09 AM
Gravatar
Total Posts 18439

Re: Telerik OpenAccess in MasterPage

It is not intended for you to compile your own code together with mojoportal code, your code should be in separate projects and compiled into separate dlls of your own.

unless your code changes you don't have to redeploy your dll after it is first deployed so I don't know what you mean about every synchronization, but in any case that is going to have to be a good enough solution.

9/16/2014 8:50:36 AM
Gravatar
Total Posts 42

Re: Telerik OpenAccess in MasterPage

I mean pulling mojoportal changes from codeplex. In such case that file layout.master.cs may change so I would have to copy this every synchronization.

9/16/2014 8:54:24 AM
Gravatar
Total Posts 18439

Re: Telerik OpenAccess in MasterPage

that file has not changed very often and is not expected to change so I would not worry too much about that

9/16/2014 9:33:00 AM
Gravatar
Total Posts 42

Re: Telerik OpenAccess in MasterPage

I understand Joe.

Of course your suggestion is good enough and works. I just thought that access to master page by possibility of expanding this class could be very usefull in some cases (like this one for example) and actually it doesn't fork the code. 

But in this case I will just monitor potential changes in layout.master.cs and it will also work of course.

Thank you very much for the advice. Mojoportal in general works great :)

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