Click here to Skip to main content
15,846,727 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
I made a simple experience on trying to find out what could be wrong with my VS.

- Created a new Silverlight Application project;

- Set Enable WCF RIA Service to true;

- To clear the "The 'MyProject.Web.csproj' project must be built before client proxy classes can be generated." warning made "build solution";

- On MyProject.Web created a new item of type WCF Service.

Nothing could be simpler than this!

When I rebuild the project get this warning that I know from experience that is going to give me trouble later on:

"Client proxy generation for service 'MyProject.Web.Service1' failed: Generating metadata files...
Warning: Unable to load a service with configName 'MyProject.Web.Service1'. To export a service provide both the assembly containing the service type and an executable with configuration for this service.
Details:Either none of the assemblies passed were executables with configuration files or none of the configuration files contained services with the config name 'MyProject.Web.Service1'.

Warning: No metadata files were generated. No service contracts were exported.
To export a service, use the /serviceName option. To export data contracts, specify the /dataContractOnly option. This can sometimes occur in certain security contexts, such as when the assembly is loaded over a UNC network file share. If this is the case, try copying the assembly into a trusted environment and running it."

This came out from nowhere today and I suspect that there is something wrong with my VS.

Can anyone help me on this?

VS 2010 Ultimate
.NET Framework 4
Silverlight 4


I took a day off, downloaded and reinstaled the hole VS pack and that warning disapeared.

I got others thou, but after googling around they seem to be of the "ignore it" type.

"WCF client proxy auto generation failed. Unable to cast transparent proxy to type 'Microsoft.VisualStudio.ServiceModel.ClientCodeGeneration.CrossAppDomainHelper'."

"The element 'Target' in namespace '' has invalid child element 'GenerateWcfClientFilesTask' in namespace ''. List of possible elements expected: 'Task, AL, AspNetCompiler, AssignCulture, AssignProjectConfiguration, AssignTargetPath, AxImp, CallTarget, CombinePath, ConvertToAbsolutePath, Copy, CreateCSharpManifestResourceName, CreateItem, CreateProperty, CreateVisualBasicManifestResourceName, Csc, Delete, Error, Exec, FindAppConfigFile, FindInList, FindUnderPath, FormatUrl, FormatVersion, GenerateApplicationManifest, GenerateBootstrapper, GenerateDeploymentManifest, GenerateResource, GenerateTrustInfo, GetAssemblyIdentity, GetFrameworkPath, GetFrameworkSdkPath, GetReferenceAssemblyPaths, LC, MakeDir, Message, Move, MSBuild, ReadLinesFromFile, RegisterAssembly, RemoveDir, RemoveDuplicates, RequiresFramework35SP1Assembly, ResolveAssemblyReference, ResolveComReference, ResolveKeySource, ResolveManifestFiles, ResolveNativeReference, ResolveNonMSBuildProjectOutput, SGen, SignFile, TlbImp, Touch, UnregisterAssembly, UpdateManifest, Vbc, VCBuild, Warning, WriteCodeFragment, WriteLinesToFile, XslTransformation, CodeAnalysis, CL, Link, BSCMake, CPPClean, Get.... C:\Program Files\MSBuild\Microsoft\Silverlight\v4.0\Microsoft.VisualStudio.ServiceModel.targets"

Are they really to be ignored?
Share this answer
I found I had a duplicate domain service routine, but even though I commented it out the warning would not go away until I closed Visual Studio and reopened.
Share this answer
Jorge J. Martins 1-Aug-12 11:05am    
I never found out what was really going on.
After reinstalling the hole VS package I picked an earlier backup of the project and restarted coding.
Haven't seen these errors since.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900