How Do Display a Cms Collection in an ASP.NET Page Using an Xslt File

How do display a CMS collection in an ASP.net page using an XSLT file

I would actually recommend against the collection control and opt for the the content view templated control which allows for filtering on collections as well. This should work in versions 8.6 and up and is much easier to style than using an xslt as it uses standard asp.net and c# markup.

Documentation on this control can be found here.
http://documentation.ektron.com/cms400/edr/web/edr.htm#Templated_Server_Controls/Content.htm%3FTocPath%3DTemplated%2520Server%2520Controls%7C_____2

How do display a CMS collection in an ASP.net page using an XSLT file

I would actually recommend against the collection control and opt for the the content view templated control which allows for filtering on collections as well. This should work in versions 8.6 and up and is much easier to style than using an xslt as it uses standard asp.net and c# markup.

Documentation on this control can be found here.
http://documentation.ektron.com/cms400/edr/web/edr.htm#Templated_Server_Controls/Content.htm%3FTocPath%3DTemplated%2520Server%2520Controls%7C_____2

Anyone know of an Asp.Net C# CMS type system with a Forms Module

Check the BizForms functionality in Kentico. I have used Kentico for a bit, just getting into the forms part, but seems like it will meet most, maybe even all of your requirements.

Why isn't the XSL displaying any data

<CMS:Collection ID="Collection2" runat="server" DynamicParameter="id" DisplayXslt="Workarea\CustomFiles\displayEventDetails.xsl" />

changed to

<CMS:ContentBlock ID="Collection2" runat="server" DynamicParameter="id" DisplayXslt="Workarea\CustomFiles\displayEventDetails.xsl" />

Worked.

Reason: I was not trying to read a collection (which holds two or more content blocks) but trying to read each content block separately, one at a time, which is why the XML format was different and showing up blank.

How to import a VS MasterPage in Ektron

You're probably using a Web Application project opposed to a Web Site. Because of this, the code for your MasterPages, ASPX templates, wireframes...etc. is compiled into a DLL (or DLLs) when you build the project.

When you deploy your Web Application project to your Ektron site, in additional to the files you've already pushed out, you have to copy your project's DLLs into the bin directory of the site. Your project will have a bin directory after building where you can find these, just look in File Explorer to find it if you don't see it.

/bin/WMED.dll

Also, if this is the case, do not push your .cs files to the server.

Is there a point creating a site using XSLT

Answers based on "the syntax is hard" is no answer at all imho. A). It really isn't, and B). You're supposed to be a programmer, just learn it.

Definitely other technologies are advancing at a pace XSLT hasn't since 2005ish, but it remains a powerful tool which gives you a level of abstraction that, say, asp.net webforms don't, and allows you to provide a general scalable solution to trivially serialise to a range of output formats. It's easy to generate HTML with any given language, it's harder to now extend that to XML, now extend that to JSON, now extend that to CSV.

And cached transforms are plenty fast enough in an environment which is still I/O bound.

OTOH, storing data in XML is generally not a good idea. Far better to store in a DB/mem and serialise as required for all the reasons above.

What are the benefits of an XML data model over the DataSet model?

Using XSLT transformations would enable you to use a different layout and formatting than the standard .Net grid controls. Some people don't approve of using the .Net grids because they can include more HTML than necessary, and because if not managed carefully, they can bloat ViewState.

There was a recent discussion here about the .Net grids being bloatware (but developers use them anyway).

Dynamic Menu generation using webservices

I guess you won't find any CMS that would have something like this built-in and wouldn't involve some coding to make it work.

It would be fairly easy to add such functionality in Orchard, though. The only two things you'd have to do would be:

1. Create an Orchard module (which can be autogenerated via command-line)
2. Create a class in your module project that implements INavigationProvider interface. There is only a single method to override that returns the menu items collection (properly hierarchized via Parent <-> Items properties). All the custom item-retrieval logic should happen right here. There is also a MenuName property to override - this should return the name of a generated menu (can be pretty much anything).

And basically that is all - compile the solution and enable your module feature via Dashboard -> Modules -> Features.

To display the menu you could use the Advanced Menu module. After installing and enabling this feature you can drop the MenuWidget (or StyledMenuWidget if you want a simple, pre-styled menu) to any Zone you want (you can do it from Dashboard -> Widgets). When doing that you'd be asked for the name of the menu to render. Provide the name your INavigationProvider's MenuName property returns.

HTH

---

Related Topics