Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...enable AJAX in Skinable Objectenable AJAX in Skinable Object
Previous
 
Next
New Post
8/11/2008 8:40 AM
 

How can i enable ajax on admin/Skin/Login.ascx File. Please help me out.

Its a skin file. so i tried to enable the ajax but the things are not going well, sometime i get object cannot be set to an instance ***

 


Sandeep Sachan

Software Development

 
New Post
8/12/2008 12:39 AM
 

How did you enable the ajax?  I'm currently building a skin object that is using the accordian from the toolkit and did this:

Protected Sub Page_PreRender(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.PreRender
 'register AJAX
 AJAX.RegisterScriptManager()
End Sub

And all is working so far. 

For your case you may want to create a copy of the login.ascx and login.ascx.vb and move them to your own namespace so you're not changing the core files (otherwise you'll have to change them in every update).

Ryan

 
New Post
8/12/2008 3:08 AM
 

Hi Ryan,

Actually i am unable to get your views please can your express in little brife. I think you process will solve my issue.

Thanks

Sandeep Sachan


Sandeep Sachan

Software Development

 
New Post
8/12/2008 11:57 AM
Accepted Answer 

Sure thing... I tested this and it should work:

  1. First create a directory in the DesktopModules for your new login skin object (or in the admin skins directory if you so choose, I do all of my development whether it be for Modules or Skin Object in the DesktopModules directories to keep things together).
  2. Create a directory App_LocalResources in the directory you have the Login skin object saved. Copy the login.ascx.resx file from the Admin/Skin/App_LocalResrouces to the new App_LocalResources directory.
  3. Open the login.ascx.vb file and change the namespace to your own, in my case I used YogIT.SkinObjects (the name of my company).
  4. Open the login.ascx file and change the Inherits property to the new namespace (i.e. YogIT.SkinObjects.Login)
  5. I had to make some minor changes to the code because the UI namespace was then duplicated. This could have been something from my work space, but just in case you see the same problem you may need to change the code: 

    Partial Class Login
    Inherits UI.Skins.SkinObjectBase

    To

    Partial Class Login
    Inherits DotNetNuke.UI.Skins.SkinObjectBase

    in the login.ascx.vb file.
  6. Add the PreRender sub routine to the login.ascx.vb file:

    Protected Sub Page_PreRender(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.PreRender
    'register AJAX
    AJAX.RegisterScriptManager()
    End Sub
  7. In to the top of your Skin ascx file add (if you are creating your skin in HTML edit the ascx file that is created after installing the skin):

    <%@ Register TagPrefix="yog" TagName="LOGIN" Src="~/DesktopModules/YogIT/SkinObjects/Login.ascx" %>
  8. Then in the skin where you want the object to go enter:

    <yog:LOGIN id="yogLogin" runat="server" Text="Login" LogoffText="Logout" /> 

After you do all of that you should be able to add AJAX objects to your newly create SkinObject.

Good luck!

Ryan

 

 
New Post
8/13/2008 2:13 AM
 

Thanks Ryan!

I did solved the issue. Well Two thumbs Up!!!!

 

 

Ryan Jagdfeld wrote

Sure thing... I tested this and it should work:

  1. First create a directory in the DesktopModules for your new login skin object (or in the admin skins directory if you so choose, I do all of my development whether it be for Modules or Skin Object in the DesktopModules directories to keep things together).
  2. Create a directory App_LocalResources in the directory you have the Login skin object saved. Copy the login.ascx.resx file from the Admin/Skin/App_LocalResrouces to the new App_LocalResources directory.
  3. Open the login.ascx.vb file and change the namespace to your own, in my case I used YogIT.SkinObjects (the name of my company).
  4. Open the login.ascx file and change the Inherits property to the new namespace (i.e. YogIT.SkinObjects.Login)
  5. I had to make some minor changes to the code because the UI namespace was then duplicated. This could have been something from my work space, but just in case you see the same problem you may need to change the code: 

    Partial Class Login
    Inherits UI.Skins.SkinObjectBase

    To

    Partial Class Login
    Inherits DotNetNuke.UI.Skins.SkinObjectBase

    in the login.ascx.vb file.
  6. Add the PreRender sub routine to the login.ascx.vb file:

    Protected Sub Page_PreRender(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.PreRender
    'register AJAX
    AJAX.RegisterScriptManager()
    End Sub
  7. In to the top of your Skin ascx file add (if you are creating your skin in HTML edit the ascx file that is created after installing the skin):

    <%@ Register TagPrefix="yog" TagName="LOGIN" Src="~/DesktopModules/YogIT/SkinObjects/Login.ascx" %>
  8. Then in the skin where you want the object to go enter:

     

After you do all of that you should be able to add AJAX objects to your newly create SkinObject.

Good luck!

Ryan

 


Sandeep Sachan

Software Development

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...enable AJAX in Skinable Objectenable AJAX in Skinable Object


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out