I've seen this before a bit, but would have had to seen the project layout to 
confirm what the issue might have been.  Apologies for the pain Greg.

-th

Tim Heuer | (602) 405-4567 | Microsoft Silverlight
blog: http://timheuer.com/blog/ | twitter: 
@timheuer<http://twitter.com/timheuer>

________________________________
From: Charles Sterling
Sent: Wednesday, August 25, 2010 6:01 PM
To: ozSilverlight; Tim Heuer
Subject: RE: Upgrading to Silverlight 4

Tim any chance you have run into this before?
Chuck


From: [email protected] 
[mailto:[email protected]] On Behalf Of Deepak Kapoor
Sent: Wednesday, August 25, 2010 4:14 PM
To: ozSilverlight
Subject: Re: Upgrading to Silverlight 4

Greg,

I know the feeling. I had a tough time with System.Windows.Controls.Toolkit 
myself.

I hope it all works out for you in the end.

Cheers,

Deepak
On Thu, Aug 26, 2010 at 8:35 AM, Greg Keogh 
<[email protected]<mailto:[email protected]>> wrote:
I recently upgraded an application to Silverlight 4 and found a memory issue.

Oh great, that’s something to look forward to!

I eventually found that I had to download the Silverlight 4 Tools (34.8MB) and 
Silverlight 4 Toolkit Apr10 (17.2MB) to get support in VS2010. I accidentally 
downloaded an RC copy of the Tools which was smart enough to recognise that it 
shouldn’t install. Then I downloaded the SDK and realised that it’s included in 
the Tools, so I wasted more time.

It took me almost 3 hours last night to upgrade my largest SL3 project to SL4. 
All the references went haywire and produced an avalanche of overlapping 
errors. It took me hours to remove and carefully add what I thought were 
correct references again. Firstly I had trouble finding the actual DLLs, which 
are scattered under the Program Files Microsoft SDKs folder, then I’m using 
some C1 and Toolkit and Visifire and Liquid libraries which caused more trouble.

I’m finally stuck on this seemingly simple error which I can’t get rid of.

uses 'System.Windows.Controls.Toolkit, Version=4.0.5.0, Culture=neutral, 
PublicKeyToken=31bf3856ad364e35' which has a higher version than referenced 
assembly 'System.Windows.Controls.Toolkit, Version=2.0.5.0, Culture=neutral, 
PublicKeyToken=31bf3856ad364e35'

I’m in DLL hell.

Greg

_______________________________________________
ozsilverlight mailing list
[email protected]<mailto:[email protected]>
http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight

_______________________________________________
ozsilverlight mailing list
[email protected]
http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight

Reply via email to