You searched for the word(s): userid:740106

More Search Options

RSS Available

• Re: Hide the root node of a SiteMapProvider ONLY into Menu control

  Well the point is if that I remove one node, I immediately prevent all the childrens to be displayed. It could be a good solutions if I'm able to find a way to intercat with my inmemory sitemap. But Sitemap class, doesn't seem to allow this kind of interaction. If I work with sitemapnodecollection, I can change the inline content, but not to hide the node. Was so difficult add a visible property?

  Posted to Master Pages, Themes and Navigation Controls (Forum) by moroandrea on 7/3/2009

• Re: Hide the root node of a SiteMapProvider ONLY into Menu control

  Hi thanks for your reply. That's not exactly what I need. My menu tree is like this <siteMapNode> <siteMapNode url="~/administration/default.aspx" title="Amministrazione"> <siteMapNode url="~/administration/website.aspx" title="CMS Setup" /> </siteMapNode> <siteMapNode title="Home" url="~/home.aspx" ShowOnMenu="True"> </siteMapNode> <siteMapNode title="Staff" url="~/staff

  Posted to Master Pages, Themes and Navigation Controls (Forum) by moroandrea on 7/3/2009

• Re: Hide the root node of a SiteMapProvider ONLY into Menu control

  Infact I can't remove the root node, but thanks to your suggestion (StartFromCurrentNode) and reingegnerizing the code I got my expected result.

  Posted to Master Pages, Themes and Navigation Controls (Forum) by moroandrea on 7/3/2009

• Re: Hide the root node of a SiteMapProvider ONLY into Menu control

  [quote user="ctheriault"] Menu structure is pretty tigthly linked to the XML. There are several option more or less neat / sloppy... 1] For instance a neat way would be to clone the initial XML structure (let's call it "XML template") and them reorganize it, by removing the Staff node only and move up its child nodes. 2] Since a node cannot be hidden the proper, let's try ways to make it disappear (in MenuItemDataBound event) : such as changing it's title to emptyString

  Posted to Master Pages, Themes and Navigation Controls (Forum) by moroandrea on 7/3/2009

• Hide the root node of a SiteMapProvider ONLY into Menu control

  Hi Guys I read so much post about this specific and done so much test that I think my last chance is to ask you help. First of all my scenario: I need to hide root node (continuing to display the childrens) as well as internal nodes according to a custom param ShowOnMenu that I added into the web.sitemap. To achieve results I do web control with two asp.net controlsconfigured in this way <asp:Menu ID="SiteMenu" runat="server" DataSourceID="menuDataSource" ItemWrap

  Posted to Master Pages, Themes and Navigation Controls (Forum) by moroandrea on 7/2/2009

• Re: A perplexity on Master Page and Interface

  Hi and thanks for the answer. Following the sample, how can I use the same technique to reach a web control property from a postback page with the previouspage property? Thanks.

  Posted to Web Forms (Forum) by moroandrea on 6/29/2009

• A perplexity on Master Page and Interface

  I was reading this article http://www.odetocode.com/Articles/450.aspx at the section called Master Pages and Cross Page Postbacks. It sounds and interesting method to avoid tons of FindControl usage (avoiding all the problems listed), but this start from the assumption that MasterPage contains the control exposed from the Interface. I was trying to play with the code a bit, since my control stays into a web control, and in all case I see that I need always to use the FindControl. Is this right or

  Posted to Web Forms (Forum) by moroandrea on 6/26/2009
  Filed under: master page findcontrol

• Re: Html.ActionLink Generci Way

  I finally founded a way. Just redirerct the view to a specific file into a dfferent folder. According to my case, here its the code public ActionResult Index() { return View(@"~/Views/Test/Index.aspx"); } I think this would break the semplicity of the pattern, since it became an hard coded path that won't be updated in case of code change. So I believe an overload like those one I proposed could be useful and may be suggested to the dev tean. Anyone of them read this blog? Or should

  Posted to ASP.NET MVC (Forum) by moroandrea on 8/17/2008

• Re: Html.ActionLink Generci Way

  I'm sorry, probabaly I don't explained it correctly. I mean, I understand that the generic provide the view destination, but what if I would like to write a common class that can serve many View, just with one input param? In this scenario, how can I say redirect the content to View A instead or View B. Using the generics I should put a reference of an existent controller, and that would mean have a view with the same name. I don't want this. Image an assemlbly like MVC.Controllers.CommonController

  Posted to ASP.NET MVC (Forum) by moroandrea on 8/17/2008

• Html.ActionLink Generci Way

  I'm just approaching to the MVC framework and I think It's a great piece of software, but it's still premature and this is the right occasion to starting learning with a bunch of characteristics instead a fully and complicated framework. This is my first perplexity. Over the year every good software developer learned the importance to separate the logic from the data and from the UI layer. This MVC pattern seeme to reunify all into a single assembly. I don't like this, so first example

  Posted to ASP.NET MVC (Forum) by moroandrea on 8/16/2008