In my inbox this morning: Interwoven & ASP.NET?
vajira sent this email to you through the Radio UserLand
John, Just came across your resume over the net (via a google search). Given you've done some Interwoven work, I'm wondering if you are able to share some of your learnings/pains. Specifically I'm interested in understanding how well Interwoven works with ASP.NET. I have not used the product at all. Considering using for one of the projects I'm involved. Given Interwoven updates the ASPX/ASCX files (essentially outside of the core development environment). What issues does this create - specifically compatibility issues with VS.NET when those ASPX/ASCX files are re-loaded.
----
Vajira,
You've found a bind spot in my resume. I've only been an architect on Interwoven jobs - I've done the system design work and then handed the template crafting work off to another team.. For .NET, I also served as a tech lead and only have experience working on a VB.NET middle tier. I have not done much in the way of ASP.NET coding.
I know that Interwoven can look like a filesystem and works well with XML. I would think you'd be able to use this functionality to separate out Interwoven managed include files or templates from your ASP.NET business logic, but haven't had to try this myself.
My sense is that Interwoven is pretty big and complicated, and best avoided (even if it's already installed) if you don't have many, many content editors and/or need the workflow flexibility.
Can anyone out there offer a better answer?
11:42:20 AM 
|
