Thanks. I now see that I have loads of .NET frameworks installed some in
C:\Windows\Microsoft.NET\Framework
C:\Windows\Microsoft.NET\Framework64
I see that the runprebuild.bat script now doe snot have the 3.5 .NET
Framework fixed path hardwired and it tries to pick up the currently
installed .NET Framework for 4.0 using registry values.
Running the new r/240runprebuild.bat on a Windows 8.1 Pro 64 bit
system it gives the error...
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\4.0"\MSBuildToolsPath
not found.
Note the " " that seem to be misplaced. My attempts to remove the
quotes " ... " round the key had no effect, but they don't seem to
be needed anyway?
That registry key if properly found though would point on my machine
to the apparently correct location which does contain an msbuild.exe
executable...
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\
I hardwired that in a version of runprebuild.bat and that worked fine
as far as the compile stage, which will need the Visual C# Studio
express installed I assume.
So it must be the script handling picking up the key and key value
needed for the msbuild.exe path from the registry that is not quite
working right yet?
_______________________________________________
Opensim-users mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/opensim-users
