Trouble building on OSX

[Bungalow12]

I'm having trouble restoring NuGet packages:

  - monoandroid10 (MonoAndroid,Version=v1.0)
  - monotouch10 (MonoTouch,Version=v1.0)
  - net46 (.NETFramework,Version=v4.6)
  - net461 (.NETFramework,Version=v4.6.1)
  - netcore50 (.NETCore,Version=v5.0)
  - netcoreapp1.0 (.NETCoreApp,Version=v1.0)
  - netcoreapp2.0 (.NETCoreApp,Version=v2.0)
  - netstandard1.3 (.NETStandard,Version=v1.3)
  - netstandard1.5 (.NETStandard,Version=v1.5)
  - netstandard2.0 (.NETStandard,Version=v2.0)
  - xamarinios10 (Xamarin.iOS,Version=v1.0)
  - xamarinmac20 (Xamarin.Mac,Version=v2.0)
  - xamarintvos10 (Xamarin.TVOS,Version=v1.0)
  - xamarinwatchos10 (Xamarin.WatchOS,Version=v1.0) (NU1202) (Moq)```
Any idea what I can do to rectify this so I can use this on OSX?
Or do you have pre-built DLLs available anywhere I can reference?

[stakx]

Sorry, I don't understand your post at all. Are you trying to build Moq from source? If so, using what tools? (You'd probably need to have Mono installed in order to compile the net45 target.) What does that list of targets above mean? (Moq v4 currently only has two targets: net45 and netstandard1.3.)

If you just want to use Moq, why not just use the Moq NuGet package? (If you just want DLLs, download the NuGet package from NUGet.org, rename it to a .zip file, then open it. You'll find the DLLs in the lib/ folder.)

[Bungalow12]

Oh... Yeah I guess that makes a lot more sense. :/ Regardless there is no easy way I have found to build Moq from source on OSX. So that would still be awesome if it was made easier.

…

On Wed, Nov 28, 2018 at 11:07 PM stakx ***@***.***> wrote: Sorry, I don't understand your post at all. Are you trying to build Moq from source? If so, using what tools? (You'd probably need to have Mono installed in order to compile the net45 target.) What does that list of targets above mean? If you just want to use Moq, why not just use the *Moq* NuGet package? (If you just want DLLs, download the NuGet package from NUGet.org, rename it to a .zip file, then open it. You'll find the DLLs in the lib/ folder.) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#726 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACIeJZAfrf-4DQtIHHJqLSJ5Yg0c9MS7ks5uz4e4gaJpZM4Y43R3> .

[stakx]

@Bungalow12 - Well, would you be interested in looking into this? I can't be of much help there, as I don't have access to an Apple machine. I'm pretty sure that it would take a recent Mono installation because you'd need a set of .NET Framework 4.x reference assemblies to build against. I also suspect that the build process as a whole might have to be rewritten to make use of the dotnet toolchain (at the very least, dotnet msbuild instead of msbuild)—this might possibly be non-trivial. We'd also have to enhance the CI setup to run an extra build, verifying that Moq can be compiled on Unix-like systems. I'd expect this would be quite a bit of work.

[Bungalow12]

Yeah I’ll take a look into it.

…

On Thu, Nov 29, 2018 at 11:52 PM stakx ***@***.***> wrote: @Bungalow12 <https://github.com/Bungalow12> - Well, would you be interested in looking into this? I can't be of much help there, as I don't have access to an Apple machine. I'm pretty sure that it would take a recent Mono installation because you'd need a set of .NET Framework 4.x reference assemblies to build against. I also suspect that the build process as a whole might have to be rewritten to make use of the dotnet toolchain (at the very least, dotnet msbuild instead of msbuild). — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#726 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACIeJfY2lpwkxst5dE8hlP_CDgwj0OMLks5u0OOtgaJpZM4Y43R3> .

[stakx]

Hi @Bungalow12, just going through issues and saw this one has been idle for a while. Did you ever get around to look into Moq4 build script improvements for OSX? (If not, I suggest we close this issue for now. We can mark it as unresolved, and always open again in the future if we pick up that particular thread again.)

[Bungalow12]

It’s definitely a nice to have but hardly vital. I’ll close the issue.