I am using vb.net/asp.net 2005. I have a master page that displays a child content page. The child content page contains a user control that I created. In the user control I would like to access a variable that is set in the Master page.
Here's the scenario: A class based on System.Web.UI.Page has been created. A number of content pages derive from this class. All of these content pages use the same master page. The content pages define controls which need to access things on the master page (in code-behind). This is fine - no problem. In particular, each content page has its own data grid. The grid on each page has the same name, so that common code can reference it. In fact, some event handling for the grids on each content page is identical, so would like to factor that code to the base class. Interestingly, I can actually define the event handler entirely in the base class, with no stub in the content class at all, because the wire-up of event handlers uses the event-handler name defined in the grid, and that name happens to be found in the inherited base class. All good and dandy... very cool in fact. The problem comes when the code in the base class needs to access any of the common elements from the content page's master. Remember, the master is the same, and I know the type of the master. I would like to do something like this in the base-class code:
((myMasterType)this.Master).PropertyofMaster=xxx;
The problem is, that myMasterType - the type of the master page the content pages are using - is not available at compile time, at least not from a class definition for a base page. I've found articles that claim that the class name of the master is available - and it is, but not from a separate class. I CAN see it and compile with the master's class name from, for example, the code behind of the various content pages. But the actually class simply isn't available, it seems, from a pure class (the base page class). Judging from other times this question has been asked, here are common misunderstandings offered as solutions: 1. Use a page directive to declare the master type. This is not even vaguely a part of the problem, as the issue is not code in the content page, but in a separate base class which content pages inherit from. That base class is a pure class -- no .ASPX file at all. 2. Pass a reference to the master object from the content page to the base class. This can be done, but is pointless, because I can already get it, using "this.Master" from the base class! But because the type of the master is not available at compile time from the base class, it can't be passed from the content page either - unless it is passed with type MasterPage, thus losing all the properties/methods publically defined in the specific master page class. 3. Move the base page class out of the App_Code folder because the app_code folder is compiled before the other classes, and thus before the master page class. Doesn't work -- put the master page class file right in the same folder with these content pages and their master page, and the master page class is still not available at compile time from within the class. Re-summarized: Base page inherited by content pages. Content pages all use a common master page. Want to access the public properties of that master page from the base page, at runtime. Barrier is that I can find no way from within the base class to cast the master page object to the actual master page subclass being used.
I created a web site in visual studio 2008, the languaje is C#. After that, I created a master page for my web forms. The problem is: When I generate a new web form and choose the master page, the new web form can't display the content of the master page in designer mode or in the browser (by example, my web form is located in a directory called Users and master page is located in a directory called MasterViews. Only I can display them, if both files are in same location.
I reviewed the path of master page in the page directive, I changed the path with the same result.
How to create create variables/properties in master page, and let sub-pages access them? So my master will have a string property HomeUrl How can any page that uses the master page access this property?
But when i go to Design View of the page (for creating the events automatically or for drag/drop any new control from toolbox, I don't want to type everything) the design view only shows the master page! the page controls are complete ignored!
Editing a web site project with master page in VS2010Ultimate with SP1 and Win7Ultimate 64 bit. Former everything was working fine - all toolbox windows were available when editing master page or aspx page. Now with the master page all toolbox relevant tab were enabled and show - when switching to a aspx page only the HTML tab is shown and enabled. When checking all "Show all" all expected tabs are disabled.
Even the <asp:> namespace is a unrecognized namespace in the aspx file.
When compiling or debugging/running everything is ok.
How can I solve this problem? I'm using Win7 Ultimate 64 Bit, VS2010 Ultimate and IExplorer 9 and the latest updates from Microsoft.
I have a master page containing a tree and 3 dropdown lists. I am populating a context menu on right click of each node, and when clicked on any item of the context menu, it navigates to required pages.
My problem is after navigating to the required page, the selected values from the drop down lists and the selected node from the tree are getting cleared.
I can set the selected values for the dropdown lists by making some properties in master page. But how do i maintain the selected node?
In my content page, i have got the valuepath of the right clicked node.
Or is there any other way than setting the properties in master page?
Downloaded and installed vwd.net I downloaded the stuff from asp.net and now when i create a new project it is based on the site master from asp.net. that's nice, but i want to get back to the delivered defaults. how do i turn it off so that when i create a project, it's empty?
This is the content in the master page as you can see there are 4 menu items i tried to form as sidebar and i tried to inherit in home.aspx(one of the content pages) as follows:
But unfortunately the sidebar is not at all getting displayed. I know i'm doing fundamentally wrong some where. My intention is to have web pages to have sidebar like this. It is a screenshot of my intended page.
I have two master pages: TopLevelMaster and NestedMaster
When my page points to NestedMaster as it's master page, intellisense quits working in the .aspx page.
If I change my page to use TopLevelMaster as it's master page, intellisense works.
No matter what I use as the master I always get a green squiggly underline under the Content control that brings up a tooltip that says "Could not find ContentPlaceHolder1" in the current master page or pages"
TopLevelMaster exists in a different project than NestedMaster and the page.
When I say "intellisense quits working" here is what happens:
If I type something between the Content tags I get no intellisense for asp controls:
Only html controls appear upon typing an open angle bracket here
</asp:Content>
If I instert a div element I can type an opening angle bracket and I see a list of all asp controls. If I choose one and start typing there is no intellisense after that:
<asp:Content ID="Content1" runat="server" etc.., etc..> <div> ASP controls appear but no intellisense other than asp:ControlName </div> </asp:Content>
Opening one or both master pages in the IDE has no effect.
Can I modify the properties of a content page control from an event fired from the master page?create a delegate and event on master page wire up the master page in the content page create the event handler (function) on the content page modify for example:
contents of the Text property of a textbox render a control visible (or hidden) etc...
Private _theskin As String Public Property theskin() As String Get Return _theskin End Get Set(ByVal value As String) _theskin = String.Empty End Set End Property
I was then expecting to be able to access these properties from the default.aspx.vb page in this way;
If Master.theskin = foo Then do things End if
In the default.aspx.vb the code is highlighted with blue underline and says;
theskin is not a member of system.Web.Ui.Masterpage
Am I making an error somewhere along the line? Do I need to do more to be able to expose the properties to default.aspx.vb?
I have a master page setup that is used throughout my site that is basically a header with a menu. I recently added a textbox and a button to this master page which is to be a quick search box that is available anywhere in the site. When a user enters text into the search box and hits the button, I need to load the actual content page which is used to search and show search results (which also uses this same master page), and have the text entered available so the search can be triggered automatically. Again, this search text box and button is now in my master page so it could be triggered from anywhere in the app... it serves as a convenient way to do a basic search from anywhere in my app, without having to first navigate to the actual 'search page' that already exists. You can also navigate to the actual search page, which uses the same master page, where there is many more search options.I'm thrown off by the master page arrangement, which I have not used until this project. What do I do?
Why is there no default 'create/open' access to 'WebSites' from the VS2010 start page?
Background:I've succesfully been developing ASP.NET web applications (via WebSite method ((((Not WebProjects)))), using VisualWebDeveloper) for roughly 3 years. Personally, I prefer the WebSite method or strategy due to the decrease in both size and complexity (the web applications I build are generally for around 50-100 simultaneous users logging in and out and constantly manipulating data). I will continue bulding my sites via the 'Website' method provided VS2010 doesn't begin it's deprecation.The root of this question (which boiled into this post) came from perusing this article and this video tutorial. It's a shame to see functionality that brings with it an overall ease of use and increase in production capacity by decreasing both size and complexity of web application development... downplayed.
If the Visual Studio 2010 Development Team left this functionality out for a reason, I would very much like to know. So that I know what is going to be "sponsored by Microsoft" in a couple of years and I don't waste another second considering using the 'WebSite method' as a viable solution (as I know that I can't stick with vs2008 while rest the development community gets to evolve with the innovations implemented within vs2010)... WebSite method or the WebProjects method.
i am working on asp.net application using C#, identifying properties that are unused in my project. in Code analysis tool i am able to see unused private fields getting reported (Avoid unused private fields), but is there any such facility too for unused Properties declared in the class.
I'm not sure if I'm asking this correctly, but I'm having a problem with a web service. The company hosting a web service wants to see what I'm submitting to the API. Is there something in the debugger I can use to "print" or somehow get the request object and all of it's properties with values in Visual Studio? I'm guessing there's some way to get the XML request?
Creating a .NET 3.5 website in 2010, and when I attempt to create public properties for a user control I whipped up it is giving me inline error:Visual Basic 9 does not support auto-implemented properties. I can, however, type GET on the next line 2010 populates the property just like it used to. However, when I expose a control property it craps out with a null reference error at runtime.
I highlight an image in a HTML document and try to set its properties in the design by right clicking and looking up properties, I see only HTML or Document (no image). In the source view there is no link to image files folder. I guess this will be improved in the final version.
I'm using VWD 2010 Express and have found that when I change a property like AutoPostBack from within the property window the corresponding tag (<asp:TextBox...>) was not updated with the property change to the tag.
Is there a setting that I can change in the VWD properties that will enable changes through the property window for a control to automatically update the HTML tag for that control?