Hi,

I'm running the virtual machine for VS.NET 2008 Beta 2.
I've installed RC1 of Silverlight and 1.1 Alpha Refresh.
I've also installed the VS.NET 2008 Silverlight Tools

However, when I try to create a basic project, VS says I'm missing references to a bunch of assemblies. I've read other people's posts but am still unable to get this working. Am I missing anything else?

Thanks!

Andrew

it's missing: 

• agclr
• mscorlib
• system
• System.Core
• system.silverlight
• system.Xml.core

that's every assembly under the references folder.

 i should also add that all these assemblies exist in C:\Program Files\Microsoft Silverlight - it seems they're just not being registered in the GAC.

I am experiencing this exact same problem... All of my assemblies are in C:\Program Files (x86)\Microsoft Silverlight. When I browse to them, I get the warning icon next to the reference, the reference property "Resolved" is false, and the file version is 0.0.0.0.

The .NET Addict
http://dotnetaddict.dotnetdevelopersjournal.com

I'm having this issue as well. Unstalled 1.1 Alpha & Orcas Beta 1. Installed VS2k8 Beta 2, the 1.1 Alpha Refresh plugin, and the 1.1 Toolkit for Beta 2. But trying to compile, the output window shows "Silverlight framework not installed.", and I get warnings that none of the DLL references can be found. I tried removing the references and manually adding them from "...\Program Files\Microsoft Silverlight", but they still show up with the exclamation point, and still "can't be found" on compile, even though I just told the project where to find them. I thought it might be an issue with leftover Beta 1 hooks, so I created a new virtual machine and did a clean install of beta 2 & 1.1 Alpha Refresh, and I STILL get the same problem After that, I tried manually installing them in the GAC, but that didn't help either. What's the deal? This is getting frustrating. I have proof-of-concept demos that I need to show, but can't run because the pre-alpha plugin has expired, and now I can't re-compile a 1.1 refresh version because VS can't see the new DLLs. Arrrgh!!!!!! Hopefully someone has a solution to this issue.

An update...

Wondering if something about my VPC setup was causing the issue, I downloaded the "official" MS Beta 2 Virtual PC image to a second PC, ran it, and installed the SL 1.1a Refresh runtime & SL 1.1a Refresh Tools. Surprise. Same result. Silverlight apps will not compile. "Silverlight framework not installed." Silverlight DLL references not found, even if I manually re-add them.

So that's:
    - Uninstall Orcas Beta 1 from existing VPC, install VS Beta 2, SL 1.1a Refresh runtime, SL 1.1a Refresh Tools
    - Install VS Beta 2, SL 1.1a Refresh runtime, SL 1.1a Refresh Tools on a clean VPC
    - Install SL 1.1a Refresh runtime & SL 1.1a Refresh Tools on "official" MS VS Beta 2 VPC.

Three different install methods, on two different PCs, all with the EXACT same result. That seems to indicate to me that there's something wrong with either Beta 2, or one of the 1.1a Refresh installers.

Did they even bother to test these? When I get this problem on MS's own Beta 2 install, I have to wonder. Sorry if I seem a little angry; this is just frustrating. Without a working Silverlight 1.1 environment, my development work is at a complete standstill, I've wasted at least a full day so far trying to get what should have been a simple setup working, and my boss is already pressuring me to have our app ready to go by the time the 1.1 Beta is released.

Arrrgh!!!

