For a build server using msbuild (not Visual Studio), do the NetAdvantage WPF components still need to be installed on the build server ? We can't just reference DLL's copied to the server ?
I found this link that said just save yourself the headache and install NetAdvantage on the build server, but wasn't sure if that also applied to WPF http://blogs.infragistics.com/blogs/eblankenship/archive/2007/07/16/building-apps-using-netadvantage-with-team-build.aspx
An alternative suggested was a workaround to clear out the contents of the licenses.licx file - but will that cause problems trying to run ?http://news.infragistics.com/forums/p/9004/35136.aspx#35136
Hello,
The following post has a solution that you may be able to use:
http://blogs.infragistics.com/forums/p/41706/231562.aspx#231562
Let me know if you have any questions with this matter.
I know it's been a while, but I'm curious has anything been done about this? It is proving to be somewhat of an inconvenience for us here, and would like to not install on our build server if at all possible. We are attempting to keep development as clean and out of the box of an SVN checkout as can be.
At the moment, the notes about installing the products on the build servers is still valid for all of the .NET products including WPF. After you install NetAdvantage for WPF you shouldn't have any issues with building your apps on the build server.
We've identified this as being a less than optimal situation and I've added a note to our backlog item.