Sitepublisher and ASPX

Hi All-

We are looking at installing Sitepublisher in a test/R&D environment to see if some of the functionality will meet the needs of our business users.

One of the areas we are looking at is delivering the content a web application framework (.NET).

From what I can see the *easiest* way to achieve this would be creating .aspx pages (from .page assets) inside TeamSite and then invoking OD to get them to the target web apps.

I need to understand the process around this a bit more.

My assumptions on the implementation:

1. Build layouts
2. Build/leverage components
3. Content authors assemble .page assets (layout+components)
4. Publishing workflow creates .aspx assets from the .page assets
5. Deploy .aspx assets to the web app

There is obviously more detail that this in the implementation, but I wanted to ensure the high-level steps were accurate. My curiousity lies in steps 4+5, and if accurate, the best way to implement these steps.

I appreciate any feedback!

Find more posts tagged with

Comments

srosewall

My understanding of .NET support in SitePublisher/LiveSite is as follows for recent releases:

SitePublisher; any development you do in terms of additional code for components/pages must be done in Java.

LiveSite; there's a choice of install options - J2EE or .NET flavours.
Essentially both provide a rendering engine to turn .page files into HTML.

If you use the .NET version, and you do some development in SitePublisher, then you have to run your java classes through a converter (IKVM) to output .NET code which can be used with LiveSite.

There is no capability OOTB to generate .aspx files from SitePublisher. That's not to say you couldn't, but don't expect there to be a menu option!
If you did want to generate .aspx, then you'd need to create a custom page type/layout to support it.

There was talk (a year or so ago) of a .NET version of SitePublisher which would allow you to develop natively in .NET, but that hasn't made it into a release as yet.

Hope that helps.

Ottawa_IWOV

My understanding of .NET support in SitePublisher/LiveSite is as follows for recent releases:

SitePublisher; any development you do in terms of additional code for components/pages must be done in Java.

LiveSite; there's a choice of install options - J2EE or .NET flavours.
Essentially both provide a rendering engine to turn .page files into HTML.

If you use the .NET version, and you do some development in SitePublisher, then you have to run your java classes through a converter (IKVM) to output .NET code which can be used with LiveSite.

There is no capability OOTB to generate .aspx files from SitePublisher. That's not to say you couldn't, but don't expect there to be a menu option!
If you did want to generate .aspx, then you'd need to create a custom page type/layout to support it.

There was talk (a year or so ago) of a .NET version of SitePublisher which would allow you to develop natively in .NET, but that hasn't made it into a release as yet.

Hope that helps.

Thanks very much for your reply; very informative !!

So, let's say all the component dev is done in Java (no real choice), and users end up with .page files. I assume there is a process (TPL) or something to that effect that can deliver a .aspx.

I was thinking a workflow would be the only way to encapsulate the process.

Also, how is the HTML generated for the .page files in a Sitepub only implementation (no LiveSite)?

Thanks!

srosewall

So, TPLs are used by FormsPublisher to render DCR XML as whatever target output you want.

SitePublisher/LiveSite doesn't use TPLs, but it does do a similar thing by using the presentation layer in page components combined with the page layout to create an output page.

If we were just talking about HTML, then yes, SitePublisher could generate static HTML pages which could be deployed to the target web server OOTB. The workflow provided supports this, and as you suggest it uses OD to do the file delivery to the webserver.

If you wanted to, then you could develop an aspx page layout, and have SitePublisher generate output in that format. And you could reuse the workflow's generation step to automatically generate them for you prior to deployment.

With this approach, you wouldn't need LiveSite; you'd be deploying static .aspx files to be served up by IIS. But you should note that you wouldn't be able to use any of the fancy capabilities of LiveSite if you did that (dynamic components etc.). You might also, for example have to regenerate and redeploy large portions of your site if a common update has occurred - that may or may not be important for you, and there are ways to mitigate this.

vpatel

SitePublisher; any development you do in terms of additional code for components/pages must be done in Java.
....
There was talk (a year or so ago) of a .NET version of SitePublisher which would allow you to develop natively in .NET, but that hasn't made it into a release as yet.

Upcoming release of LSDS.NET will support .NET controls so you do not have to write any code in Java if desired. You can write code in C# or the likes directly using MS VS....

Ottawa_IWOV

Upcoming release of LSDS.NET will support .NET controls so you do not have to write any code in Java if desired. You can write code in C# or the likes directly using MS VS....

Correct me if I am wrong, but this would be if you have LiveSite as part of your overall web framework?

In a Sitepublisher only environment, does this still apply?

Thanks.

anisha

srosewall and Ottawa_IWOV -

Were you ever successful in implementing a sitepublisher only solution that generates aspx pages without LiveSite environment? Also, could you please share if you know whether TS 7.2.1 supports sitepublisher component development in .net

Thank you.