stigzler

Nope - I did IM him out of courtesy, just didn't hear back from him. Sure he's super-duper busy.

EDIT: Further investigation seems to imply it's Launchbox dlls that are the issue. Firstly, 3rd party dlls are loaded fine. The refer in .csproj: <ItemGroup> <Reference Include="Caliburn.Micro"> <HintPath>..\..\Core\Caliburn.Micro.dll</HintPath> </Reference> <Reference Include="Caliburn.Micro.Platform"> <HintPath>..\..\Core\Caliburn.Micro.Platform.dll</HintPath> </Reference> <Reference Include="LaunchBox"> <HintPath>..\..\Core\LaunchBox.dll</HintPath> </Reference> <Reference Include="System.Windows.Interactivity"> <HintPath>..\..\Core\System.Windows.Interactivity.dll</HintPath> </Reference> <Reference Include="Unbroken"> <HintPath>..\..\Core\Unbroken.dll</HintPath> </Reference> <Reference Include="Unbroken.LaunchBox"> <HintPath>..\..\Core\Unbroken.LaunchBox.dll</HintPath> </Reference> <Reference Include="Unbroken.LaunchBox.Plugins"> <HintPath>..\..\Core\Unbroken.LaunchBox.Plugins.dll</HintPath> </Reference> <Reference Include="Unbroken.LaunchBox.Windows"> <HintPath>..\..\Core\Unbroken.LaunchBox.Windows.dll</HintPath> </Reference> </ItemGroup> Caliburn, System dlls are all loaded fine. Seocndly, I deleted and re-added caliburn (via `Add Project Reference`) from the Core folder without any issues. However, when I tried doing this with LB dlls, I get the above error. It feels like unless you're willing to pay a monthly subscription for the Theme Creator app, theming is broken in launchbox?

Hi. Having difficulty getting started with this. Not wanting to use the monthly subscription (!!) Community Theme Creator. Know Xaml + WPF so would prefer that. Have created a copy of Default, but all the assemblies are missing and as a result, no design view: I moved over to CriticalZoneV2 that I found in my themes folder as this has a 'References" folder. I tried copying over the missing dlls from launchbox/core but this didn't resolve the missing dependencies: Tried importing it manually, only to be greeted with: I hate to say it, but it's all a bit jank, really. How do I get up and running editing themes in Visual Studio. I've seen Jason's videos from 8 years ago, but these are super outdated now and seemingly irrelevant.

Did you get anywhere with this? In the same boat and banging my head against a brick wall here. Not the smoothest of software design, really...

I updated and expanded my C64Dreams sister App. It adds the following features: Makes installation into existing (or indeed vanilla) Launchbox installations a lot easier (fully automated). Automates adding other C64 games to the C64Dreams collection without having to mess about with .bat, .vbs, .ahk files. Also automates adding to the Launchbox database (not having to add it manually). Lets you search the C64Dreams collection for specific games in-app rather than having to launch Launchbox each time. Fixes broken Images for Platforms, Platform Categories and Playlists. Also lets you use your own images and automates the installation to launchbox process. Details here:

Hi Folks. I wrote an app as an add-on to Zombeaver's excellent C64Dreams project. Features: Makes installation into existing (or indeed vanilla) Launchbox installations a lot easier (fully automated). Automates adding other C64 games to the C64Dreams collection without having to mess about with .bat, .vbs, .ahk files. Also automates adding to the Launchbox database (not having to add it manually). Lets you search the C64Dreams collection for specific games in-app rather than having to launch Launchbox each time. Fixes broken Images for Platforms, Platform Categories and Playlists. Also lets you use your own images and automates the installation to launchbox process (GIMP template attached to this post for convenience). The C64Dreams Project: C64DreamsTool Pics: C64DreamsTool video: C64DreamsTool Downloads: Github: https://github.com/stigzler/C64DreamsTool/releases/tag/Release Images XCF: PlatformLogos.xcf

