p2p.wrox.com Forums

p2p.wrox.com Forums (http://p2p.wrox.com/index.php)
-   BOOK: Beginning SharePoint 2010 Development (http://p2p.wrox.com/forumdisplay.php?f=583)
-   -   Twitterizer download which file? (http://p2p.wrox.com/showthread.php?t=82441)

mikemai January 31st, 2011 08:54 PM

Twitterizer download which file?
Twitterizer has been updated and the site moved to twitterizer.net from Google code servers.

I could not find Twitterizer.Framework namespace with the new dll - Twitterizer.Framework.dll was not in the download .zip file only Twitterizer2.dll. Also, no references to version as used in the book example.

Suggestions? I will try using code against the new dll and let you know if it works.

Thanks in advance.


kennybright February 21st, 2011 07:39 PM

re:Twitterizer download which file?
there is acopy of the framework included with the source code on wrox website.

AlexGrab March 12th, 2011 06:28 AM

I tried the framework dll in the book code from the website and even though there were no errors, when I tried to "tweet" with the web part in SharePoint it gave me an exception saying


Could not load file or assembly 'Twitterizer.Framework, Version=, Culture=neutral, PublicKeyToken=a61*********d9cb' or one of its dependencies. The system cannot find the file specified.

kennybright March 12th, 2011 05:58 PM

Download the source code from Wrox site.
In one of the same sample there is a dll component you can add a reference to your app. 584637c03_CodeDownload.zip contains Twitterrizer.Framework-
Unzip, either run the sample or and a reference to the framework dll
If you just want to see if the code works just run the author's sample; it works!

AlexGrab March 12th, 2011 06:30 PM

I may not have been clear.
I did download the code from the book and add a reference to the dll file in the Twitterizer zip of the Ch 3 folder. I still got the framework error I posted previously (despite no errors in visual studio and it recognizing all of the code/namespaces/etc).

I did not try to run the author's sample, however. I'll give that a shot.

kennybright March 12th, 2011 06:39 PM

Give that a try.
also remember to set your application properties.
1. Target Framework - 3.5
2. PlatForm Target: Any CPU or 64 bit if you are running on Windows Server 2008
(Visual Studio is a 32bit application and your calls needs to get routed tthrough the 64 bit pipeline)

AlexGrab March 12th, 2011 11:20 PM

First of all, I tried the sample solution and I got the exact same error.

Second of all, the framework was set to 3.5 and I had it set in "Any CPU" (also tried 64 bit even though it's server 2010).

Does the fact that I'm using the trial of server 2010 and the trial of VS2010 have to do with anything?

At any rate, at least I don't feel like I'm crazy now. Something is up somewhere and I've followed the instructions :P.

kennybright March 13th, 2011 12:52 AM

re:Twitterizer download which file?
If i were you i would install server 2008 R2.
to be honest i have no idea and i have not tried server 2010. so i don't know what to tell you.

AlexGrab March 21st, 2011 04:19 AM

I meant Server 2008R2 Sorry. (Server 2010 doesn't exist, it is Server 2008R2, released in 2010).

tailslide March 6th, 2012 07:36 PM

Me Too
I am also seeing this error and I followed all the steps, and used the .dll included in the .zip source code. Help!

tailslide March 6th, 2012 08:13 PM

Found these instructions on the internet which fixed it for me:

To make Visual Studio adding 3rd party assembly or even your own assembly from other project in solution to GAC please do next:
Open Package.package from Package folder in SharePoint project.

Click Advanced in bottom area.

Click Add and chose which type of assembly you want to add.

In dialog select dll file, chec GAC or BIN, add safe controls and class resources entries if required. Click Ok.

Your assembly will be packaged to WSP, defined in manifest and deployed everytime.

All times are GMT -4. The time now is 12:18 AM.

Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.