Hi all,
I am not sure whether this is a question or a discussion. We have an ADX portal v7 solution (on premise) that needs to be upgraded to a supported version. The solution contains a significant number of custom pages which can't be accommodated on Microsoft Portals (online) without significant difficulty if at all. We are looking at the possibility of porting/rewriting this in .NET webpages, where we figure we could reuse a lot of the custom pages. Any advice would be welcome as to how to approach this and what are the potential pitfalls of porting to .NET be, e.g., one area of concern for us is the authentication layer, we are not federating to our local AD but instead customers authenticate against the contact record on CRM. We would obviously lose this and would need an alternative. Basically we are trying to decide on the least worse scenario rather than gain any value, however, we would like to explore using Microsoft Portals and having both the on premise and online version running off the same instance is not recommended by Microsoft.
If anyone is facing similar difficulties or has overcome same, I would be very interested to hear from you.
Thanks in advance,
P
*This post is locked for comments
I have the same question (0)