Home/ Questions/Q 7028719
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-28T00:26:43+00:00

I made some changes in the Silverlight Toolkit for Windows Phone 7, more specifically,

  • 0

I made some changes in the Silverlight Toolkit for Windows Phone 7, more specifically, I made the
internal static class Transitions
public =>
public static class Transitions

and also the formerly private static method GetStoryboard method public:
public static Storyboard GetStoryboard(string name)

because I wanted to use Transitions.GetStoryboard to load a storyboard from the Toolkit and use that storyboard directly in my code. So, I rebuilt the Toolkit, and in my Phone App project, I first deleted the reference, then added the reference again (I’ve definitely selected the right .dll), but I don’t get access to the Transition class. Visual Studio says: “‘Microsoft.Phone.Controls.Transitions’ is inaccessible due to its protection level”

Somehow, the assembly reference is not updated. I’ve tried everything. I’ve deleted the Bin-folders, switched between Debug and Release build, etc. nothing did work. Any suggestions?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I ran into the same issue. The compiler is always picking the silverlight toolkit assembly from

    C:\Program Files (x86)\Microsoft SDKs\Windows Phone\v7.1\Toolkit\Aug11

    regardless that I have a newer version of the toolkit installed in:

    C:\Program Files (x86)\Microsoft SDKs\Windows Phone\v7.1\Toolkit\Oct11

    or even if I set explicitly the reference path from the VS IDE. I solved the issue by modifying my .csproj with a HintPath

     <Reference Include="Microsoft.Phone.Controls.Toolkit, Version=7.0.0.0, Culture=neutral, PublicKeyToken=b772ad94eb9ca604,processorArchitecture=MSIL" >
 <HintPath>C:\WP_Development\WindowsPhoneToolkit\Source and Samples\Bin\Debug\Microsoft.Phone.Controls.Toolkit.dll</HintPath>
 </Reference>

    This works, but I still can’t understand why VS completely ignores the user defined path when the path is set from within the Visual Studio IDE.

    • 0