How to get Enterprise Library 3.1 working in VS 2008
Enterprise Library 3.1 was published for Visual Studio 2005. That is to say: the Guidance Packages and the integrated Configuration Tool were built to work with Visual Studio 2005. The rest of the library works against .NET 2.0 and continues to work with .NET 3.5 apps.
We have done some work to get the integrated tool to work in Visual Studio 2008. If you run the following registry script it will change the keys where VS looks to load the integrated tool package. After you run the script, you will need to run devenv /setup from the Visual Studio 2008 command prompt.
You can download the file from the EntLibContrib project on CodePlex from here.
[edit]
I will try and be a little clearer for the steps:
1. Install EL 3.1 (you don't need the Guidance Packages)
2. Run the script
3. Run devenv /setup from the VS 2008 command prompt
Wheels from the album "Pressure Chief" by Cake
Comments
Anonymous
March 13, 2008
If you want to use "take full advantage of Enterprise Library 3.1", Scott Densmore just posted a blogAnonymous
March 13, 2008
If you want to use "take full advantage of Enterprise Library 3.1", Scott Densmore just postedAnonymous
March 13, 2008
Scott just posted on how to get Enterprise Library 3.1 installed with Visual Studio 2008. Check it outAnonymous
March 13, 2008
Scott just posted on how to get Enterprise Library 3.1 installed with Visual Studio 2008. Check it outAnonymous
March 13, 2008
ショートノーティスです♪ Enterprise Libraty 3.1 を Visual Studio 2008 で使うためのユーティリティが CodePlex にてリリースされました。 こちら からダウンロードできます。Anonymous
March 13, 2008
Integrare l'Enterprise Library in Visual Studio 2008Anonymous
March 16, 2008
Please, clarify the order of operations:
- Install EL3.1 (with the integrated tool)
- Run the script
- Run devenv / setup Is it correct? Thank you
Anonymous
March 20, 2008
I tried the above order. but getting an error. Could you please helpAnonymous
March 27, 2008
devenv does not appear to have a /setup switch? Can you please advise the correct syntax? __AllanAnonymous
March 27, 2008
I believe the .reg file assumes you installed the ent lib in c:program files... and that windows is installed in c:windowssystem32 If your system doesn't match that you may need to edit the reg file prior to running it and inserting the values into your registry.Anonymous
March 27, 2008
If you already ran the reg file and you didn't install entlib in c:program files or windows isn't in c:windows, you will need to go in and edit the registry with regedit. Search for '488366a4-630c-4a0e-a6a2-b019cee13bea' There are a couple places to update, so look at all the sub nodes from '488366a4-630c-4a0e-a6a2-b019cee13bea' and make your changes. Then run the above devenv command and you should be good to go. It worked for me.Anonymous
April 01, 2008
what changes should i do in '488366a4-630c-4a0e-a6a2-b019cee13bea'Anonymous
April 14, 2008
EL 3.1 won't appear in VS2008 on Vista64. I edited the .reg to change "Program Files" to "Program Files (x86)" (the default install location) before running the install steps as outlined. Also made sure I ran the steps logged in as administrator and as an admin install (msiexec /a) to boot. Just for simple tests I created a project and added an app.config file and right-clicked on it for the editor. Nothing in the context menu (as I would expect from prior VS2005 install, albeit those were on XP32bit). Any suggestions? MikeAnonymous
May 06, 2008
Works great, thanks. And did not break the integrated tool for VS 2005.Anonymous
May 14, 2008
The comment has been removedAnonymous
May 14, 2008
Man am I tired. In the above post it shoud read "I did not get the context menu item to appear ..." MagnusAnonymous
May 14, 2008
The simplest way to get it to work in 64-bit Vista may actually be to follow the directions here http://blog.lyalin.com/2008/01/visual-studio-2008-and-enterprise.html. Haven't tried it thou. MagnusAnonymous
May 14, 2008
At last! I even managed to get the context menu item to appear when right-clicking app.config. After having searched through and corrected the registry as described above I kept getting an error, "The operation could not be completed", when running devenv /setup. If you are running on Vista you need to do this from the VS2008 Command Prompt runas /env /user:Administrator "devenv.exe /setup" That did the trick. Magnus