Welcome to DU! The truly grassroots left-of-center political community where regular people, not algorithms, drive the discussions and set the standards. Join the community: Create a free account Support DU (and get rid of ads!): Become a Star Member Latest Breaking News Editorials & Other Articles General Discussion The DU Lounge All Forums Issue Forums Culture Forums Alliance Forums Region Forums Support Forums Help & Search

DaveJ

(5,023 posts)
Tue Jun 4, 2013, 08:43 AM Jun 2013

Another WCF in VS 2012 Express Question

Not sure if anyone here uses this environment, but I'm still just trying to teach myself.

I noticed that in every example that I come across, after they create a WCF project, the web.config contains a <services> section in the <system.ServiceModel> section.

OTOH, whenever I create a WCF project, I see a <behaviors> section instead o <services>.

This makes it a little confusing when trying to follow tutorials and I was wondering if something has changed in 2012.

3 replies = new reply since forum marked as read
Highlight: NoneDon't highlight anything 5 newestHighlight 5 most recent replies
Another WCF in VS 2012 Express Question (Original Post) DaveJ Jun 2013 OP
The .config files support IntelliSense when edited in VS ChromeFoundry Jun 2013 #1
This isn't really an intellisense issue DaveJ Jun 2013 #2
Think I finally found the answer DaveJ Jun 2013 #3

ChromeFoundry

(3,270 posts)
1. The .config files support IntelliSense when edited in VS
Tue Jun 4, 2013, 04:13 PM
Jun 2013

Their XML Schema Definition is defined in local files:
C:\Program Files (x86)\Microsoft Visual Studio 11.0\Xml\Schemas\DotNetConfig*.xsd

depending on which version of the framework you are developing against.

DaveJ

(5,023 posts)
2. This isn't really an intellisense issue
Tue Jun 4, 2013, 05:09 PM
Jun 2013

Looks like nobody around here messes with WCF much. I was just wondering why web.config doesn't look the same way it does in the tutorials. No Services section. But it works anyway. I'm just learning so I'm sure this would be common sense to a WCF pro.

DaveJ

(5,023 posts)
3. Think I finally found the answer
Tue Jun 4, 2013, 05:48 PM
Jun 2013

It took me awhile, but it looks like .Net version 4 introduced default endpoints and bindings making the Services section unnecessary.

http://stackoverflow.com/questions/16810997/confusion-about-default-wcf-project-web-config-layout

Thanks!

Latest Discussions»Retired Forums»Website, DB, & Software Developers»Another WCF in VS 2012 Ex...