Web Forms :: Using Themes And Multiple Master Pages To Make A Template/profile Based Website?
Oct 21, 2010
I have atleast 10 websites that have different css,html,javasacripts and webconfig. But the same code behind files.With this design everything is hard to maintain. So I decided to work on it and I started moving all the queries in the code beghind file to stored procedures. Since every website uses the same database.
What I have decided is to make use of themes and multiple master pages? IS this the best way to go about it?
Also lets say I have two templates. There is site A and site B. both using different templates. And have pages Home About Us and Contact.
Now would I be creating three different masterpages? for each template so 6 in total? ( since none of the templates are supposed to look the same)
or Should I just create two masterpages? if so how would I manage the html of the page so it looks different?
I have been working on a fun little project just to build my skills as an ASP.Net developer. I have learned quite a bit thus far, and don't normally post questions in forums. Google and the books I own generally do the trick for me. But for this question I would like some community input.
I am developing a simple blog platform in ASP.Net / C#. Eventually I hope it will basically be a clone of how Wordpress works. Again, this is mostly a learning project for myself and I realize there are many projects out there doing what I am doing in .Net.
Anyways, the question I want some input on is whether I should use themes or master pages to customize the look and feel of the site. As I understand it, a theme mostly just changes colors and such, but CAN do much more. Whereas a master page can easily change the look and feel of an entire site.
What are the pro's and con's of either route, and what would y'all recommend? I'm not really looking for code examples here, just input on what y'all would think is the best route to pursue.
to a vb code resource/tutorial that explains how you can change a theme from a dropdown list on a content page derived from a nested master page, not the main master page.
We have a nested master page which we have made it as a seperate class library.(Becoz many projects use the same master page) Initially we had all our css files,skin files, images inside the Master page project itself. But now we wanted the themes to be global and moved it out to wwwroot as mentioned in the below link.
The Masterpage has user controls out of which one user control has the telerik menu. The css is not getting set for that particular user control. We use relative path for setting the style sheet link. But it is not getting set. Its still referring to the old path. But all the skin files, images are pointing to the new global location. Except for the telerik menu rest all is aligned according to the style sheet.
When i do view source, the link to style sheet is pointing to the old location. I dunno why this happening. Is this a telerik issue or i am going wrong somewhere.
I'm trying to set profiles/themes using a basepage to allow the colour of my site to change for users. I can do this on a single page but I'm trying to do this site wide and am getting an error.
I've been watching http://www.asp.net/general/videos/how-do-i-create-user-selectable-themes-for-a-web-site this tutorial
but I'm getting errors at the final step...
System.NullReferenceException was unhandled by user code Message="Object reference not set to an instance of an object." Source="App_Code.gflsvdcc" StackTrace: at BasePage.OnPreInit(EventArgs e) in D:WebsitesBalticQuarter19.01.11App_CodeBasePage.vb:line 9 at System.Web.UI.Page.PerformPreInit() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) InnerException:
is the error, The error occurs because of the line 9 =
I've just finished and published my most recent version of
[URL]
but when I try to validate the website using http://validator.w3.org it is giving me few errors.
I noticed that I have multiple <title> tags in my pages and reason for that is because I am using master pages. What happened is my master pages are using <head> tag and <title> tag inside, then default page will have <asp:content ID="Content2" runat="server" contentplaceholderid="head"> and here I'll have another <title> tag.
The question is obviously I am having duplicate <title> tags across my entire website. Which <title> tags should I remove, the one in <head> tag of my master page, or the one on every other page such as one specified in default.aspx?
I would think that master page should not have the title and any other meta tags such as <meta name = "keywoards", "description" etc since I am repeating it in all other pages but is my thinking correct?
I am using a master page with a treeview control. I have 2 other pages Summary.aspx and Home.aspx
I want the Summary page to be loaded when I run the application but afterwards I want to load the Home.aspx page based on the selected Node change event of the treeview control.
I have placed the treeview control in master page because it has to remian the same for all my pages.
Did I do something wrong? The problem is I am not able to load the pages based on events occuring for Tree view control.
My web application is so large so i break it 2-3 dlls like 1 DLL for Acc-section-Forms.DLL other is Acc-Section-Reports.DLL and so on all these app are using same master page
but when i run my application and open any form it give me error
The type 'Tempelates.invGeneral' is ambiguous: it could come from assembly 'E:wwwrootASP.NETaccountsinAcc-section-Forms.DLL' or from assembly 'E:wwwrootASP.NETaccountsinAcc-Section-Reports.DLL'. specify the assembly explicitly in the type name.
Line 3: <%@ Master Language="C#" AutoEventWireup="true" CodeBehind="masterInvGen.master.cs" Line 4: Inherits="Tempelates.invGeneral" %> i know that i can create the clone of master page but it does not full fill my requirement bcs in that case if i need to do any change in any master file i have to apply that changes to all my clone master files too which is not a good way
is there any way that i create a master page with same name which can be used in all other app as well w
I have two Master Pages, each with a SiteMapPath control that uses a separate sitemap assigned in markup via the SiteMapFile attribute. Both sitemap files are defined as providers in web.config, and sitemap "A" is set as default. My master pages are dynamically assigned to common content pages (in the Page_PreInit event).
I've been trying for 3 hours to figure this out... Basically I'm trying to incorporate this script into my personal website which is built using .NET Master Pages...
The link to the demo is here [URL]
I copied this guys code and built locally on my machine to test. Works find UNTIL you convert the HTML to ASPX and add the <form runat="server"></form> tags. Is there a work around for this or a method that works better? I'm trying to understand how to properly insert such code into a .NET website for both now and future purposes.
I'm trying to update/create the user profile for a specific user that will not be the logged on user of the moment. I'm able to do this with the following code:
'Dim p As ProfileBase = ProfileBase.Create(Email, False)
I have 2 master pages with same (href) links on top of the page. Now these links load on the same master page when clicked on (by requirement). The problem is both these master pages have same links, so basically the same page shall be loaded in the master page.Now what i need is when the person is on Master Page 1 and clicks on the link it should load in the same page. Whereas if the user is on Master Page 2 and clicks on the same link, i should be able to change the master page from 1 to 2 and load that in Master Page 2. Something like DirectCast.
I'm working on a webforms aspx app (not MVC) and I'm not sure if I should just create separate pages or somehow make multiple views on the same aspx page for the following scenario: Basically, I need to give the user the option to view a set of data a few different ways (essentially different group by's from a data perspective)... the data is always the same, its just a matter of how to arrange on the page...
each way I need to present the data will essentially consist of 2 repeaters, one nested inside the other. The outer repeater will display a nice header section with the nested repeater showing the list of items under that heading. view by book title (title is outer repeater, with the book list being the nested repeater, yes, multiple books with same title for this example - the app has nothing to do with books, this is just to illustrate)
Book Title: A Good Story Author - Publisher - ISBN Dan Johnson - Smith Publishing - kjdkjfd99898989 Susan Day - Smith Publishing - aa777fd99ff Greg Greger - Corp XYZ - amkj897hgrt554
Book Title: Another Good Story Author - Publisher - ISBN Frank Franky - Corp XYZ - kj3kjfd9d9980 Jason Cambel - Smith Publishing - 7g7fddddttt Jill Breker - Smith Publishing - d9ddt523321
Or, view books by publisher (here the publisher would be the outer repeater and the list, with different fields compared to first view, is the nested repeater.
Publisher: Smith Publishing Title - Author - ISBN A Good Story - Dan Johnson - kjdkjfd99898989 A Good Story - Susan Day - aa777fd99ff Another Good Story - Jason Cambel - 7g7fddddttt Another Good Story - Jill Breker - d9ddt523321
Publisher: Corp XYZ Title - Author - ISBN A Good Story - Greg Greger - amkj897hgrt554 Another Good Story - Frank Franky - kj3kjfd9d9980
so what do I do here? Just making separate pages is simple and would work, but is there something else I should be considering? There will be 3 different views, so 3 pages total if I went that route. Something is making me think I should be doing this all within one aspx page? maybe just toggling the visible property of the repeater controls? but then I was thinking each of these repeater controls is databound, and I assume even if they are not visible they still incurred database hits to get the data, right? and that could be bad?
My website use master page as template. All my other pages spread in different level folder. Master page will get images (which use related path - related to master page) from style sheet file which located in App_themds's sub folder. When application run,The page will lost all images if the content page did not located in the same level as Master page.
I have developed an application in ASP.NET 3.5 which utilizes the Membership and Roles Providers and Forms Authentication to manage user access and profiles.
There are various area's of this application that are only to be used by an admin users whom login using their email and password and the rest of the users log in using their telephone number and password via their iPhone.
For simplicities sake, I would like to have two different login pages, one that is formatted for the iPhone and performs the correct validation for users adding a telephone number and the other for the application administrators.
I want to redirect the user to their respective login page based on which folder they are attempting to access. For example say I have an application structure like this
I have a master page which contains a treeview and a linkbutton. i have used 3 different stylesheets for the same page and those are listed in dropdownlist on the same master page. on dropdownlist change() event stylesheet of the master page change, i have 1 default style sheet which will come as master page loads.
now the problem is when i changed stylesheet from dropdown list, stylesheet changes the master page , but after that when if i clicked on treeview or linkbutton the stylesheet is restored to default one.
i have written following code
Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load
I am using master pages and i want to benefit mywebsite with localization.
i created a baseclass below, then i used this class in my default.aspx and it worked fine. but how can i change the culture from site.master page then other pages should uinherit the culture. by doing the base class it is not exactly giving me what i want.
Setting up the editItem template of a gridview. I have a template field with a dropdown list for editing. When the gridview goes into edit mode the dropdown list is displayed with all the right options but the current value of the field (pre-editing) is not the selected value of the dropdown list? How do I make that happen? I have a couple fields where the editItem template will use a dropdown list and I'm sure a user will not realize those values have changed and they will just edit what they intended to edit and save the changes, inadvertently also making changes to other fields.
