|
|
Don't care for pesto much.
Now olive oil and butter is really my favorite....
ed
|
|
|
|
|
Slow Eddie wrote: Now olive oil and butter is really my favorite....
Add freshly chopped parsley, cilantro, and basil and/or oregano ( or fennel for a switch ) ( but then I had to add sautaed onions and 'shrooms ).
|
|
|
|
|
I've had such coding jobs, in the past. Since I wasn't permitted to change variable names en masse, I created a list of the major variables from declarations, etc. and provided a description and where used. it was list that grew real time. grrr
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
Lucky you, you can't feel productive just refactoring code! 
Here where I am now, refactoring is difficult, all public & protected method are "possibly in use" by internal customers... And it is strongly recommended not to remove or rename any.... 
|
|
|
|
|
Create a new method with a 'good' name and copy (or, if you can, refactor) the old method to it. Then change the 'bad' name method to just call the 'good' name method and add an attribute of Deprecated / Obsolete (depending on the language and environment). Then you can use the 'good' name and the minor overhead will only be felt by the old users.
I have often wanted a feature to alias / synonym a method / routine. The only environment that I use that has this feature is SQL Server.
|
|
|
|
|
c++ will support that also 
|
|
|
|
|
My sympathies. I can only suggest sacrificing either a cat or the previous programmer to the Gods of programming.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
|
I have a similar situation with an app using MS tech that is no longer available. Using references to this library all through the code, with no attempt at segregating it from the main logic, etc. No attempt at SOLID.
Since I have to look at how to update (if possible) or replace this library, first job is pull all of this code into its own module. To be honest, this could be fun in its own right... 😉
|
|
|
|
|
|
Updates install but no issues. Might well be keyboard related.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
Anyone working in .Net MAUI?
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
|
sounds too good to be true.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
At first I thought you were looking for developers in Hawaii.
"It is easy to decipher extraterrestrial signals after deciphering Javascript and VB6 themselves.", ISanti[ ^]
|
|
|
|
|
It's only available on Visual Studio preview, and I only install stable version. So, no...
|
|
|
|
|
I avoid MAUI. It's former Xamarin, I don't want to deal w "hobby" projects, bloated till "enterprise library". And hell, old good WinForms still service very well!
|
|
|
|
|
Except that WinForms tends to fall on its face when scaling is involved and more and more people are using scaling. WPF solves that problem quite nicely.
|
|
|
|
|
Well, I agree that LCD become bigger and better density, but... I'm such an old guy who still uses Win7 and has NO ANY WISH to move on win10 cr__p. And Win7 - you know, its interface is best looking at normal 100% scale at 90dpi. And there ALL windows software (inc. which I make) works perfect.
|
|
|
|
|
Nope, I work in .Net Denver. 
|
|
|
|
|
I did. I was looking for a way to use Blazor for Windows apps, and saw MAUI was the latest from Microsoft. I gave it a try since I was building a basic app, and didn't care that it's still in preview or not that mature.
|
|
|
|
|
Following up on this. Maybe you can answer a question
I get that with MAUI you can publish to Windows, Android, and Mac. The demo app shows the SAME UI being run on all 3 platforms. That’s NOT a real world example. In a real production app the UI’s for the different platforms are NOT going to be the same.
For example, I’m working on a large WPF app for a construction company. It has dozens of UI’s and View Models. There’s also a Xamarin Android app which is a collection of smaller UI elements that contain specific pieces of functionality from the Windows app, like a task list, uploading files, etc.
I created the WPF app and Xamarin app as two different projects in the same solution. Many of the UI’s from both share common view models, like the Login view. The view may be different on both platforms, but the VM is the same and can be shared by both. They also share common data models, API Proxy, and repo. That solution architecure works great.
But in MAUI, it seems like ALL the UI is contained in one project, and the only answer I’ve gotten is to use compiler directives to decide what UI to show based on the environment the app is running on. That feels like a workaround.
So, what is the right way to organize a MAUI solution given a similar design?
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
You are right. You have to be careful with certain features only being available for some platforms.
The way I had structured the project was: I separated the whole project into
- a Class Library for a particular functionality
- a Razor Class Library for holding all my UI Razor Components, which would call a function in the Class Library
- a Blazor Web App
- a Windows MAUI App
(both importing from the Razor Class Library)
|
|
|
|
|
Thanks
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
