A COMPLETE solution is there. We've got something! I'm going to try it out later.
Guys, prepare for the new sgdotnet wave, not longhorn wave. *chuckles*
That solution needed CS DB and DNN DB to be the same.
Here's another solution that I'll try out which allows seperate dbs
http://forums.asp.net/908050/ShowPost.aspx
Cross our fingers and hope it works.
triplez wrote:That solution needed CS DB and DNN DB to be the same. Here's another solution that I'll try out which allows seperate dbs http://forums.asp.net/908050/ShowPost.aspx Cross our fingers and hope it works.
Okay, I've tried the stuff @ the 2nd thread.
In simple terms, the gist of what he's trying to do is to provide a webservice to communityserver to update it's own user-base when dotnetnuke adds/deletes/updates a user. So when dotnetnuke calls any of those, additional code is added to call the webservice @ communityserver to update it's own users.
There's still a problem of the cookies not reading correctly, but I'll fix it soon. :) Prepare for a great day today.
Best Regards, Kit Kai, MVP (SharePoint Portal Server)
triplez wrote:So when dotnetnuke calls any of those, additional code is added to call the webservice @ communityserver to update it's own users.
The melody of logic will always play out the truth. ~ Narumi Ayumu, Spiral