Great response, thanks retrogirl. I suspected from looking at the files that it would be constructing the folder structure right with the right files in etc. Just started expanding my C64Dreams Importer to automate this process. It's the edge cases that'll get me (all the bats and vbs' looked the same, for example - but I bet there are edge cases that require different code somewhere). I know @Zombeaver is super busy so likely doesn't have time,. but if anyone knows these edge cases let me know!

Does anyone know how to add your own C64 games to this collection. I'm guessing you add it to the C64Dreams/Games folder, but given they all seem to follow a cutom format (with a folder for each game and also other bat files etc) - I didn't want to do this via Launchbox Import File process as it asks for an emulator etc. Search on this long topic wielded too many results to be helpful.

Annyywhooos... Just revisited this @Zombeaver + again - fab bit of work. Installing it on my 'final' emu machine. I've had a poke around as I'm trying to dovetail C64D's controls with those I've globally configured across all other retroarch systems. Is there any way to choose a different hotkey? I'd like to change it from Back to [what is essentially] the Guide button (long story short PS4>DS4Windows>Xbox Controller). Route irrelevant: shows in retroarch as button 10 rather than button 7 (Back). Changing it in C64D retroarch doesn't change the hotkey. I notice you have some AHK scripts working alongside other utility apps, so rather than guess what's inside the black box, thought I'd ask first! Unfashionable of me, I know! Also had a quick search on this topic - couldn't find anything - although it may be buried deep in the details somewhere. EDIT: Nemmind - found it - you do this via C64Dreams/Configurator.exe>Config Editor.

Hi all. Just checking whether this is possible through LB natively before I go down a rabbit hole of coding this. I have an old console shell fitted with a PC and a LB installation. I also have a server full of roms. Given file sizes for the later generations and limited space (2TB) on the unit's SSD, I'm looking to have a mixture of local roms (e.g. Soul Calibre and Crazy Taxi for dreamcast) and also importing full sets from my server. So, in this example, the full DC set would be available when the unit's plugged into my home network, but when not networked (or in another home) only Soul Calibre and Crazy Taxi would be available in LB/BB. I've tested this, and unfortunately the network roms are still visible in LB when it is detached from the network. I'm just checking whether there are any settings I'm missing which would make the network roms invisible when unit's not attached to the LAN? Failing that, any thoughts on the best design approach for a plugin? I'm currently developing one that already has the facility to monitor all LB/BB actions and has the ability to augment LB functionality via individual platform setting etc. My first thought would be via leveraging the "hidden" property in the roms - that is have a setting in a plugin that registers the root of your network roms and at an event (e.g. change of selected platform event), see if this network location is available. If not, go through each rom in the local db, making them hidden if they are on the network location. Only drawback is if you were to set a game to be hidden in all scenarios (but could work around that by having a per-game setting in my plugin to make it hidden no matter what). I haven't really looked into the LB/BB views objects in the plugin API - but guess that's also a possible approach (and possibly better given I wouldn't be messing with the db entries and it may be quicker) Would welcome thoughts (+ hopefully a simple box I can tick in LB natively to do this all for me!)

Thanks for this. Having tried no end of other approaches (involving a dummy emulator, launch application before etc) this is by far the easiest way to achieve this.

Nice work brother - exactly what I needed. I did try to distinguish between the user or windows awakening the PC as also wake @ 3am on a Sunday to do updates, but couldn't find a way to do it. I'm just hoping my AV amp doesn't turn on when it senses the PC waking up else I'm going to hear the BB launch video at full blast early hours of a Monday morning! I wouldn't hold your breath for the LB team fixing issues like this. They seem to struggle with the 'smaller' issues.

Can also confirm this. Problem is lunchbox side. 2.5 years later and still no fix?

Hey. Just to contribute. I often had the same problem during development of a plugin and testing. From exploring files on my test machines and from Jason's posts here, I think it has to do where there are competing .dlls between those in Launchbox/Core and any plugins or possibly themes (or anything that uses its own individual dlls). Often for me, it occurs when my plugin uses dlls that are also used in launchbox and those in my plugin directory are more current than those in laucnhbox (i.e. launchbox likely requires an update). In short: if you're having these errors, ensure Launchbox is updated first. Then you can manually compare the dll referenced in the error message to any in the Launchbox\Core directory. If the Launchbox version is older, then that might be your problem.

I'd probs raise a separate post with a few more details.

God that was bloody horrible. Never make me do that again.... 12 hours straight and finally upgraded about 7 different projects to .net 9. To be fair to M$ - their Upgrade tool is really good. The hassle came from resolving references and fixing breaking changes in .net 9. Curses! I know I'm going to be finding bugs for a while yet.. Goodbye Framework - you served me well, but like an ex-wife - don't think I'll be visiting for tea again any day soon. So yes, in conclusion, upgrading to .Net9 solves this issue. However, if you've got any kind of complexity (read: multi-local library, old platform etc) make sure to bring a 4-pack of patience.

So is this good or bad? Looks baaaad to me:

Oh gosh, no. But I know my own limitations and the state of my code! 😉

Thanks Joe. God I've got a horrible feeling this is going to go really, really badly.

Oh, I WILL be doing a commit if I do it! 🤣

Cheers dude. @JoeViking245 has suggested referencing LB/Core/Drawing.Common - so need to find a way to try this first as my plugin is v complicated (5 projects + leveraging some potential framework only features) - so if Joe's suggestion works this would be the preferable path rather than the upgrade. However - is there a "reverse" upgrade option? The Framework/Core/.net transition is one I've never braved!

Thanks, Rob, but forgot to mention that it's built using Framework 4.8 - so not sure how easy it is to switch to .net 9.

Think this likely has something to do with the .net version update. Error thrown at my entry point class inheriting ISystemMenuItemPlugin: public class SystemMenuItemHook : ISystemMenuItemPlugin { // Launchbox Properties ============================================================================================== public string Caption => "Gearbox"; public System.Drawing.Image IconImage => Gearbox.Presentation.Properties.Resources.gearboxicon; public bool ShowInLaunchBox => true; public bool ShowInBigBox => false; public bool AllowInBigBoxWhenLocked => false; // Gearbox Properties ============================================================================================== public SystemMenuItemHook() { } public void OnSelected() { // Blah - problem not here } } Gearbox.Presentation.Properties.Resources.gearboxicon throws the error: "System.PlatformNotSupportedException: 'BinaryFormatter serialization and deserialization have been removed. See https://aka.ms/binaryformatter for more information.'" gearboxicon shows as a System.Drawing.Bitmap and is included via the Vis Studio Resources system. This has been working fine for all past versions. Plugin built using Framework 4.8 Any ideas?

I was really replying to the OP. However, I assume you've tried AHK for what you are wanting to achieve? It lets you launch things via key combos