Config failur

Hot Topic

MsiProductCheck element
my vs.net version
pivot table Line Graph.
How to support to create the web site
Lack of Integration with Active Directory
FireFox Compatiblity
xbap downloaded does not use connection properties of IE for proxy
ReportViewer Control
A very technical (I think) VSTO startup question
OTP: Can't open any graphic file !!!

Visual Studio

How can I catch "Add a breakpoint" event?
Data Island+Server Document
Printing online documents is limited to one page, other pages don't appear
Windows Vista Development
Error when installing VS 2005 Beta 2
Error When Deploying Application
Office SP1 & SP2
Can't install VS 2005 Tools for Office
How to prevent autoformatting on dates in excel.
Unable to create Excel Workbook Project

Config failur

I am creationg a service.

When I add an end point in code it works. But when I add it in app.config

I get a exception telling me then the configuration of the service can not understand the attribute "type" in the statmant <service type="xxx" ...

why did the schema change



Answer this question

Config failur

  • dsaniket

    Hi,

    I run into the same problems, did you find a solution

    Please let me know.

    Thanks

    Gerhard

    gerhard.kreuzer@liftoff.at

  • monfu

    Yes, the configuration schema has changed. You now set the service's name instead of the type. For the default ServiceHost that ships with the WCF product, the name resolves to a .NET type string by default. However, this change allows ServiceHost developers to create their own look-up mechanism that does not rely on the .NET type system without needing to develop their own configuration system as well.

    Mark Gabarra

    http://blogs.msdn.com/markgabarra

    This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm



  • G.Peters

    Hi Mark,

    I found a sample app.config, and I see the schema changes. First I think, my problems are solved now, but I get an error in the .config file, as I type 'name' instead of 'type'. The editor underlines the keywords now.

    I start debugging and I get an error message:

    The object of type System.ServiceModel.Configuration.ServicesSection could not be converted to type System.ServiceModel.Configuration.ServicesSection

    I think, there is some versions jam on my installation, please help me out.

    Thanks

    Gerhard

  • J-Rock

    If you have a version conflict, my advice would be to remove the Feb CTP (using the removal app) and install the most recent one (May):

    http://blogs.msdn.com/madhuponduru/archive/2006/05/23/605077.aspx

  • jayant_jkn

    There was a change from "type" to "name" in Feb CTP.

    However, the intellisense installed with that CTP was not updated, so using "name" caused a warning. This was resolved in May CTP.

    If you are using the Feb CTP, here is a fix for the intellisense:

    http://weblogs.asp.net/cibrax/archive/2006/03/07/439763.aspx

  • Jayson Go - Old Account

    Thanks,

    but if I ignore the XML warning, I get a nice error message, as you can see in one of my entries above.

    Do you know. which version conflict happens, and how I can solve it

    Thanks

    Gerhard
  • Config failur
Answer this question