Enterprise Library is poo and I hate it.
-
Seriously. I have a fair sized app that I've been working on for quite some time. Previously it has deployed without problems. It also works just fine with the built in webserver, but fails under IIS. However, now it won't. That is, the app deploys, but instead of working, it gives me the following error: Could not load file or assembly 'Microsoft.Practices.EnterpriseLibrary.Security, Version=3.1.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) I've tried everything I can come up with to fix it. I just want to deploy the freaking site so someone can look at it. It's not going into production in a secure environment right. Hell, I don't even care any more if the machine gets owned (it's a VM anyway on a crappy box anyway and is due for a reformat.). I just need to let somebody look at it, and I can't make it happen because of this problem. I'm sick, I've wasted an hour and a half out of my day trying to fix it. If someone can identify what particular "feature" of Enterprise library, .NET, or Visual Studio is causing this problem and tell me how to make it go away, I'd really appreciate it. I only need a quick and dirty hack to make it work. Nothing fancy. Removing all traces of Enterprise library from my system and every project I do now and in the future has just become top priority, so I don't even need a sustainable solution.
-
Seriously. I have a fair sized app that I've been working on for quite some time. Previously it has deployed without problems. It also works just fine with the built in webserver, but fails under IIS. However, now it won't. That is, the app deploys, but instead of working, it gives me the following error: Could not load file or assembly 'Microsoft.Practices.EnterpriseLibrary.Security, Version=3.1.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) I've tried everything I can come up with to fix it. I just want to deploy the freaking site so someone can look at it. It's not going into production in a secure environment right. Hell, I don't even care any more if the machine gets owned (it's a VM anyway on a crappy box anyway and is due for a reformat.). I just need to let somebody look at it, and I can't make it happen because of this problem. I'm sick, I've wasted an hour and a half out of my day trying to fix it. If someone can identify what particular "feature" of Enterprise library, .NET, or Visual Studio is causing this problem and tell me how to make it go away, I'd really appreciate it. I only need a quick and dirty hack to make it work. Nothing fancy. Removing all traces of Enterprise library from my system and every project I do now and in the future has just become top priority, so I don't even need a sustainable solution.
Well, I finally tracked it down. I was using integrated security when connecting to my database. When running under IIS, this was failing. Enterprise library was performing some mystery operation as a result of the error, the result of which was a new exception that swallowed the old one. I still hate it and it is still poo though.