I am experiencing the same - spookily I can run the silverlight demo site (http://www.microsoft.com/silverlight/default_ns.aspx#0_0) in FireFox but not in I.E.

Did you find a resolution to this issue at all? 

Chris Gaskell, .Net Developer and Web enthusiast.
http://cgaskell.wordpress.com

I´ve the same problem. I try install - uninstall and the issue is the same

I'm experiencing the same problem. The steps i followed were:

1. Installed the Orcas Beta 2, never used the Beta 1 release.

2. Installed the Silverlight.1.1.AlphaRefresh.exe.

3. VS_SilverlightTools_Alpha_Setup.exe.

4. Created a new silverlight project.

All the references to the assemblies seem to be missing. Tried to add them manually also from the Microsoft Silverlight folder. Still missing... Any clue?

Thanks.

Cheers, Niki.

P.S. I'm running Windows XP. Could that be the rouble?

I doubt it will be OS based - hope not anyhow!  

Chris Gaskell, .Net Developer and Web enthusiast.
http://cgaskell.wordpress.com

I doubt we're looking at an OS-specific problem. I think people have posted that they have encountered the problem on XP, Vista 32-bit, and my own experience on Vista 64-bit.

The .NET Addict
http://dotnetaddict.dotnetdevelopersjournal.com

And the MS Beta 2 VPC image is Server 2003, so add that to the list. Definitely not an OS issue.

I have installed vs2008 on vista and xp, I have the same problem on both installs.

1. Installed silverlight 1.1

2. installed vs2008

3. installed the tools for vs2008

Come on MVP's tell us how to fix this!  

Chris Gaskell, .Net Developer and Web enthusiast.
http://cgaskell.wordpress.com

Additionally the error I get when trying to build the solution (with bad ref's) is "The Silverlight framework is not installed" 

Chris Gaskell, .Net Developer and Web enthusiast.
http://cgaskell.wordpress.com

got the same problem. I think ther's somthing wrong with the silverlight 1.1 aplha refresh

Me too! In Blend 2  I furthermore get the error message "The name canvas does not exists in the namespace http://schemas.microsoft.com/winfx/2006/xaml/presentation"

 I also uninstalled SL1.1, rebooted, reinstalled ... but with the same outcome.

I'm using WinXP SP2 German but with an englisch VisualStudio.

SL1.1 Runtime seams to work fine with other app in IE7 (at least those samples here on silverlight.net website)

-------------------
Christian O. Metz

I'm having this problem too.

I'm running:

Vista 64 bit
VS2008 Pro beta 2 (with VS2005 Pro full side by side)
Silverlight 1.1a

Same here.

The funny thing is, it already worked on my system for a few days without problems. Then after a reboot I couldn't compile my half finished project, or a new one.

In Blend I can't create a Silverlight.Net application anymore.

I reinstalled VS2008 beta2, Blend, Silverlight Alpha Refresh 1.1 and the 1.1 Alpha tools and I get the same errors.

I can run the allready compiled app.

Something is bugged here -.-

I have discovered the source of the problem, and a (not such a great) around:

1. The problem is due to the fact that the "Microsoft.Silverlight.Common.targets" file calls a .dll in the same directory "Microsoft.VisualStudio.Silverlight.Build.Tasks.dll" to retrieve the path to the Silverlight CLR assemblies. (That directory is C:\Program Files\MSBuild\Microsoft\VisualStudio\v9.0). This dll is throwing an error with the "The framework is not installed" message.  I am thinking that a Registry key is not being set, or (gasp) an environment variable is not not set.  So the problem is either a bad dll build (note that the .target files predate the dll by 3 months, so maybe they are just out of step), or the installer is not setting/resetting an HKEY value properly.

2. The workaround is to open the "Microsoft.Silverlight.Common.targets" and change this section:

 <Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
    <UsingTask TaskName="Microsoft.VisualStudio.Silverlight.Build.Tasks.GetSilverlightFrameworkPath"   AssemblyFile="Microsoft.VisualStudio.Silverlight.Build.Tasks.dll" />
    <UsingTask TaskName="Microsoft.VisualStudio.Silverlight.Build.Tasks.CompileXaml"   AssemblyFile="Microsoft.VisualStudio.Silverlight.Build.Tasks.dll" />

    <!--
        Add Silverlight specific Item names to AvailableItemName item, so that they can show up
        in a drop-down menu for Build Action field of the properties window in VisualStudio.
     -->

    <ItemGroup Condition="'$(BuildingInsideVisualStudio)'=='true'">
        <AvailableItemName Include="SilverlightPage" />
    </ItemGroup>

    <!--
    ================================================================
                        GetFrameworkPaths
                       
    Override GetFrameworkPaths in Microsoft.Common.targets so that
    references resolve to the silverlight assemblies rather than the
    desktop CLR assemblies
    ================================================================
     -->
    <Target
        Name="GetFrameworkPaths"
        DependsOnTargets="$(GetFrameworkPathsDependsOn)"
     >
        <GetSilverlightFrameworkPath>
            <Output TaskParameter="Path" PropertyName="TargetFrameworkDirectory"/>
            <Output TaskParameter="Path" ItemName="TargetFrameworkDirectoryItem"/>
            <Output TaskParameter="Path" PropertyName="TargetFrameworkSDKDirectory"/>
            <Output TaskParameter="Path" ItemName="TargetFrameworkSDKDirectoryItem"/>
        </GetSilverlightFrameworkPath>

        <CreateProperty Value="$(TargetFrameworkDirectory)">
            <Output TaskParameter="Value" PropertyName="FrameworkPathOverride"/>
        </CreateProperty>
        <CreateProperty Value="$(TargetFrameworkDirectory)">
            <Output TaskParameter="Value" PropertyName="SdkPath"/>
        </CreateProperty>
    </Target>

TO THIS:

<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
    <UsingTask TaskName="Microsoft.VisualStudio.Silverlight.Build.Tasks.CompileXaml"   AssemblyFile="Microsoft.VisualStudio.Silverlight.Build.Tasks.dll" />

    <!--
        Add Silverlight specific Item names to AvailableItemName item, so that they can show up
        in a drop-down menu for Build Action field of the properties window in VisualStudio.
     -->

    <ItemGroup Condition="'$(BuildingInsideVisualStudio)'=='true'">
        <AvailableItemName Include="SilverlightPage" />
    </ItemGroup>

    <!--
    ================================================================
                        GetFrameworkPaths
                       
    Override GetFrameworkPaths in Microsoft.Common.targets so that
    references resolve to the silverlight assemblies rather than the
    desktop CLR assemblies
    ================================================================
     -->
    <Target
        Name="GetFrameworkPaths"
        DependsOnTargets="$(GetFrameworkPathsDependsOn)"
     >

        <CreateProperty Value="C:\Program Files\Microsoft Silverlight">
            <Output TaskParameter="Value" PropertyName="FrameworkPathOverride"/>
        </CreateProperty>
        <CreateProperty Value="C:\Program Files\Microsoft Silverlight">
            <Output TaskParameter="Value" PropertyName="SdkPath"/>
        </CreateProperty>
    </Target>

Then you place the contents of the C:\Program Files\Microsoft Silverlight\*.dll in your project's clientbin (target file output) directory.  This is an awful hack but at least it will build and successfully run Silverlight 1.1 projects.  I will also admit that this hack does not properly locate the directory (hence placing the path to the Silverlight .dlls in the propertyvalue is moot, but I am still trying to find a workaround for the bad build.dll or the missing HKEY value).

I hope someone at MS notes this and has an "aha" moment.  In the meantime, I hope this helps other avoid, or who have already spent, lots of valuable time trying to fix it.

Great! That was the right hint.
I refactored the dll and looked into my registry and found that there has been missing an entry.

Therefore I added the key

SOFTWARE\Classes\CLSID\{32C73088-76AE-40F7-AC40-81F62CB2C1DA}\InprocServer32
 
And entered the hardcoded directory name to my \Microsoft Silverlight\ directory.
After that I could compile within Visual Studio.
This could be a bit shorter workaround as described above.

-------------------
Christian O. Metz

ChrisMe, what do you mean by "entered the hardcoded directory name to my \Microsoft Silverlight\ directory"? Do you mean added that as the value for the "(Default)" value for the new key?

Thanks for the tips guys but I'm not 100% how to follow them. How do I open up Microsoft.Silverlight.Common.targets? Is that a file to open up in reflector?

Josh,

It's just an XML file, so you can just open it in Notepad.

Thanks jbaysingar - where is this elusive XML file?

Right --- I've spent two (very long) days trying to correct this. I imagine this has wasted much time for many people. All of the Silverlight assemblies are not picked up as references --- I get this error for all the dlls in the Program Files Silverlight directory:  

Any Help would be appreciated. 

Lou

Josh,

It's in "...\Program Files\MSBuild\Microsoft\VisualStudio\v9.0\Silverlight"

ChrisMe:

I refactored the dll and looked into my registry and found that there has been missing an entry.

Okay. What do you mean by refactored the dll? 

ChrisMe:

Therefore I added the key

SOFTWARE\Classes\CLSID\{32C73088-76AE-40F7-AC40-81F62CB2C1DA}\InprocServer32
 
And entered the hardcoded directory name to my \Microsoft Silverlight\ directory.

How did you determine the GUID here?  And are we talking about HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\... ?

There was an update to the silverlight 1.1 runtime in the last day or so, which changed the GUID of the control. We have a fix for the tools, but there are a few more changes to silverlight.js expected this week, so we wanted to hold off until they are ready and have 1 update with all of that in it. Options:

a)       Wait a couple of days and we’ll have a updated tools release

b)       Hack the registry: Add the key HKLM\SOFTWARE\Classes\CLSID\{32C73088-76AE-40F7-AC40-81F62CB2C1DA}\InprocServer32. Set the value to the full file path for the npctrl.1.0.XXXXX.dll which should be in \program files\microsoft silverlight. For example:

