How to make a Ju52:
In a tall glass with NO ice:
1 part coffee liquor (e.g. Kahlúa)
1 part cream liquor (e.g. Bailey's)
1 part orange liquor (e g. Grand Marnier)
2 parts cold milk.
The special guy that I am, I had to go invent my own cocktail. As its name betrays, it is very similar to B52. In fact, it is just B52 with cold milk instead of ice. The replacement of ice with cold milk brings the following benefits:
Visual Studio is a capricious product, and its "Solution" subsystem is especially capricious. When you look at what options are available you might think you have a great degree of freedom to structure things the way you want, but as you will inevitably (and painfully) find out later, many things have to be done in precisely one, entirely undocumented way, or else there will be pain of the worst kind: Visual Studio will malfunction either without any error message, or with error messages that are completely unhelpful for locating and fixing the problem.
Here is a list of things I have (painfully) found out over the years.
I have a lot to say about the modern trend in graphical user interface design which aims to achieve an impossibly clean look at the expense of usability, but this is going to be the subject of another blog post. In this post, I want to talk about simplifying the user interface when the simplification is clearly a win, both from a usability point of view and, incidentally, from an aesthetics point of view. Specifically, I want to show how a yes/no/cancel prompt can be reduced to just a yes/cancel prompt.
I recently did this at work, and I decided to document the process here in the form of a how-to guide. Please note that I am not an expert, I am learning as I go along, so there may be mistakes.
Sdk-style project files have existed since net5. The kind of project files we were using before that can now be called legacy-style project files.
Sdk-style project files are necessary if you want to:
I recently did this at work, and I decided to document the process here in the form of a how-to guide. Please note that I am not an expert, I am learning as I go along, so there may be mistakes.
The XAML Hot Reload feature of WPF is extremely useful because GUI work often involves tweaking visual aspects of an application, so being able to modify XAML, save it, and immediately see the changes on the screen saves a huge amount of time as opposed to having to terminate the application, modify the code, re-compile, re-run, and go clickety-clickety-click to navigate to the same page and finally see your changes.
Unfortunately, as a WPF project grows, the XAML Hot Reload feature inevitably one day stops working: You modify your XAML, you save the XAML file, and yet nothing changes on the screen. The message "No changes were found" appears in the Hot Reload tab of the Visual Studio Output Window, but it is a damned lie, because you just made changes. This can really be a problem.
When you find yourself in this extremely unpleasant situation, here is a list of things to try:
 |
Artwork based on original mouse-15887 by Arkthus from the Noun Project |
