Intersoft Community - Lounge - Are Intersoft Components Incompatible with ASPNET membership framework?

Are Intersoft Components Incompatible with ASPNET membership framework?

handy@intersoftpt.com — Thu, 12 Jul 2012 21:40:32 GMT

Hello Jean,

Yes, for Asp.Net Membership Provider and Roles, it should be handled in web.config level. You will need to set manually for the membership and permisson level.

Regards,
Handy

Are Intersoft Components Incompatible with ASPNET membership framework?

JNguimb — Thu, 12 Jul 2012 00:30:55 GMT

Hello,

Upon further testing, I found out that the problem came from the content and placement of my web.config files, and not your components. I have since corrected, and everything is now working properly.

Thank you.
Jean

Are Intersoft Components Incompatible with ASPNET membership framework?

yudi — Mon, 09 Jul 2012 07:04:35 GMT

Could you please provide us with more detail information regarding the reported problem? For example:

Are there any specific scenarios which may cause the problem? Or does the problem happen every time Intersoft’s controls are used in ASP.NET Membership Provider and Roles?
Any errors or exceptions which appear on the specific scenario? If so, could you please provide us with this information?

I’m willing to advise you further but in order to do so I would need you to elaborate on your specific scenario and possibly give me a step-by-step guide that I can use to observe the problematic behavior.

Are Intersoft Components Incompatible with ASPNET membership framework?

JNguimb — Sat, 07 Jul 2012 23:30:55 GMT

Hello,

I have been unable to Integrate Intersoft components with any application/component using Asp.Net Membership Provider and Roles.

I would like to use a customized Website Administration Tool (similar to the Visual Studio WSAT) as a shell wrapping my web application, in order to administer rules and permissions for the application. So, the WSAT would be an integral part of my application. However, none of the Intersoft components work when included in the project.

Am I doing something incorrectly, or your components do not work with asp.net membership?

Regards

Jean