c:\Program Files\Microsoft Silverlight\npctrl.1.0.20730.0.dll

You should remove this key when the tools update is shipped.

OK so I added the key into HKEY_LOCAL_MACHINE\SOFTWARE..., then I updated the XML file in C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v9.0\Silverlight and finally manually added the three remaining DLLs that were not happy (taking them from C:\Program Files (x86)\Microsoft Silverlight).

Now it compiles but I think I may have mismatched versions somewhere along the line because all I get is a "Get Silverlight" icon and 2 warnings of "conflicts between different versions of the same dependant assembly". Clicking on "Get Silverlight" takes me to the Silverlight 1.0 RC page.

If I uninstall Silverlight the C:\Program Files (x86)\Microsoft Silverlight dir still exists with all the files. How can I properly remove version 1.0?

Thanks for the info

Here's what I did to fix:

1) Added the reg key:

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{32C73088-76AE-40F7-AC40-81F62CB2C1DA}\InprocServer32

and set the default value to:

C:\Program Files (x86)\Microsoft Silverlight\npctrl.dll

There was no dll with funky Silverlight version numbers.

2) I modded the following XML file:
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v9.0\Silverlight\Microsoft.Silverlight.Common.targets.xml

replacing:

<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
    <UsingTask TaskName="Microsoft.VisualStudio.Silverlight.Build.Tasks.GetSilverlightFrameworkPath"   AssemblyFile="Microsoft.VisualStudio.Silverlight.Build.Tasks.dll" />
    <UsingTask TaskName="Microsoft.VisualStudio.Silverlight.Build.Tasks.CompileXaml"   AssemblyFile="Microsoft.VisualStudio.Silverlight.Build.Tasks.dll" />

    <!--
        Add Silverlight specific Item names to AvailableItemName item, so that they can show up
        in a drop-down menu for Build Action field of the properties window in VisualStudio.
     -->

    <ItemGroup Condition="'$(BuildingInsideVisualStudio)'=='true'">
        <AvailableItemName Include="SilverlightPage" />
    </ItemGroup>

    <!--
    ================================================================
                        GetFrameworkPaths
                       
    Override GetFrameworkPaths in Microsoft.Common.targets so that
    references resolve to the silverlight assemblies rather than the
    desktop CLR assemblies
    ================================================================
     -->
    <Target
        Name="GetFrameworkPaths"
        DependsOnTargets="$(GetFrameworkPathsDependsOn)"
     >
        <GetSilverlightFrameworkPath>
            <Output TaskParameter="Path" PropertyName="TargetFrameworkDirectory"/>
            <Output TaskParameter="Path" ItemName="TargetFrameworkDirectoryItem"/>
            <Output TaskParameter="Path" PropertyName="TargetFrameworkSDKDirectory"/>
            <Output TaskParameter="Path" ItemName="TargetFrameworkSDKDirectoryItem"/>
        </GetSilverlightFrameworkPath>

        <CreateProperty Value="$(TargetFrameworkDirectory)">
            <Output TaskParameter="Value" PropertyName="FrameworkPathOverride"/>
        </CreateProperty>
        <CreateProperty Value="$(TargetFrameworkDirectory)">
            <Output TaskParameter="Value" PropertyName="SdkPath"/>
        </CreateProperty>
    </Target>

