Enterprise Library 6.0, does the Configuration Console work?

In Enterprise Library 5.0 you can add an App.config file, right click on it and have the option to edit the config using the Configuration Console:
This option doesn't seem to be available in Enterprise Libarary 6.0 - is that correct?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

käµfm³d 👽Commented:
There is an extension you can download, but it only appears to install for VS 2012.

quentinAAuthor Commented:
Thanks. I had already downloaded the extension.
I am using VS2103.
The standalone configuration console can be used to set up validators in the App.config of a solution.
When this is done the PublicKeyToken for EnterpriseLibrary is set as null, and the validators don't work.
When the PublicKeyToken is manually updated to PublicKeyToken=31bf3856ad364e35 the validators work correctly.

If I then try to open the App.config in the configuration console, I get the following error message:

 Error Message
Do you know how I should deal with this error?
käµfm³d 👽Commented:
I commented in your other question. When I tried in the configuration console, it added the PKT as expected.
quentinAAuthor Commented:
Do you have the "edit configuration file" as an option when you right click on the App.config in VS2013.
(I don't use VS2012)?

I'm using windows 8.1, 64-bit, VS Professional 2013.
käµfm³d 👽Commented:
No. I can't seem to locate an extension for EL that works in VS 2013. Were you able to locate such?

Now, I did find an article that shows how to hack the .vsix file in order to extend the supported products a given extension supports. I tried it out, and it seems to work, but be warned:  I cannot guarantee that this is 100% safe. If you decide to hack the .vsix file, then you do so at your own risk.

If you decide to try hacking the .vsix file, then all you need to do is add an entry for version 12.0 of VS (since you are using VS 2013). You can simply copy the section for version 11, and then change it to 12.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
.NET Programming

From novice to tech pro — start learning today.