Rory
Rory
CC#
Created by monkeyoohlala on 1/12/2025 in #help
✅ WPF
Some of those look like they might be good small examples you could play with
38 replies
CC#
Created by monkeyoohlala on 1/12/2025 in #help
✅ WPF
38 replies
CC#
Created by monkeyoohlala on 1/12/2025 in #help
✅ WPF
I don't have any good examples to hand sadly
38 replies
CC#
Created by monkeyoohlala on 1/12/2025 in #help
✅ WPF
It's been a fair few years since I did WPF but Dockpanels, Stackpanels, Grids and then small adjustments to margins and padding mostly I think.
38 replies
CC#
Created by monkeyoohlala on 1/12/2025 in #help
✅ WPF
Do you mean like structuring the layout?
38 replies
CC#
Created by monkeyoohlala on 1/12/2025 in #help
✅ WPF
You could try it. I can't say I've ever tried it. I think it works well for a world of absolute positioning rather than relative
38 replies
CC#
Created by monkeyoohlala on 1/12/2025 in #help
✅ WPF
np!
38 replies
CC#
Created by monkeyoohlala on 1/12/2025 in #help
✅ WPF
Like, here, you could just reduce that margin number a bit and it'd be onscreen
38 replies
CC#
Created by monkeyoohlala on 1/12/2025 in #help
✅ WPF
Also the controls won't adapt well when you add more controls, but that's very much in your control. That said the rules posted above very much come from a place of how to write good maintainable production WPF code. If you're just starting out, do what works best for you but just know that you can tweak the xaml by hand if it's not looking right
38 replies
CC#
Created by monkeyoohlala on 1/12/2025 in #help
✅ WPF
The designer does work like that but all it can/will do is place controls in a very fixed way that won't adapt if you resize the app
38 replies
CC#
Created by monkeyoohlala on 1/12/2025 in #help
✅ WPF
But here if you dropped the margin and changed vertical alignment might that be better?
<Button Content="Button" HorizontalAlignment="Left" Height="47" VerticalAlignment="Bottom" Width="109"/>
<Button Content="Button" HorizontalAlignment="Left" Height="47" VerticalAlignment="Bottom" Width="109"/>
38 replies
CC#
Created by monkeyoohlala on 1/12/2025 in #help
✅ WPF
You'd be best learning out how to do some simple layouts with containers like grids, stackpanels and stuff, and then putting your controls and things inside of them. Sorry that's a bit vague, it's hard to outline where to start with it and i've been out of the WPF space for a bit
38 replies
CC#
Created by monkeyoohlala on 1/12/2025 in #help
✅ WPF
the top two ❌ points here essentially
38 replies
CC#
Created by monkeyoohlala on 1/12/2025 in #help
✅ WPF
Broadly, it's easier to have a layout that works logically if you are hand-crafting the markup.
38 replies
CC#
Created by monkeyoohlala on 1/12/2025 in #help
✅ WPF
Where did you want the button to go?
38 replies
CC#
Created by monkeyoohlala on 1/12/2025 in #help
✅ WPF
I am gonna assume you didn't type that xaml by hand to add the button but maybe I'm wrong there, it's all oddly specific numbers in the height, margin, width.
38 replies
CC#
Created by monkeyoohlala on 1/12/2025 in #help
✅ WPF
you have a 387 pixel margin from the top of the app in the button there: "0,387,0,0"
38 replies
CC#
Created by monkeyoohlala on 1/12/2025 in #help
✅ WPF
You're going to have to share the code for this before anyone can advise
38 replies
CC#
Created by Quantix on 1/11/2025 in #help
"Correct" way of setting up DB for Aspire.NET MicroServices following CA
I feel the thing about "microservices" is it's a bit of a loaded term now and a bit of a fuzzy definition, so it can be useless to use the term sometimes when saying "I'm doing microservices!" rather than highlighting what you're trying to achieve But yeah, typically a microservices-oriented architecture is about breaking down the composition of your service into smaller ones with discrete roles and, crucially, those services having complete isolation of their own data, and only communicating with other services through intentionally designed APIs (http, messaging, whatever). You might have different teams owning different services, even writing them with different technologies. Redundancy is one appeal (in the sense you describe and also not bringing the whole application down if one whole area (all instances of CartService for e.g.) goes down). There's other appeals like making a system "easier" to understand, develop, deploy, refactor. Not sure I'd call any "main" The key thing for you here would be ensuring MarketService can't directly interact with CartService's database tables and that they only share data over APIs. You would want a logically separate database to enforce this ideally I'd think. They could be the same server initially but you risk bringing both down if that goes down (if this is just for practice though don't complicate your life - keep the databases separate but on same server)
18 replies
CC#
Created by yummy_bee on 1/11/2025 in #help
othello game
You might want to make sure your code still works locally because it looks like your latest update to GitHub is a bit off then. What sort of stuff have you tried? Sounds like the computer player successfully makes a move in the cod behind but it doesn't update the UI? From memory you might need to trigger some PropertyChanged event to trigger the UI to update after the game logic has run?
28 replies