|
Home > Archive > Microsoft Content Management Server > May 2005 > ASP.NET Application integration with CMS
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
ASP.NET Application integration with CMS
|
|
| jgullickson 2005-05-12, 7:51 am |
| We recently converted our intranet to CMS. We have many legacy ASP
applications which we will be migrating to ASP.NET.
I would like to integrate these applications as seamlessly as possible into
the CMS site, but the only way I've come up with to do this is to create a
CMS template for each application, then add the templates to the site. This
is awkward and seems redundant (since these applications will only be added
to the site once).
I want the applications to be able to have the same look and navigation as
the CMS site (i.e., use the same usercontrols).
Any suggestions or pointers to documentation on the subject is appreciated.
I've read "Microsoft Content Management Server 2002" (Addison Wesley) and
even in that beast of a book I didn't find what I'm looking for.
Thanks!
| |
| Stefan [MSFT] 2005-05-12, 5:50 pm |
| Hi,
you can integrate the ASP.NET web forms into the MCMS site also without
creating templates and postings based of them but then you would need to
develop navigation controls that not only enumerate the channels but also
the folders on the file system holding the pages.
Usually it is simpler to convert the web forms into templates (a template is
actually already a web form - you only have to drop a console on the
template to allow saving the posting) and to create a posting based on it.
As you are already in the process of migrating the ASP pages into ASP.NET
you should go one step further and create them as template files and then
create the postings.
Cheers,
Stefan
--
This posting is provided "AS IS" with no warranties, and confers no rights
New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
----------------------
"jgullickson" <jgullickson@discussions.microsoft.com> wrote in message
news:5DC14B35-E480-456C-A44E-E1E8BF5EC9F2@microsoft.com...
> We recently converted our intranet to CMS. We have many legacy ASP
> applications which we will be migrating to ASP.NET.
>
> I would like to integrate these applications as seamlessly as possible
> into
> the CMS site, but the only way I've come up with to do this is to create a
> CMS template for each application, then add the templates to the site.
> This
> is awkward and seems redundant (since these applications will only be
> added
> to the site once).
>
> I want the applications to be able to have the same look and navigation as
> the CMS site (i.e., use the same usercontrols).
>
> Any suggestions or pointers to documentation on the subject is
> appreciated.
> I've read "Microsoft Content Management Server 2002" (Addison Wesley) and
> even in that beast of a book I didn't find what I'm looking for.
>
> Thanks!
| |
| jgullickson 2005-05-12, 5:50 pm |
| Thanks for the quick reply Stefan.
I've done this for some of the applications already and while it works, it
seems like this limits the application to one "page"; for example, let's say
you have a search function that then displays a repeater of matching records.
Normally each item in the grid would have an href pointing to a detail page,
however if this detail page is a template, which then becomes a posting, how
does my original results list know what the URL is for the detail page?
Does this make sense or am I missing something?
"Stefan [MSFT]" wrote:
> Hi,
>
> you can integrate the ASP.NET web forms into the MCMS site also without
> creating templates and postings based of them but then you would need to
> develop navigation controls that not only enumerate the channels but also
> the folders on the file system holding the pages.
>
> Usually it is simpler to convert the web forms into templates (a template is
> actually already a web form - you only have to drop a console on the
> template to allow saving the posting) and to create a posting based on it.
>
> As you are already in the process of migrating the ASP pages into ASP.NET
> you should go one step further and create them as template files and then
> create the postings.
>
> Cheers,
> Stefan
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
>
> New to MCMS?
> Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
> ----------------------
>
>
> "jgullickson" <jgullickson@discussions.microsoft.com> wrote in message
> news:5DC14B35-E480-456C-A44E-E1E8BF5EC9F2@microsoft.com...
>
>
>
| |
| Stefan [MSFT] 2005-05-12, 5:50 pm |
| You could handle this identical as with a web form.
Means provide querystring parameters which are evaluated by the result page
to determine what to display.
But as such a page will not be in the navigation you can keep this detail
page also as a separate ASP.NET webform.
I would recommend to migrate items that should show up in the navigation as
templates and all other items (like this repeater result page) as a ASP.NET
webform.
Cheers,
Stefan
--
This posting is provided "AS IS" with no warranties, and confers no rights
New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
----------------------
"jgullickson" <jgullickson@discussions.microsoft.com> wrote in message
news:A94C11C1-9E3F-4ED7-AFC0-FDECDF2C6139@microsoft.com...[vbcol=seagreen]
> Thanks for the quick reply Stefan.
>
> I've done this for some of the applications already and while it works, it
> seems like this limits the application to one "page"; for example, let's
> say
> you have a search function that then displays a repeater of matching
> records.
> Normally each item in the grid would have an href pointing to a detail
> page,
> however if this detail page is a template, which then becomes a posting,
> how
> does my original results list know what the URL is for the detail page?
>
> Does this make sense or am I missing something?
>
>
> "Stefan [MSFT]" wrote:
>
|
|
|
|
|