Developer forum

Forum » Development » Cannot access UserManagement

Cannot access UserManagement

E-mail notifications

Reply
Posted on 29/06/2010 12:49:56
Hi

This might sort of a newbie question but how do I make the Dynamicweb.Modules.UserManagement module/class available in my Dynamicweb custom module solution in Visual Studio?

I have plenty of experience coding custom modules for Dynamicweb, but I have no idea how to make this module available in my code (we don't use a lot of the Dynamicweb modules programmatically).

When I "dot" through the Dynamicweb namespace, I only get .Modules.Common. Can anyone explain to me how to make UserManagement available?

Do I do something in the Dynamicweb Management Center? Do I make manual changes to the Module table in the database? Is non-standard UserManagement a module that we need to buy in order to be able to use it?

The version of my Dynamicweb solution is 19.0.0.4.


I hope that these are questions that can be answered pretty easily.

Thanks

PS: I've looked at the "Single sign-on in Dynamicweb" article, but I'm guessing that these things can be done via the API using the (new?) UserManagement module -- rather than using the not-so-pretty datareaders...

Replies

 
Posted on 29/06/2010 13:01:36
Reply

It should work with that version.

Are you absolutely sure that your VS solution doesn't have a "copy local" that overwrites your DLL with a previous version?

1) Check your reference path
2) Right-click the Dynamicweb.dll in you bin-folder. If using version 19.0.0.4 this version number should be given in the "Product version" parameter of the "Details" tab, and the date should be set to 09-10-2009.

Is this so?


Regards /Snedker
 
Posted on 29/06/2010 13:17:58
Reply
The product version of the Dynamicweb.dll in my bin-folder is 19.0.0.4 so it should be the correct version.

I've attached a screenshot of the list of thing that *are* available in the Dynamicweb dll in my VS solution, if that helps.
dynamicweb.png
 
Jeppe Eriksson Agger Dynamicweb Employee
Jeppe Eriksson Agger
Posted on 29/06/2010 13:35:10
Reply
This is quite a conundrum. I can only imagine, that your dll is corrupt, damaged or incomplete in some way because you're missing about 20 namespaces compared with my Dynamicweb.dll (19.0.0.4).
 
Posted on 29/06/2010 13:46:25
Reply
Ok. My 19.0.0.4 Dynamicweb.dll is 4772 kb -- is yours a different size? The date stamp of the file is 09-10-2009, by the way, like Snedker wrote.

Can I download a complete/correct Dynamicweb in the correct version somewhere on Engage?
 
Jeppe Eriksson Agger Dynamicweb Employee
Jeppe Eriksson Agger
Posted on 29/06/2010 14:07:08
Reply
My dll has the same size and date as yours.

With regard to downloading a new version. Is it necessary for you to use the version you're using now (19.0.0.4)? If not you can download the latest version of Dynamicweb 7 and Dynamicweb 7.1 here: http://engage.dynamicweb-cms.com/Download-software-438.aspx (requires login).

If you require version 19.0.0.4, then that is not available on Engage as of now, but if you need that specific version, I can get it put up some time tomorrow (I hope). Please let me know you need me to do that.
 
Posted on 29/06/2010 14:46:52
Reply
I'm going to try to get the latest version of the dll and see if I can get that to work. Don't bother putting the 19.0.0.4 version on engage. Thanks anyway.
 
Posted on 29/06/2010 15:53:20
Reply
Are you sure you are comparing apples with apples? Sounds like your project is referencing a different (older) DLL than the actual one you're looking at. What happens when you open the correct DLL using Reflector?


Imar (Who just found out he was still logged in as Niek)
 
Posted on 29/06/2010 16:34:15
Reply
Aha. It turns out that I did in fact point to the wrong version of the dll in my VS references. I found out that my IIS and VS used two different versions of the dll and I was checking the product version of the IIS dll (I guess someone needs to clean up their project space :-)).

This was a pretty easy problem to spot, after all. But when i pointed my VS reference to the correct version of the dll, I still only got the same, limited amount of namespaces from the dynamicweb.dll. Then I remembered that, with VS being a Microsoft product, it probably had to be restarted in order for the changes (new reference) to be applied -- it was showing me the namespaces of the old reference. A restart of VS solved the problem.

Sorry that I didn't check it properly from when Snedker first suggested it as the problem, but hopefully other forum users can learn from this problem...

Yes, I was comparing apples with slightly older apples :-)

Thank you guys for all your (very quick) help.

 

You must be logged in to post in the forum