Hello everyone.

We are creating an internal portal site. This portal will be a combination of apps written by our development staff (phone directory, but also some larger multi-page more complicated apps, etc..) and content that we would like for non-developers to be able to manage and update themselves.

We are seriously evaluating Kentico as our tool to make this happen because we like the integration with Visual Studio better than any other CMS tool we have seen.

We believe that we would like to have 1 VS 2005 project that houses the Kentico CMS stuff (CMS desk, etc.) in addition to all of our portal apps that we want to manage outside of Kentico (i.e. the developers would write them directly inside of Visual Studio.) In theory, then we could share the same master pages, etc.. to make sure our "app" pages look like the rest of the site.

1. So my first question is.. does this make sense as an approach? Or is there an absolute reason that we should make a completely separate solution for all of our portal apps.

2. Can you cleanup the VS 2005 project structure in a blank Kentico solution? We would love to have a very clean root in our VS project structure.. something like 3 folders Kentico, Apps, Common and a single default.aspx page might be all that we would have in the root. All of the stuff in the default blank solution would be under Kentico. However the generated blank solution seems to have lots of stuff right in the root including some aspx files (like scheduler.aspx). Is it possible to move any of this around to cleanup the structure or does it have to remain the way it is?

3. Given what we described about a mix of content from content editors and apps that our developers write... How can we use the Kentico menu control to show both the pages the content editors publish plus the other pages for our apps... are we going to need to write our own menu control to do this? How would the breadcrumb control work on one of our app pages.

I hope all this makes sense. We are trying hard to quickly get the best project structure setup for what we are trying to accomplish so that we can properly evaluate the tool and move forward.

Thanks,

Brian