Robert Muehsig

My target was to get a single .exe, but I need to try if the "place MahApps.Metro.dll beside the .exe" works for my application. The workaround is of course not...

I tried the following with the latest ILRepack (I copied the ILRepack.exe in the bin/debug folder so I don't have those long paths) ILRepack.exe /verbose /log /out:merged/OneOffixx.ConnectClient.WinApp.exe OneOffixx.ConnectClient.WinApp.exe System.Windows.Interactivity.dll Microsoft.Practices.ServiceLocation.dll...

Ah - will try to change it and see if MahApps will take it via a PR. Just to make sure I understand - such resources in XAML are detected...

I try this approach and changed all lines which points directly to MahApps.Metro to a method which invokes the following code: private static string GetCurrentAssemblyName() { return typeof(ThemeManager).Assembly.GetName().Name; } Sadly...

This might work. As an alternative: Maybe the ILRepack user could use a special argument so that ILRepack doesn't do the prefixing: ``` ILRepack.exe /verbose /log /out:merged/MetroDemo.exe MetroDemo.exe JetBrains.Annotations.dll MahApps.Metro.dll...

I had the exact same problem and updated to the most recent `3.1.407` SDK and the issue seems to be gone.

@augustoproiete It has nothing to do with the actual build script. Somehow the above files had a "invalid" "LastWriteTime" timestamp. Not even Windows was capable of zipping those files. At...

- I would like to see an easy way to create "colored-full-width container" elements (e.g. http://www.microsoft.com/surface/)

Had the same problem and somehow this "works": ``` bundle.AddCssBundle("/Content/css.css", "/wwwroot/Content/metro-bootstrap.css", "/wwwroot/Content/jquery.fileupload-ui.css", "/wwwroot/Content/font-awesome.css", "/wwwroot/Content/tablesorter.theme.default.css", "/wwwroot/Content/jquery.bonsai.css", "/wwwroot/Content/DataTables/css/jquery.dataTables.css", "/wwwroot/Content/DataTables/css/buttons.dataTables.css", "/wwwroot/Content/DataTables/css/buttons.bootstrap.css", "/wwwroot/Content/Site.css").UseContentRoot().AdjustRelativePaths(); ```

We encountered the same problem and were also forced to "migrate" from "net6.0-windows" to "net6.0". Of course, this was only possible because we "muted" this rule in `.editorconfig` at the...