Comments on: Custom Property: ShareIt

By: Frederik Vig

Frederik Vig — Wed, 23 Jun 2010 11:18:38 +0000

Hi Anders
Based on the stack trace I would say that the Network Service user does not have access rights to the xml file: SocialMediaSites.xml. Also try and compile it yourself, I know there are some security restrictions in Windows 7 when downloading .dll files.

Hope this helps!

Frederik

By: Anders

Anders — Wed, 23 Jun 2010 05:49:10 +0000

Hi Frederik!

Just added ShareIt to my project (CMS 6), but I’m getting this error:

Unable to load one or more of the requested types. The following information may be a subset of the Type/LoaderException information present – inspect with debugger for complete view.
Check assemblies [FV.ShareIt, Version=1.0.0.1, Culture=neutral, PublicKeyToken=null] and/or types [FV.ShareIt.Classes.SocialMediaSite,
FV.ShareIt.Util.Helper,
FV.ShareIt.Property.ShareIt,
FV.ShareIt.Util.Helper+c__DisplayClass4]. Information from LoaderExceptions property [Request for the permission of type 'System.Web.AspNetHostingPermission, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.,
Request for the permission of type 'System.Web.AspNetHostingPermission, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.,
Request for the permission of type 'System.Web.AspNetHostingPermission, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.].

Do you got any idea what the problem might be? Am I missing something essential?

anders

By: Abhishek

Abhishek — Wed, 28 Apr 2010 11:14:13 +0000

I have taken your full code (for ShareIT) and pasted in the solution root folder.
No problem while compiling the code as I can see the Images and give count in edit mode .
But in view mode it is not working properly. I can’t see any social sites links and when I click the button show more
I get the error as I mentioned earlier.
I will probably need to debug your code a bit(which I wil do when I get time).
I just wanted to make sure if I am missing any steps?

By: Frederik Vig

Frederik Vig — Tue, 27 Apr 2010 19:42:13 +0000

Tried with the files from the Install folder? Also remember that the code is compiled against EPiServer CMS 6, update the references in Visual Studio if you need to target an earlier version.

By: Abhishek

Abhishek — Mon, 26 Apr 2010 13:42:24 +0000

Today I did the following steps
1) copied your Custom property (full code) in root folder and build IT.
2)Added the styles in master page.
3)Created property of type custom property(ShareIT) in admin and added in the code

The link show more is not working . I can see the View mode as in the Image(your blog) but I cant see anything in View mode
and when I click the button show more ,I get the error:-
Directory Listing Denied
This Virtual Directory does not allow contents to be listed.(in IE)
It URL changes and point to rooturl/av.share/units and page cannot be displayed(In firefox)

Thanks a lot for the reply..

Am I missing any steps?

By: Frederik Vig

Frederik Vig — Mon, 26 Apr 2010 10:00:01 +0000

@Abhishek – when did you get this error?

By: Abhishek

Abhishek — Mon, 26 Apr 2010 09:55:43 +0000

I get the following error :

Directory Listing Denied
This Virtual Directory does not allow contents to be listed.

Can you please tell me what step I am missing?

By: Updated all EPiServer posts to EPiServer CMS 6 | Frederik Vig - ASP.NET developer

Sun, 28 Mar 2010 17:20:21 +0000

[...] now use EPiServer CMS 6, and making sure the code still works. I’ve also added the code for ShareIt and SlideShare Dynamic Content to EPiCode, and updated EPiCode.Extensions. They’re all now [...]

By: Marcus Lindblom

Marcus Lindblom — Wed, 16 Sep 2009 06:56:02 +0000

Smooth, Thanks for sharing!

By: Magnus Paulsson

Magnus Paulsson — Tue, 08 Sep 2009 07:03:20 +0000

I imagine editors like to use the same share panels on most pages, so the best way is probably to use your property type on a common settings page and then use the “Property from other page” dynamic content to place the panel on the pages where it should be. That way you administer everything from one place. Your control is prettier too