WCF service warning - Client proxy generation for service 'MyProject.Web.MyService' failed: Generating metadata files...

Question

0.00/5 (No votes)

See more:

VS2010

, +

Hi
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?

Using:
VS 2010 Ultimate
.NET Framework 4
Silverlight 4

Thanks

Posted 24-Apr-12 4:52am

Jorge J. Martins

Add a Solution

2 solutions

Solution 2

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.

Posted 1-Aug-12 4:01am

Mivoat

Comments

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.

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

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

Jorge J. Martins · Accepted Answer · 2012-04-25T22:22:00

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 'http://schemas.microsoft.com/developer/msbuild/2003' has invalid child element 'GenerateWcfClientFilesTask' in namespace 'http://schemas.microsoft.com/developer/msbuild/2003'. 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?