Welcome to MSDN Blogs Sign in | Join | Help

Using Visual Studio Intellisense to Edit WCF Configuration files.

If you are using Visual Studio 2005 below is how you can enable intellisense to edit your WCF config files. 

Copy the Attached WCF Configuration schema file to your VS installation folder at %Program Files%\Visual Studio 8\Xml\Schemas. You will find DotNetConfig.xsd in the same directory. Open this file in notepad and  following right after the xs:schema element add the below line,

<xs:include schemaLocation="WCFConfig.xsd" /> 

You will now have intellisense support for your WCF configuration files in VS!

Published Tuesday, March 06, 2007 3:33 PM by govindr
Filed under: ,

Attachment(s): WCFConfig.xsd

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

# Using Visual Studio Intellisense to Edit WCF Configuration files.

Thursday, March 29, 2007 4:50 AM by A BULL's view of LIFE and TECHNOLOGY

# re: Using Visual Studio Intellisense to Edit WCF Configuration files.

Thanks for posting this.  This worked perfectly.    

Tuesday, June 26, 2007 8:13 AM by blogx

# re: Using Visual Studio Intellisense to Edit WCF Configuration files.

I was wondering if anyone has written an installer/script/Visual Studio Plugin etc. which can automatically modifiy the DotNetConfig.xsd as required.  Any advice on the best way to start such a task would be greatly appreciated.  

thanks in advance.

Friday, July 20, 2007 8:46 AM by Brandon

# re: Using Visual Studio Intellisense to Edit WCF Configuration files.

I know this might be a pipedream, but... I would love a common web location containing non-installed schemas so that I do not have to search for them in various microsoft forums and such - yes, I am a lazy searcher. The schema you made available here for wcf configuration is great. And in general I love intellisense while updating xml so that I do not have to remember the exact element and attribute names. For instance, the other day I needed to create a manifest file part by hand, and I found conflicting information about the exact namespace to use for various elements. After a bit of trial and error, I think I got it right. Later on I stumbled upon the manifest schema on msdn library, ugh.

Thanks for the posting.

Wednesday, August 15, 2007 12:51 PM by frinkfree

# .net fw 3.0

Why this schema does not come along with the SDK ?

Thursday, July 03, 2008 10:20 AM by mlh

# re: Using Visual Studio Intellisense to Edit WCF Configuration files.

Thanks a lot for posting this .

Tuesday, August 19, 2008 12:43 AM by Russell stitt

Leave a Comment

(required) 
required 
(required) 

  
Enter Code Here: Required
 
Page view tracker