with:

<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
    <UsingTask TaskName="Microsoft.VisualStudio.Silverlight.Build.Tasks.CompileXaml"   AssemblyFile="Microsoft.VisualStudio.Silverlight.Build.Tasks.dll" />

    <!--
        Add Silverlight specific Item names to AvailableItemName item, so that they can show up
        in a drop-down menu for Build Action field of the properties window in VisualStudio.
     -->

    <ItemGroup Condition="'$(BuildingInsideVisualStudio)'=='true'">
        <AvailableItemName Include="SilverlightPage" />
    </ItemGroup>

    <!--
    ================================================================
                        GetFrameworkPaths
                       
    Override GetFrameworkPaths in Microsoft.Common.targets so that
    references resolve to the silverlight assemblies rather than the
    desktop CLR assemblies
    ================================================================
     -->
    <Target
        Name="GetFrameworkPaths"
        DependsOnTargets="$(GetFrameworkPathsDependsOn)"
     >

        <CreateProperty Value="C:\Program Files\Microsoft Silverlight">
            <Output TaskParameter="Value" PropertyName="FrameworkPathOverride"/>
        </CreateProperty>
        <CreateProperty Value="C:\Program Files\Microsoft Silverlight">
            <Output TaskParameter="Value" PropertyName="SdkPath"/>
        </CreateProperty>
    </Target>
