|
Yes.
I have a couple of libraries (being primary a SharePoint Developer), I’ve got a Common, Winforms, ASP.NET and SharePoint libraries (including unit tests) which I’ve built up over the years of consulting.
|
|
|
|
|
Anything that can be generalized is added to the library.
Some of it even ends up as articles. But the backlog seems to be growing, mundane things such as family, work and procrastination, tends to get in the way.
|
|
|
|
|
I'm doing it even for a higher level stuff like search dialogs, connectivity, data handling etc. I'm lazy as f***, so I reuse every single bit of code.
There is only one Vera Farmiga and Salma Hayek is her prophet!
Advertise here – minimum three posts per day are guaranteed.
|
|
|
|
|
I do, and as soon as i figure out it needs to be enlarged or split i do so to keep it on point. Though it's not always easy since all dependend projects could be affected with the change.
Rules for the FOSW ![ ^]
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
I have a tiny one for automating view and viewmodel comms, and lots of share code in base classes in my framework. So far I still just Copy-Paste the first steps from the previous project. It is a framework, but only within each new project and not yet ready as a proper stand-alone framework.
|
|
|
|
|
Any technical (vs. business) code should always be a library. (Others touch on this as well)
In addition, create a Façade (at the minimum) for any System or Third Party library that is not part of the deep core of the language or that is heavily used in the business layer. This protects business logic from platform upgrades or Third Party changes.
A good example is email.
|
|
|
|
|
I think it is natural to develop a "code library" of sorts for the things that should be easier, but are not, or the things like Logging which need different implementations depending on the type of application, etc.
Sometimes, just wrapping an outside tool so we all use it in a consistent manner.
Logging, and Timing come to mind. We add those to every project.
Then we have impersonation things we do all the time in web frameworks so we can test specific user features/paths.
It all feels like a framework at some point, because we know it is going to be in there, but it is really a set of libraries and approaches, so we are not locked in too far.
|
|
|
|
|
I built a framework for an ERP system once.
The only "framework" I have these days includes:
1) A class for serializing / deserializing any object to / from xml
2) A class for sending emails.
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
|
|
|
|
|
For those of us that do keep a reusable framework around, how do we like to organize it?
- Create a personal NuGet package?
- Keep a Visual Studio project around that gets included into each project that uses it?
- Keep a folder full of *.cs files that get copied into a project when needed?
- Keep a *.dll (or folder of them) to reference without looking at the source code?
|
|
|
|
|
What works for me is to organize things into projects, then include the project in the apps I'm working on.
The issue with this is versioning. I probably need to create a defined version of each project, then create a NuGet repository that I can publish from.
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
Thought of this while driving, but couldn't post until home.
OG posted his "Thought of the Day", so this is a follow up.
If you use an Ab Master for exercise, does that make you a user or an abuser?
|
|
|
|
|
Or a master abuser?
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
It takes time to reach the level of master, until then you're just AB Normal.
DURA LEX, SED LEX
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
When I was six, there were no ones and zeroes - only zeroes. And not all of them worked. -- Ravi Bhavnani
|
|
|
|
|
If an animal spray tags your wall, is that just pandalism?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
If the animal is a fish, is it Wandalism?
DURA LEX, SED LEX
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
When I was six, there were no ones and zeroes - only zeroes. And not all of them worked. -- Ravi Bhavnani
|
|
|
|
|
|
Particularly exquisite, because "wand" is Dutch for "wall".
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Not sure, but it would put me in a pissy mood.
When you are dead, you won't even know that you are dead. It's a pain only felt by others.
Same thing when you are stupid.
modified 19-Nov-21 21:01pm.
|
|
|
|
|
It depends on whether the animal walks on two or four legs.
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
If you dare call your teenager a panda, he will spray-tag your walls.
... such stuff as dreams are made on
|
|
|
|
|
If any teenager of mine spray-tags any walls, she(*) will discover that this old dog still has quite a few bites left in him!
(*) I only have daughters
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
|
At least it's not a Tapir[^]
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Funny, we used to have a book publisher that was called Tapir[^]
|
|
|
|
|
if it's a dog performing mark-up, that's grrrfitto.
«There is a spectrum, from "clearly desirable behaviour," to "possibly dodgy behavior that still makes some sense," to "clearly undesirable behavior." We try to make the latter into warnings or, better, errors. But stuff that is in the middle category you don’t want to restrict unless there is a clear way to work around it.» Eric Lippert, May 14, 2008
|
|
|
|