WCF

1. Read the question carefully
2. Understand that English isn't everyone's first language so be lenient of bad spelling and grammar
3. If a question is poorly phrased then either ask for clarification, ignore it, or mark it down. Insults are not welcome
4. If the question is inappropriate then click the 'vote to remove message' button

1. Choose the correct forum for your message. Posting a VB.NET question in the C++ forum will end in tears.
    
   
2. Be specific! Don't ask "can someone send me the code to create an application that does 'X'. Pinpoint exactly what it is you need help with.
    
   
3. Keep the subject line brief, but descriptive. eg "File Serialization problem"
    
   
4. Keep the question as brief as possible. If you have to include code, include the smallest snippet of code you can.
    
   
5. Be careful when including code that you haven't made a typo. Typing mistakes can become the focal point instead of the actual question you asked.
    
   
6. Do not remove or empty a message if others have replied. Keep the thread intact and available for others to search and read. If your problem was answered then edit your message and add "[Solved]" to the subject line of the original post, and cast an approval vote to the one or several answers that really helped you.
    
   
7. If you are posting source code with your question, place it inside <pre></pre> tags. We advise you also check the "Encode "<" (and other HTML) characters when pasting" checkbox before pasting anything inside the PRE block, and make sure "Use HTML in this post" check box is checked.
    
   
8. Be courteous and DON'T SHOUT. Everyone here helps because they enjoy helping others, not because it's their job.
    
   
9. Please do not post links to your question into an unrelated forum such as the lounge. It will be deleted. Likewise, do not post the same question in more than one forum.
    
   
10. Do not be abusive, offensive, inappropriate or harass anyone on the boards. Doing so will get you kicked off and banned. Play nice.
     
    
11. If you have a school or university assignment, assume that your teacher or lecturer is also reading these forums.
     
    
12. No advertising or soliciting.
     
    
13. We reserve the right to move your posts to a more appropriate forum or to delete anything deemed inappropriate or illegal.

[DataContract]
public class Team
{
    [DataMember]
    public Employee[] Members {get; set;}
    
    [DataMember]
    public Employee Leader {get; set;}
}

[DataContract]
public class Employee
{
    [DataMember]
    public string Name {get; set;}
}

[DataContract]
public class Employee
{
    [DataMember]
    public string Name {get; set;}
 
    //This is new
    [DataMember]
    public int ID {get; set;}
}

[DataContract]
public class Person
{   
    [DataMember]
    public int ID {get; set;}
}

[DataContract]
public class Employee : Person
{
    [DataMember]
    public string Name {get; set;}
}

jschell wrote:

Other than that I would consider your base class example (Employee/Person)
suspect because it should only occur if someone badly messed up the original
architecture.

Collin Jasnoch wrote:

This is not at all true. An object that is published in a webservice can be used
with in the system publishing the service. If that system decides to extend the
object for whatever reason it should be allowed to with out breaking its
publishing, thus having to version etc.

Collin Jasnoch wrote:

My example was merely that, an example. It was a dumbed down classic 'employee'
and I would hardly say that if someone decided to add a FK relationship to their
internal design it is a poor design.

Collin Jasnoch wrote:

In fact, for all purposes that is how it will be serialized. This is in fact
common refactoring practice (not poor design adjustments).

Collin Jasnoch wrote:

Please read posts more carefully before critizing someones 'simple' example as a
poor design. There was no design in it. It was meant to be an example for clear
question that would obtain a clear answer.

Collin Jasnoch wrote:

To which you did not answer but provided a link. Useful link, but still not an
actual answer. Move along, nothing to see here.

Collin Jasnoch wrote:

Who the frak cares about poor design or any design for that matter in this
thread?

jschell wrote:

Still not clear...you are both defending the design and claiming that it isn't a
design.

Collin Jasnoch wrote:

For example

Collin Jasnoch wrote:

lets define Team like this:

Collin Jasnoch wrote:

and we will define (at first) Employee like this:

Collin Jasnoch wrote:

So we can 'Extend' in 2 ways (well that I see and want to know about)

Collin Jasnoch wrote:

First:

Collin Jasnoch wrote:

Second instead of the ID being in the Employee we decide to make a base
.... And have Employee inherit from it.

Collin Jasnoch wrote:

In either case I am wondering will the client still receive the Employee object
as it knows it (i.e. there is not an ID property)?

Collin Jasnoch wrote:

Or will one of the cases or maybe both, cause the Employee object to fail
construction and not return anything (i.e. receive a Null even though the
service populates it)?

jschell wrote:

DataMember has Properties which can change the behavior.
 
Read this
and drill down into referenced articles as well.
 
http://msdn.microsoft.com/en-us/library/ms733832.aspx[^]

Collin Jasnoch wrote:

Which does not provide an answer. I was still forced to go through building up my services and testing them. T

WCF Service Host cannot find any service metadata. This may cause the client application to run improperly. Please check if metadata is enabled. Do you want to exit?

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
 
  <system.web>
    <compilation debug="true" />
  </system.web>
 
  <system.serviceModel>
    <services>
      <service name="WcfServiceLibrary1.CustomerService"
               behaviorConfiguration="Metadata">
        
        <endpoint address="" 
                  binding="wsHttpBinding" 
                  contract="WcfServiceLibrary1.IService1">
          <identity>
            <dns value="localhost" />
          </identity>
        </endpoint>
        
        <endpoint address="mex" 
                  binding="mexHttpBinding" 
                  contract="IMetadataExchange" />
        <host>
          <baseAddresses>
            <add baseAddress="http://localhost:8000" />
          </baseAddresses>
        </host>
        
      </service>
    </services>
 
    <behaviors>
      <serviceBehaviors>
        <behavior name="Metadata">
          <serviceMetadata httpGetEnabled="true" />
        </behavior>
        <behavior>
          <serviceMetadata httpGetEnabled="True"/>
          <serviceDebug includeExceptionDetailInFaults="False" />
        </behavior>
      </serviceBehaviors>
    </behaviors>
  </system.serviceModel>
 
</configuration>
 

Kevin Marois wrote:

WCF Service Host cannot find any service metadata. This may cause the client application to run improperly. Please check if metadata is enabled. Do you want to exit?

thatraja

---

FREE Code Conversion VB6 ASP VB.NET C# ASP.NET C++ JAVA PHP DELPHI | Nobody remains a virgin, Life screws everyone