---------------------------------------------
3) I loaded Visual Studio, the project was closer to compiling but three DLLs were still badly referenced. I added them manually, compiled and got the "Get Silverlight" message. Closed VS2008.
4) I *deleted* C:\Program Files (x86)\Microsoft Silverlight
5) I installed Silverlight 1.1a
6) Reloaded my project and voila it works!
7) Now I have funky numbered npctrl dll so changed reg entry to:

C:\Program Files (x86)\Microsoft Silverlight\npctrl.1.0.20806.0.dll

New Silverlight projects now still need me to add manual references to:
- agclr.dll
- System.Silverlight.dll
- System.Xml.Core.dll

I also get one "Found conflicts between different versions of the same dependant assembly." warning.

So perhaps all is not *quite* right yet...

Brilliant! That worked. Thanks!

Josh,

A couple things:

1. It's strange that you don't have a versioned npctrl DLL. My Program Files\Silverlight dir. had "npctrl.1.0.20806.0.dll"

2. If you add the registry value, you don't need to change the .target XML file. You should use the original un-modded file so that it picks up the path from the registry value that you added.

Cheers jbaysingar!

OK, so spelled out my (and perhaps others) simplest solution would be:

1) Delete C:\Program Files (x86)\Microsoft Silverlight
2) Installed Silverlight 1.1a
3) Added the reg key:

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{32C73088-76AE-40F7-AC40-81F62CB2C1DA}\InprocServer32

and set the default value to:

C:\Program Files (x86)\Microsoft Silverlight\npctrl.1.0.XXXXX.dll

or if you're on 32 bit then you might need:

C:\Program Files\Microsoft Silverlight\npctrl.1.0.XXXXX.dll

--------------

Prior to this I tried many a time uninstalling and reinstalling Silverlight but the \Microsoft Silverlight\ dir remained as did it's files and the lack of a versioned "npctrl" dll. It only appeared when I maunally deleted the dir and installed Silverlight.

I changed the XML file back and it doesn't work again....

Hmmm. I added the registry key, reverted to the original .target file, and everything worked. Not sure why it's not working for you.

I can confirm that adding the entry to the registry mentioned above worked for me.  I reverted my changes to the .targets file (to the original state) and the sample projects build and run without error.  Thanks to all who posted!  Now onward...

Hi Thanks... After added the register key, it is woriking.

Sorry, guys, I always have to sleep some hours the day.

OK, all you have to do to fix this problem has already been described by joshcomley .

Only 1 thing to remember. Check out where your files actually are placed. On my machine (WinXP German) all Silverlight dlls are in not in the directory
C:\Program Files (x86)\Microsoft Silverlight\
but in
C:\Programme\Microsoft Silverlight\

Therefore I have to use this path instead as described by joshcomley.

In this directory have to be all necessary Silverlight dll. These main are:

agclr.dll
mscorlib.dll
system.dll
System.Core.dll
System.Silverlight.dll
System.Xml.Core.dll

And the slup.exe

If they are not there or there is no Microsoft Silverlight directory, try to Uninstall "Microsoft Silverlight", reboot and Install Silverlight.1.1.AlphaRefresh.exe agein (you do not need to install Silverlight 1.0 RC!).

Also check if there is a directory called C:\<Your Program Directory>\MSBuild\Microsoft\VisualStudio\v9.0\Silverlight\
Here you can find these "targets" files and the Microsoft.VisualStudio.Silverlight.Build.Tasks.dll I refactored.
If you do not have this directory I guess you have to reinstall Microsoft Silverlight Tools Alpha Refresh for Visual Studio (July 2007)

It seems that this workaround not only fixes this problem with Visual Studio 2008 Beta2 and Silverlight 1.1 Alpha but also Blend 2 (August) and Silverlight 1.1 Alpha.

joshcomley:

Here's what I did to fix:

1) Added the reg key:

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{32C73088-76AE-40F7-AC40-81F62CB2C1DA}\InprocServer32

and set the default value to:

C:\Program Files (x86)\Microsoft Silverlight\npctrl.dll

There was no dll with funky Silverlight version numbers.

2) I modded the following XML file:
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v9.0\Silverlight\Microsoft.Silverlight.Common.targets.xml

