.Net 3.5 messing up Regasm

[DuncanL]

The .Net "Register" steps in our build script are trying to run regasm from the v3.5 .Net framework folder - however it is not present there - it is in the "v2.0.50727" folder.

One machine is still working fine, but another has started showing this problem. Any ideas what the difference between the installs of .Net 3.5 might be and how we go about fixing the errant machine?

Thanks.

[kinook]

Update the DOTNET_DIR global macro (or create a project or temporary macro to override the global value) to point to the v2 path. Or copy regasm.exe to the 3.5 path.
http://www.kinook.com/VisBuildPro/Ma...omregister.htm

[DuncanL]

Ah-ha - RTFM! ;-)

Many thanks.

Out of interest, any suggestions on how that ended up being set differently on the two machines? Nobody would have changed in manually, since only two people have access.

[kinook]

The global DOTNET_DIR macro gets initialized (to the highest installed .NET version) when VBP first runs, so my guess is that 3.5 was not installed on machine A but was installed on machine B when VBP was first used. Unfortunately, .NET has become bifurcated since v2.0. With v3.5, parts of it are in the 3.5 path, while other parts are still in the 2.0 path. And it will probably be even more mixed up with v4.0 :^)