Vista - RC1 Presentation*.dll trouble with VS 2005

After installing the .NET Runtime 3.0 RC1 as well as the Windows SDK RC1,
Visual Studio is not capable of finding any WPF dlls (PresentationCore.dll,
PresentationFramework.dll etc.) in the GAC. Allthough they definatedly ARE
installed in the GAC (I doubledchecked). When I try to add references to
those Dlls in a C# project in Visual Studio 2005 Team System, those
Assemblys are not listed (under the ".NET" tab). When I copy those dlls from
the GAC into my local project directory everything compiles and runs fine
tough.
This brings me to two questions:

1.) How does VS dteremine, wich Assemblies show up under the ".NET"-tab in
the "Add Reference"-Dialog? Exactly what folders or exactly what registry
keys does it scan?

2.) How can I make those assemblies stored in the GAC show up in
the".NET"-tab in the "Add Reference"-Dialog. (I already tried to uninstall
and reinstall the assemblies in question using the explorer shell extension
as well as gacutil.exe - no luck).

The "Add Reference" dialog looks for Net3.0 references in
"%ProgramFiles%\Reference Assemblies\Microsoft\Framework\v3.0". There must
have been a setup problem if the assemblies are not there. Can you double
check? thanks


"bonk" <bitbonk@msn.com> wrote in message
news:e5lJrBd0GHA.1304@TK2MSFTNGP05.phx.gbl...
> After installing the .NET Runtime 3.0 RC1 as well as the Windows SDK RC1,
> Visual Studio is not capable of finding any WPF dlls
> (PresentationCore.dll, PresentationFramework.dll etc.) in the GAC.
> Allthough they definatedly ARE installed in the GAC (I doubledchecked).
> When I try to add references to those Dlls in a C# project in Visual
> Studio 2005 Team System, those Assemblys are not listed (under the ".NET"
> tab). When I copy those dlls from the GAC into my local project directory
> everything compiles and runs fine tough.
> This brings me to two questions:
>
> 1.) How does VS dteremine, wich Assemblies show up under the ".NET"-tab in
> the "Add Reference"-Dialog? Exactly what folders or exactly what registry
> keys does it scan?
>
> 2.) How can I make those assemblies stored in the GAC show up in
> the".NET"-tab in the "Add Reference"-Dialog. (I already tried to uninstall
> and reinstall the assemblies in question using the explorer shell
> extension as well as gacutil.exe - no luck).
>
>

I am having the same problem with the RTM release. The assemblies do
exist in the location you mentioned, but they are not available in
Visual Studio's "Add Reference" dialog. I have to browse for the files
manually. I received no errors during setup. I can build and run apps
fine, but I have to manually hunt down the DLLs for every new project.

Dennis Cheng [MSFT] wrote:
> The "Add Reference" dialog looks for Net3.0 references in
> "%ProgramFiles%\Reference Assemblies\Microsoft\Framework\v3.0". There must
> have been a setup problem if the assemblies are not there. Can you double
> check? thanks
>
>
> "bonk" <bitbonk@msn.com> wrote in message
> news:e5lJrBd0GHA.1304@TK2MSFTNGP05.phx.gbl...
>> After installing the .NET Runtime 3.0 RC1 as well as the Windows SDK RC1,
>> Visual Studio is not capable of finding any WPF dlls
>> (PresentationCore.dll, PresentationFramework.dll etc.) in the GAC.
>> Allthough they definatedly ARE installed in the GAC (I doubledchecked).
>> When I try to add references to those Dlls in a C# project in Visual
>> Studio 2005 Team System, those Assemblys are not listed (under the ".NET"
>> tab). When I copy those dlls from the GAC into my local project directory
>> everything compiles and runs fine tough.
>> This brings me to two questions:
>>
>> 1.) How does VS dteremine, wich Assemblies show up under the ".NET"-tab in
>> the "Add Reference"-Dialog? Exactly what folders or exactly what registry
>> keys does it scan?
>>
>> 2.) How can I make those assemblies stored in the GAC show up in
>> the".NET"-tab in the "Add Reference"-Dialog. (I already tried to uninstall
>> and reinstall the assemblies in question using the explorer shell
>> extension as well as gacutil.exe - no luck).
>>
>>
>
>

Sounds like a setup problem with the VS Extensions. Can you try uninstalling
and re-installing the November CTP of the VS extensions with .Net 3.0?
Hopefully that re-write the registry extry to fix the problem.


"Gary" <gary@discussions.microsoft.com> wrote in message
news:ubR%23nECCHHA.3448@TK2MSFTNGP03.phx.gbl...
>I am having the same problem with the RTM release. The assemblies do exist
>in the location you mentioned, but they are not available in Visual
>Studio's "Add Reference" dialog. I have to browse for the files manually. I
>received no errors during setup. I can build and run apps fine, but I have
>to manually hunt down the DLLs for every new project.
>
> Dennis Cheng [MSFT] wrote:
>> The "Add Reference" dialog looks for Net3.0 references in
>> "%ProgramFiles%\Reference Assemblies\Microsoft\Framework\v3.0". There
>> must have been a setup problem if the assemblies are not there. Can you
>> double check? thanks
>>
>>
>> "bonk" <bitbonk@msn.com> wrote in message
>> news:e5lJrBd0GHA.1304@TK2MSFTNGP05.phx.gbl...
>>> After installing the .NET Runtime 3.0 RC1 as well as the Windows SDK
>>> RC1, Visual Studio is not capable of finding any WPF dlls
>>> (PresentationCore.dll, PresentationFramework.dll etc.) in the GAC.
>>> Allthough they definatedly ARE installed in the GAC (I doubledchecked).
>>> When I try to add references to those Dlls in a C# project in Visual
>>> Studio 2005 Team System, those Assemblys are not listed (under the
>>> ".NET" tab). When I copy those dlls from the GAC into my local project
>>> directory everything compiles and runs fine tough.
>>> This brings me to two questions:
>>>
>>> 1.) How does VS dteremine, wich Assemblies show up under the ".NET"-tab
>>> in the "Add Reference"-Dialog? Exactly what folders or exactly what
>>> registry keys does it scan?
>>>
>>> 2.) How can I make those assemblies stored in the GAC show up in
>>> the".NET"-tab in the "Add Reference"-Dialog. (I already tried to
>>> uninstall and reinstall the assemblies in question using the explorer
>>> shell extension as well as gacutil.exe - no luck).
>>>
>>>
>>