replacing:

<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
    <UsingTask TaskName="Microsoft.VisualStudio.Silverlight.Build.Tasks.GetSilverlightFrameworkPath"   AssemblyFile="Microsoft.VisualStudio.Silverlight.Build.Tasks.dll" />
    <UsingTask TaskName="Microsoft.VisualStudio.Silverlight.Build.Tasks.CompileXaml"   AssemblyFile="Microsoft.VisualStudio.Silverlight.Build.Tasks.dll" />

    <!--
        Add Silverlight specific Item names to AvailableItemName item, so that they can show up
        in a drop-down menu for Build Action field of the properties window in VisualStudio.
     -->

    <ItemGroup Condition="'$(BuildingInsideVisualStudio)'=='true'">
        <AvailableItemName Include="SilverlightPage" />
    </ItemGroup>

    <!--
    ================================================================
                        GetFrameworkPaths
                       
    Override GetFrameworkPaths in Microsoft.Common.targets so that
    references resolve to the silverlight assemblies rather than the
    desktop CLR assemblies
    ================================================================
     -->
    <Target
        Name="GetFrameworkPaths"
        DependsOnTargets="$(GetFrameworkPathsDependsOn)"
     >
        <GetSilverlightFrameworkPath>
            <Output TaskParameter="Path" PropertyName="TargetFrameworkDirectory"/>
            <Output TaskParameter="Path" ItemName="TargetFrameworkDirectoryItem"/>
            <Output TaskParameter="Path" PropertyName="TargetFrameworkSDKDirectory"/>
            <Output TaskParameter="Path" ItemName="TargetFrameworkSDKDirectoryItem"/>
        </GetSilverlightFrameworkPath>

        <CreateProperty Value="$(TargetFrameworkDirectory)">
            <Output TaskParameter="Value" PropertyName="FrameworkPathOverride"/>
        </CreateProperty>
        <CreateProperty Value="$(TargetFrameworkDirectory)">
            <Output TaskParameter="Value" PropertyName="SdkPath"/>
        </CreateProperty>
    </Target>

with:

<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
    <UsingTask TaskName="Microsoft.VisualStudio.Silverlight.Build.Tasks.CompileXaml"   AssemblyFile="Microsoft.VisualStudio.Silverlight.Build.Tasks.dll" />

    <!--
        Add Silverlight specific Item names to AvailableItemName item, so that they can show up
        in a drop-down menu for Build Action field of the properties window in VisualStudio.
     -->

    <ItemGroup Condition="'$(BuildingInsideVisualStudio)'=='true'">
        <AvailableItemName Include="SilverlightPage" />
    </ItemGroup>

    <!--
    ================================================================
                        GetFrameworkPaths
                       
    Override GetFrameworkPaths in Microsoft.Common.targets so that
    references resolve to the silverlight assemblies rather than the
    desktop CLR assemblies
    ================================================================
     -->
    <Target
        Name="GetFrameworkPaths"
        DependsOnTargets="$(GetFrameworkPathsDependsOn)"
     >

        <CreateProperty Value="C:\Program Files\Microsoft Silverlight">
            <Output TaskParameter="Value" PropertyName="FrameworkPathOverride"/>
        </CreateProperty>
        <CreateProperty Value="C:\Program Files\Microsoft Silverlight">
            <Output TaskParameter="Value" PropertyName="SdkPath"/>
        </CreateProperty>
    </Target>
---------------------------------------------
3) I loaded Visual Studio, the project was closer to compiling but three DLLs were still badly referenced. I added them manually, compiled and got the "Get Silverlight" message. Closed VS2008.
4) I *deleted* C:\Program Files (x86)\Microsoft Silverlight
5) I installed Silverlight 1.1a
6) Reloaded my project and voila it works!
7) Now I have funky numbered npctrl dll so changed reg entry to:

C:\Program Files (x86)\Microsoft Silverlight\npctrl.1.0.20806.0.dll

New Silverlight projects now still need me to add manual references to:
- agclr.dll
- System.Silverlight.dll
- System.Xml.Core.dll

I also get one "Found conflicts between different versions of the same dependant assembly." warning.

So perhaps all is not *quite* right yet...

 

-------------------
Christian O. Metz

I change only  the entry to register and it work!!

I think I might have screwed things up a little bit on my home PC (Vista); just installed everything on my work PC (XP), had the same problem.. but just changed the registry entry and all was OK!

