Hi, After having upgraded from 4.0.5 to 4.1.0, I experienced the following issues : [1] - Build error: PostSharp: The plug-in "Xtensive.Core.Weaver" required by the assembly "Xtensive.Storage, Version=1.0.0.0, Culture=neutral, PublicKeyToken=93a6c53d77a5296c" was not found. -> This problem was fixed by adding the following in the PropertyGroup section of the .csproj : <usepostsharp>true</usepostsharp> <dontimportpostsharp>true</dontimportpostsharp> [2] - Runtime error: Could not load file or assembly 'Xtensive.Sql.sqlserver, Version=1.0.0.0, [...]' or one of its dependencies. The system cannot find the file specified." -> This problem was fixed by adding a reference to 'Xtensive.Sql.sqlserver' to my project. [3] - Runtime error: I get a DomainBuilderException during the Domain build : DomainBuilderException : Persistent attribute isn't applied. Add the following line to AssemblyInfo.cs for "Test" assembly: [assembly: Persistent(AttributeTargetAssemblies = "Test")]. However, the AssemblyInfo.cs file already has the line with Persistent attribute. Please find here after the complete stack traces (pressing 3 times F5 after the first exception occurs) : Exception #1
Exception #2 :
Exception #3:
Questions: 1- Problems [1] and [2] seem to indicate that the build process that I use is not correct anymore for DO4. Since my projects were created with DO 4.0.5, I could not use the project templates provided in the samples without rewriting all my projects. Could you provide some information about best practices or recommendations on how to build an application that uses DO4 ? 2- How can I fix problem [3] ? Best regards, Auguste Updated at 10.11.2009 11:16:31Hello, I created a new project from scratch using the template provided in Visual Studio, and added my source code files. Everything works perfectly in that case. Then I compared the two .csproj files with a merge tool and edited .csproj of the migrated project : now both .csproj files are identical . However, I am still not able to have a migrated version that works : a NullReferenceException occurs at runtime for the migrated project. I already : - removed bin and obj folders before build - checked that the .sln files are identical (except of coarse for the path to the csproj) What else can I check ? I can send you the source code of both projects for further investigation. This thread was imported from our support forum. The original discussion may contain more detailed answer. |
Yes, your analysis is fully correct. Likely, you didn't add this line to .csproj:
See http://blog.alexyakunin.com/2009/10/add ... w-way.html Another good way to check if everything is correct is to create similar project based on our on template, compare your own with it by some 2-way comparison/merge tool (e.g. Beyond Compare) and migrate all the missing parts from:
I apologize for inconvenience. Most likely, this is the last serious change to build process we made: current solution allows us to control everything there. We resolved the issue:
|