It seems not to be possible to build without installing DO anymore. I need this on build server, and that would be practical for the rest of the team.

Scenario: I have all the binaries necessary to build (basically Bin, Common, Lib folders of Program Files) in a folder in source control.

I have a Property in my .csproj like this : <dataobjectsdotnetpath>$(MSBuildProjectDirectory)..\ExternalLibs\DataObjects.Net</dataobjectsdotnetpath>

I added the following targets : <import project="$(MSBuildToolsPath)\\Microsoft.CSharp.targets"/> <import project="$(DataObjectsDotNetPath)\\Common\\DataObjects.Net.targets"/> <import project="$(DataObjectsDotNetPath)\\Common\\Defaults.MixedProject.targets"/>

This was working with DO 4.3 RC1, but now I get :

POSTSHARP : postsharp error PS0099: Unhandled exception (, 32 bit, CLR 4.0, Release): System.InvalidOperationException: DataObjects.Net is not installed. Please install it or run Install\Install.bat. 
POSTSHARP : postsharp error PS0099:    at Xtensive.Core.Weaver.PlugIn.Initialize() 
POSTSHARP : postsharp error PS0099:    at PostSharp.Extensibility.Task.^pFnf8wEt(TaskTypeConfiguration _0, XmlElement _1, Project _2) 
POSTSHARP : postsharp error PS0099:    at PostSharp.Extensibility.Configuration.TaskTypeConfiguration.^N565HL29(XmlElement _0, Project _1) 
POSTSHARP : postsharp error PS0099:    at PostSharp.Extensibility.TaskCollection.Add(String taskTypeName) 
POSTSHARP : postsharp error PS0099:    at PostSharp.Extensibility.Tasks.AutoDetectTask.Execute() 
POSTSHARP : postsharp error PS0099:    at PostSharp.Extensibility.Project.ExecutePhase(String phase) 
POSTSHARP : postsharp error PS0099:    at PostSharp.Extensibility.Project.Execute() 
POSTSHARP : postsharp error PS0099:    at PostSharp.Hosting.PostSharpObject.ExecuteProjects() 
POSTSHARP : postsharp error PS0099:    at PostSharp.Hosting.PostSharpObject.InvokeProject(ProjectInvocation projectInvocation)

Neither Postsharp or DataObjects are installed on build server.

Is it a new limitation?

Updated at 26.05.2010 7:49:20

Ok, I'll define it : thanks for your answer.

This thread was imported from our support forum. The original discussion may contain more detailed answer.

asked May 25 '10 at 13:52

olorin's gravatar image


Ups, that's bug.

The new part of the weaver responsible for license checks currently requires DataObjectsDotNetPath environment variable to function. We'll fix this ASAP, workaround for now is to define it.

(May 25 '10 at 13:52) Alex Yakunin Alex%20Yakunin's gravatar image

One Answer:

We just discussed this - that's not a bug, but issue. We were trying to implement this w/o env. variable, but failed: since weaver is executed inside PostSharp, and (as it seems) PostSharp makes a shadow copy of it, it isn't easy to determine its actual path. So currently we don't know how to fix this, but we'll look for options.

answered May 26 '10 at 07:56

Alex%20Yakunin's gravatar image

Alex Yakunin

Your answer
Please start posting your answer anonymously - your answer will be saved within the current session and published after you log in or create a new account. Please try to give a substantial answer, for discussions, please use comments and please do remember to vote (after you log in)!
toggle preview

powered by OSQA