I think I might uninstall VS2008, .NET 3(.5), Silverlight etc. at home and start again :(

I added the registry key and it didn't do squat to help me. None of my Silverlight apps work on this machine.

I also screwed around with the .projects file and manually pointed everything at my x86 silverlight directory and still nothing works.

I'm completely down and unable to write _any_ Silverlight code on _any_ of the 3 test machines right now.

The .NET Addict
http://dotnetaddict.dotnetdevelopersjournal.com

Thanks samsp!  That seems to have worked for me!

The updated tools have been uploaded to the download servers. See http://silverlight.net/forums/t/3580.aspx for details.

I installed the updated tools and that didn't fix it for me.  But I am getting a slightly different problem.  When in VS 2008 Beta 2 I hit "Debug" with Scott's samples open (from here) - I get this error:

 Parser Error Message: Could not load file or assembly 'System.Web.Extensions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. (C:\Users\Mike Kelly\Documents\SilverLight 1.1 Samples\Samples\WebApplication\web.config line 61)

The system.web.extensions in the beta2 release got an updated version number. You'll need to update the version number in web.config to the one you have (I think its now 3.5).

OK - changing all the version numbers in my web.config from 2.0 to 3.5 fixed this problem. I still get the prompt to install Silverlight.  I think that's a GUID problem.

Great, thanks... fixed the problem by installing the new tools! :)

Dear All, I have fixed the problem by following the normal steps of editing the reg. keys in addition to i start the project on the Expression Blend first and then editing it in VS 2008. it really works.

 Still having issues here having tried the above registry change and .target file alteration.

 Very frustrating. I know it's in beta but I just want to start playing!! Will plug away and hope for an update shortly.
 

Now I am frustrated! I am going to reinstall the whole setup! but anyone can guarantee that it will work agai?

_________________
Fadisss

Now I am frustrated! I am going to reinstall the whole setup! but anyone can guarantee that it will work again?

_________________
Fadisss

wzowee:

 Still having issues here having tried the above registry change and .target file alteration.

 Very frustrating. I know it's in beta but I just want to start playing!! Will plug away and hope for an update shortly.
 

 install the updated tools. they fix the problem!

Sorry I'm newbie in this forum

I'm Indonesian student and I get a thesis for Silverlight...

But I'm very confuse, I install WPF/E plugin and then I will run chess example(with silverlight)...

How does it can't..??? 

samsp:

expected this week

I just downloaded the version marked 8/10/07.  Is that the version that is meant to have the fix in it?  I just loaded a system from scratch.

order:

vs2005, sp1, patches

vs2008

silverlight add on.

and I still get the same errors   "the referenced components 'agclr' could not be found', etc.

so, my question is, do you think the 8/10 addressed this issue (if so, it did not)

or

it's been 6 days since your post (more than a couple days).  what is the status of the update?

Peter Kellner
http://73rdstreet.com and blogging at
http://PeterKellner.net
MVP, ASP.NET

I had the missing references problem and installing the Silverlight TOOLS 1.1 refresh seems to have solved the problem.

More recently I have an auto-generated filed called page.g.cs that has references to system.windows that are unresolved. There is no such .dll on my computer. I'm not sure what generated this file!

using System;

using System.Windows;

using System.Windows.Controls;

using System.Windows.Documents;

using System.Windows.Ink;

using System.Windows.Input;

using System.Windows.Media;

using System.Windows.Media.Animation;

using System.Windows.Shapes;

namespace SilverlightProject2 {

public partial class Page

// variable declarations

Wounded_Ego,

could you post a link to the tools you downloaded?  if it is not recent, then it doesn't address the issue.

Microsoft posted to another thread (referenced here) that they were working on a fix and it would be out in a few days (about 2 weeks ago)

Peter Kellner
http://73rdstreet.com and blogging at
http://PeterKellner.net
MVP, ASP.NET

pkellner:

Wounded_Ego,

could you post a link to the tools you downloaded?  if it is not recent, then it doesn't address the issue.

Microsoft posted to another thread (referenced here) that they were working on a fix and it would be out in a few days (about 2 weeks ago)

see this post: http://silverlight.net/forums/t/3580.aspx

the version linked to in there is the one i installed and it fixed the problems.

