Hi All,

We have just begun a project to utilize DNN for a critical portion of our business. We are creating a flexible forms architecture and selected DNN as the tool that we wanted to use to accomplish this. Eventually we want to move most of the functionality into this app, but are taking baby steps. So, we are going to call DNN from another app using a single signon approach. We have created a Security Context object in our current environment that will be hydrated, stored in the database, called from DNN when the call is made using a security token (GUID) and re-hydrated in DNN upon authentication. This will supply the data necessary to detemine which forms (tabs) will be used and dynamically generate the tabs collection modifying the current architecture.

Our legacy code is in C# and I understand from reading posts that this should not be an issue, but when I add our libraries to the solution, they are not available to default.aspx. I can add them to the references, and compile, but when I try to use the Imports statement, the namespace is not there. This is very early in the development process, and I may have underestimated the effort required to accomplish this project based on this experience.

Is there something that I am missing regarding this issue? This is pretty early in the process to be having headaches.

Do you see addional challenges regarding the process that I have outlined that I am not seeing?

Thanks in advance for your help.

Rob