Welcome to ShenZhenJia Knowledge Sharing Community for programmer and developer-Open, Learning and Share
menu search
person
Welcome To Ask or Share your Answers For Others

Categories

It seems that starting with .NET 3.0, Microsoft moved some common assemblies to

C:Program FilesReference AssembliesMicrosoftFrameworkxxx

in order to support their effort to split out the CLR 2.0 and CLR 4.0 GACs (having also added

C:\%windir%Microsoft.NETassembly).

However, while I have both

C:Program FilesReference AssembliesMicrosoftFrameworkxxx

and

C:Program FilesReference AssembliesMicrosoftFramework.NETFrameworkv4.0

on my development machine, the latter does not exist on a server where I just installed .NET 4.0. A WCF project being deployed there references some common DLLs from this folder and cannot find them.

What am I doing wrong? Should I change these references to the new 4.0 GAC explicitly? Why does this folder not exist on the server?

See Question&Answers more detail:os

与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
thumb_up_alt 0 like thumb_down_alt 0 dislike
280 views
Welcome To Ask or Share your Answers For Others

1 Answer

Reference Assemblies folder is used with Visual Studio. While the actual deployed application will use the GAC in c:WindowsMicrosoft.NetAssembly. I am assuming you didn't install Visual Studio on your server, therefore you wouldn't have the Reference Assemblies Folder.

If you hosting WCF on the server, you need to ensure you installed .NET 4.0 Full Framework and not just the client framework.


与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
thumb_up_alt 0 like thumb_down_alt 0 dislike
Welcome to ShenZhenJia Knowledge Sharing Community for programmer and developer-Open, Learning and Share
...