 Andrew

just follow these steps for installation

1.       Windows XP Professional with SP2 along with IIS 5.1

2.       Microsoft Silverlight 1.0 Release Candidate

3.       Microsoft Silverlight 1.1 Alpha Refresh

4.       Microsoft Visual Studios Studio 2008 Beta 2 ("Orcas" Beta 2)

5.       Microsoft Silverlight Tools for Visual Studios "Orcas" Beta 2

6.       Microsoft Expression Studio- (Web, Blend, Design, Media, Encoder)

7.       Microsoft ASP.NET Futures (July 2007)

i think even u can uninstall and install step  2, 3, 5 ,7 it should work 

(If this has answered your question, please click on "Mark as Answer")
Thanks & Rgds,
Suyog Kale
Senior Software Engineer
************************************************************

I've tried all of the solution to fix this problem but it still doesn't work for me.

I have uninstall Microsoft Silverlight Tools for Visual Studio "Orcas" Beta 2 and the Silverlight Runtime. After that, i install September Preview of the Microsoft Silverlight Tools for Visual Studio "Orcas" Beta 2 and again the Silverlight Runtime.

This doesn't fix my problem. So i've changed the  Microsoft.Silverlight.Common.targets like in the post above but it will not work for me. When i change the XML File, i get online three assembly missing. If i try to reference they manually i get this error: "requested registry access it not allowed". Thats it :-/

Now i'm downloading the vpc image of Visual Studio and try my luck on a test development enviroment in virtual pc - maybe this will work. 

Don't hold your breath.  I did that, took my entire monthly bandwidth allowance (don't forget the base image) and after completing all the installation instructions I still cannot develop in Silverlight (see my other post). 

Was it too much for MS to add testing the RC for 1.1 on their virtual server image?  Whilst I can understand there being problems getting it to run on peoples PCs with a wide range of hardware and software configurations, in this case the hardware is exactly the same on everyones vm and the software is exactly what they configured so a decent set of instructions to get up and running should be really simple... very, very frustrating!

Note to MS silverlight team - add a test case to make sure that the installation instructions for the VM image work (so at least the quickstarts will display) and are tested on a freshly paved copy of the beta vs2008 image..  If that can't be made to work easily then what hope has anyone else got of a simple install?

 When you do get the image you will have to get firefox or remember to take out the comment in the HTML page which prevents the page from displaying for security purposes (there is a post on this board somewhere about this) because it only comes with IE6.

:-(

:-)zz[

I really don't know yet if it's working but..

Just add all the missing reference from "C:\Program Files\Microsoft Silverlight" and all the error message have gone.

I've still don't check it cause this error was from a custom controls I've  try to build from the sample that post in the "LiquidBoy website"

http://advertboy.wordpress.com/project-silverlight-11/

So I need to hook them first on an ASP + SilverLight website that need some adjustments until I master that combine environment.

Debug your life :-).

http://epsilone3.spaces.live.com/

I am executing my application from browsing in IIS.

From Virtual Directory.

Still i got same error which is mentioned in subject.

I followed all the steps of registry update -> change the target xml file -> reinstall Silverlight.

But it is same what it was.

What should i have to do?

hi Friend, You can find the solution on the following link:

http://vijaymodi.wordpress.com/2007/10/04/vs-2008-beta-2-silverlight-reference-problems/

Regards, Vijay Modi

Vijay Modi
http://vijaymodi.wordpress.com

I found an other bug that produces this error.

When you create a project that has a "-" or " " in the name, then the reference in the assembly property is created wrong with a "_" sign. Example:

Project "SilverlightProject1-Test" creates "x:Class="SilverlightProject1_Test.Page;assembly=ClientBin/SilverlightProject1_Test.dll"" change it to "x:Class="SilverlightProject1_Test.Page;assembly=ClientBin/SilverlightProject1-Test.dll" and it works.

I hope that helps when all the other workarounds failed.

nirav5884:

I am executing my application from browsing in IIS.

From Virtual Directory.

Still i got same error which is mentioned in subject.

I followed all the steps of registry update -> change the target xml file -> reinstall Silverlight.

But it is same what it was.

What should i have to do?

 Yeah, I had the same problem.  I fought this all week following the registry hack without success until I tried copying the project to C:\Inetpub\wwwroot and then it worked!  So if anyone else is getting an error trying to browse to a project and you set it up using a Virtual Directory, try copying it to the wwwroot folder, creating the application, and then running it. Worked for me (FINALLY!) :)

 Here's my solution:

1) Deleted MS Silverlight folder(C:\Program Files\Microsoft Silverlight)

2)Installed Silverlight.1.1.AlphaRefresh

3)Reinstalled VS Silverlight Tools Alpha

5) I celebrated :)