Hello, I'm unable to compile after installing the license with latest 4.3 release. I need to set the windows date time format options to US (see viewtopic.php?f=29&t=6016 ) to avoid an exception in postsharp :
Then I get this message : (I entered a company license)
I will try to switch back to RC until this is fixed. Updated at 16.07.2010 9:10:59After update to latest release of installer, I get another exception:
EDIT: This seems related to the addition of <copyindirectdependencies>true</copyindirectdependencies> in project properties EDIT 2: This is very strange : I've been able to compile one time, and then it fails again... Updated at 23.07.2010 8:25:34I got again this exception.
Then I closed Postsharp pipe server : Dataobjects.Net license agent was not running. This time the solution builds correctly. I made then another test : if I close Postsharp piper server AND Dataobjects.Net license agent, and then rebuild, I reproduce the error. Any idea on this behavior? Updated at 23.07.2010 8:56:18Ok I get it : this happens when a project using Postsharp aspects, but not DataObjects.net is compiled first. Here is a test project. [attachment=0:93mtdys0]TestPostsharpLicenseBug.zip[/attachment:93mtdys0] Steps to reproduce: * Close any postsharp pipe server and DataObject license manager running * Rebuild test project Updated at 26.07.2010 13:15:29Are you sure Alex? I already use the version from 7/20/2010 available at the download section. Postsharp version : 2.0.8.1267 Xtensive.Storage version : 1.0.5605.4108 By the way, could you please put the build number on download page? It's getting hard to know which version is the latest when there are several with the same release number... This thread was imported from our support forum. The original discussion may contain more detailed answer. |
We didn't change PostSharp build this time (i.e. it's still the same PostSharp 2.0 RTW). So most likely the issue is related to PostSharp itself - we'll report about it. Btw, now you can run PostSharp.IntegrityChecker.exe from Lib\PostSharp to check the consistency of the version we ship. Our own investigation has shown the original error is:
We've been able to find the following:
> Are you sure Alex? Sorry, I was really wrong. PostSharp was updated to this version in build 5609 (.NET 4) and 5612 (.NET 3.5). So your version really contains older version of PostrSharp. The most current build was published today in the morning (v4.3.1, build 5680), although I didn't announce this yet. I wanted to test how it is adopted by customers that reported bugs we resolved there. It fully works, but if can wait till tomorrow, I recommend you to do this - I plan to update it. > agree with that! Me too. Descriptions aren't update automatically yet, but I'll do this shortly. Good then... Use new postsharp release from postsharp site. I've reported the bug and they fixed it Yep. Btw, the latest build of DO4 available at Downloads section at X-tensive.com already includes this PostSharp build.
agree with that! olorin wrote: This problem seems to be gone with install of latest 4.3 version. I think It may may have been caused by a version mismatch between postsharp : when the postsharp pipe server is running you may not use the version you think you are using... So the safest way is to wait for the response from PostSharp team. olorin wrote: An indication about this : this version works on build server that is still with an evaluation Dataobjects license, but not on my machine which a company license for which I requested an hardware license. |