This tool falls woefully short providing rudimentary functionality for the validation block. There is no ability to move validation checks between levels, rearrange levels, test validation, or maintain connection to DLLs after shutting the tool down and returning to work at a later time. Reloading DLLs causes work to be overridden and will erase previously created validation checks for properties of classes. Moreover, there is no integration with VS2013 out of the box, but there is the ability to include a reference to the tool and right-mouse click to start the tool. Additionally, only public properties are validation applicable. No private fields, properties, or types are available for validation.
Enterprise Library Configuration Console Extension seems to be failing on Visual Studio 2012.
So, I installed it directly from the Download @ http://www.microsoft.com/en-us/download/details.aspx?id=38789 instead of using the standard extension mechanism into VS, and it worked well. The built-in mechanism was downloading Console version 5), but Enterprise Libraries are currently on version 6.x
I have written a custom validation provider to use with EntLib Config. Console V6 in VS 2012.
However I am not able to find where VSIX package is installed, because, as per documentation, I should copy the DLL to the console's installation directory.
Any help would be appreciated.
Can't get it to work using VS2012 and Enterprise Library 6
Error launching the configuration console
Could not locate the Enterprise Library binaries required to launch the configuration console. Either use NuGet to add references to the Enterprise Library blocks or set a value for the 'Enterprise Library binaries path' property on the solution to indicate the location of the binaries
<compilation debug="true" targetFramework="4.5" />
<httpRuntime targetFramework="4.5" />
<package id="EnterpriseLibrary.Common" version="6.0.1304.0" targetFramework="net45" />
<package id="EnterpriseLibrary.Data" version="6.0.1304.0" targetFramework="net45" />
Inside the solution file :
GlobalSection(ExtensibilityGlobals) = postSolution
EnterpriseLibraryConfigurationToolBinariesPathV6 = packages\EnterpriseLibrary.Common.6.0.1304.0\lib\NET45;packages\EnterpriseLibrary.Data.6.0.1304.0\lib\NET45;packages\EnterpriseLibrary.Logging.6.0.1304.0\lib\NET45;packages\EnterpriseLibrary.ExceptionHandling.6.0.1304.0\lib\NET45;packages\EnterpriseLibrary.ExceptionHandling.Logging.6.0.1304.0\lib\NET45;packages\EnterpriseLibrary.Validation.6.0.1304.0\lib\NET45
I had the same issue.
In my case i just had to install Enterprise Library 6 Config tool.
I had the Enterprise Library 5 Config tool installed from the Visual Studio Gallery which was obviously the wrong Version.
I have Enterprise Library 4.1 version installed in my office system and I am currently working on an application .Net 4.0 with Silverlight where the enterprise library is used for logging purpose. The app.config file contains the settings required for logging the errors and it is working fine. But, I don't see the Edit Configuration menu when I right click on the App.config file. I installed the file given in this link and after that the menu is visible. But, since it is not applicable for 4.1 version of the library, it is not working. Is a similar tool available for adding this Extension to VS 2010 for the 4.1 version of enterprise library?
If I have EnterpriseLibrary.Config enabled, and I have WiX 3.6 installed with a wix project in my solution, Visual studio 2012 crashes after every compile. If I disable EnterpriseLibrary.Config it works fine. Also note I have Resharper 7.0 installed.
From the EnterpriseLibrary documentation on creating a custom provider with full integration :
"Compile your project, and copy your provider assembly into the same folder as the configuration tools. "
Is it possible to do the same with the Visual Studio Extension ? I've located the folder where the extension is installed and copied my assembly there but it doesn't seem to work. I know the solution is much less user-friendly because installing a custom provider requires the user to dig in hidden folders. Maybe there's another way ?
I've tried restarting Visual Studio and it did work. However, I'm still wondering if there's another way to do this (instead of digging in hidden folders and copying my custom provider along with the config tool).
Hi, if you want your custom provider to show up in the config tool when right clicking on the .config file and launching the config tool, you should open the Visual Studio solution (.sln) file with a text editor, and update the EnterpriseLibraryConfigurationToolBinariesPath global section (at the end of the file) to include a relative path to where your custom binary is located. This is how the config tools finds the Enterprise Library built-in assemblies.
Not for v5.0 config tool. You'll have to use the stand-alone version.
We will consider VS2012 integration for the next version of Enterprise Library. Suggest it/vote on http://entlib.uservoice.com.
I managed to install the extension on VS2012 RC.
You have to extract vsix (it's just a ZIP archive)
locate extension.vsixmanifest file (it's an xml document)
change <VisualStudio Version="10.0"> to <VisualStudio Version="11.0"> and save changes
than you only have to create a zip archive from the extracted files and rename it that the extension is vsix instead of zip.
That is it.
I have installed the EnterpriseLibrary.Config tool for VS 2010, but can't figure out how to launch it. I don't see it anywhere within VS 2010 (outside of the disable/uninstall area of the Extension Manager in VS 2010). Any tips will be appreciated!
If you open the context menu for your application config file ("app.config" or similar) - for example in the solution explorer - you will find the option "Edit Enterprise Library V5 Configuration" (with the well-known orange colored icon). This will start the appropriate config editor with your application config pre-loaded.
I would like to open the Enterprise Library Configuration Editor from within Visual Studio 2010 (SP1) to edit the enterprise library settings.
If the config file exists in a project, the Editor opens successfully.
If the config file does not exist in a project, i.e. Solution Items, the Editor fails to open. There are two available editors:
1. Installed using Enterprise Library 5.0 Optional Update 1.msi. This fails with message "Cannot retrieve target framework for the current selection. The editor will not be launched".
2. Installed using Microsoft.Practices.EnterpriseLibrary.ConfigConsole.vsix. This fails with the message "Object reference not set to an instance of an object".
The following solution properties are set:
Enterprise Library 5 Assembly Set set to Microsoft Signed (or machine default)
Enterprise Library binaries path set to location of the v5.0.505.0 binaries.
How can I open the Editor in VS for config files not in a project?
This behavior is actually by design. The config console launcher needs to know the project type and the target framework in order to launch the proper config tool. Please include the config file in a project or use the standalone config console (not integrated with VS).