You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 25, 2020. It is now read-only.
While a Windows dev myself, I'm a cheap bastard and having a Linux host is the way to go for me. I currently use DigitalOcean, with Jekyll building on git commit/push.
I thought I'd start a bit of a discussion and discovery to whats needed to get Pretzel working on mono.
So far, to get it building
Mono doesn't have nuget support? Or nuget is built to a not nuget profile, I'm not sure, removing the nuget task from the csproj makes it build as all the references were there as I'd previously built on .NET. Apparently nuget does have mono support, so perhaps the nuget.exe in the repo is out of date?
It doesn't have to be removed, but the ILMerging does not work. This can be left to 'error' out or removed from the csproj. IL-Repackor Fody.Costura might be options.
Because the ILMerging doesn't work, the MEF stuff doesn't work.
Specifically, var first = new AssemblyCatalog(Assembly.GetExecutingAssembly()); would need to be changed to
AggregateCatalog first = new AggregateCatalog();
first.Catalogs.Add(new AssemblyCatalog(Assembly.GetExecutingAssembly()));
first.Catalogs.Add(new AssemblyCatalog(Assembly.GetAssembly(typeof (SanityCheck))));
Ideally some sort of ILMerging that works with mono would be best
Fixed
Todo
Confirm working on *Nix
ILMerging/equiv for single exe
Nuget all the things.
fixing paths - baking (and thus serving up via taste) fail pretty epically
While a Windows dev myself, I'm a cheap bastard and having a Linux host is the way to go for me. I currently use DigitalOcean, with Jekyll building on git commit/push.
I thought I'd start a bit of a discussion and discovery to whats needed to get Pretzel working on mono.
So far, to get it building
Mono doesn't have nuget support? Or nuget is built to a not nuget profile, I'm not sure, removing the nuget task from the csproj makes it build as all the references were there as I'd previously built on .NET. Apparently nuget does have mono support, so perhaps the nuget.exe in the repo is out of date?
It doesn't have to be removed, but the ILMerging does not work. This can be left to 'error' out or removed from the csproj. IL-Repack
or Fody.Costuramight be options.Because the ILMerging doesn't work, the MEF stuff doesn't work.Specifically,
var first = new AssemblyCatalog(Assembly.GetExecutingAssembly());would need to be changed toIdeally some sort of ILMerging that works with mono would be bestFixed
Todo
baking(and thus serving up viataste) fail pretty epically