Title says it all. I start a new DataObjects web project. Add the sqlserver provider as my default. Create a VERY simple entity that reflects a table in the database. Build throws an exception complaining: System.Security.VerificationException: {"Operation could destabilize the runtime."} The machine this is on is a new install of Windows 7 64 bit. This is running in VS2010, or rather not running. Using the latest available package from xtensive. |
I just studied your sample, and identified a set of issues. I my case they were different - i.e. I didn't seen verification exception, but I suspect, it could occur because you were trying to run .NET 4.0 application in .NET 2.0 application pool. Anyway, let's review what I found: 1. web.config there is pretty strange It references a set of .NET 3.5 assemblies, although you use version of DO for .NET 4.
Moreover, target framework inside I tried to install this application both to "ASP.NET v4.0" and "ASP.NET 4.0 Classic" application pools, and in both cases my IIS 7 was reporting "HTTP 500.19 - Internal Server Error" pointing to I compared your This helped almost instantly. 2. the same is about .csproj. It seems it's VS2008 project ( I fixed this by comparing it with .csproj from ASP.NET sample as well. 3. There were few minor bugs in code You didn't register any types in
Also, you didn't create any persistent type, so
After all these changes the application began to show "Hello world!" message. Finally, I made 2 cosmetic improvements: a) I renamed your
b) I changed You can download version of your application with my modifications to study the changes. I recommend you to compare it with your original code using a tool like Beyond Compare. In addition, I added So to test everything quickly, download the archive, extract it somewhere, run Remember that:
Good luck with testing DO further! Original answer: Could you send us the project to support@(our web site).com? That's the only easy way to check/reproduce this. This is only possible, if either our aspects or PostSharp inject unverifiable MSIL code. I remember there were some issues like this when we were migrating to PostSharp 2.0 - simply because our weaver was unstable. But currently this should never happen. I can certainly send you the project. The only thing you would need to change is to point it at a sqlserver instance. Check your mail it should be there shortly. Thanks! I studies your sample. See the answer above - I just edited it. Update: I already understood how such web project could appear: you've built an application using our Web Application template! It seems we've occasionally merged the changes made to it in .NET 3.5 branch to the default (.NET 4.0) branch. This also means we'll update the latest installer today. I apologize for this issue. Thank you once more for contacting us. |
Latest = v4.3.5? Important, because it was just published, although this isn't officially announced.