|
semi-monthly: Quote: occurring or published twice a month.
bi-monthly: Quote: done, produced, or occurring twice a month or every two months.
Quote: Assuming bi- can be two or twice, bimonthly can be every two months or twice a month, which is a bit confusing and can lead to a big difference in meaning. ... Semimonthly, however, is always twice a month.
|
|
|
|
|
Biweekly has the same problem.
|
|
|
|
|
|
I've half a mind to agree.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
I always understood semi- to mean half (e.g. semimajor), and bi- to mean two (e.g. bicycle)
The use of bi- to mean half may refer to a doubling of the frequency, but is more likely to be due to people using words they don't properly understand.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
I've never come across semi monthly, although semi annual is very commonly used in financial circles.
Cheers,
Vikram.
|
|
|
|
|
Also, biannual which can and most commonly is used to mean twice a year, may also be used to mean every two years, though for the latter it's often sensible to use biennial to avoid confusion.
|
|
|
|
|
Bi-monthly, bi-weekly, bi-annually - I'll never understand why words with such ambiguities are in-use!
When I worked at a banking processing center and they were pushing for "bi-monthly billing" as a feature - half the staff had one definition in mind, and the other had another!
Any attempt to have them adopt less ambiguous speech like "twice-monthly billing" or "two-week-billing" was shown with disdain. Don't be optimistic about explaining why wording is important to any higher-ups in the financial industry. They already had the marketing stuff all printed up and didn't want to be seen as troublemakers.
|
|
|
|
|
Is it just me or is Visual Studio a little lax in understanding when it doesn't need to build, and when it doesn't need to build.
cheers
Chris Maunder
modified 11-May-21 10:02am.
|
|
|
|
|
Not sure what you are saying here - for me, VS builds when I tell it to and at no other time ...
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Press F5. You haven't changed anything, and you only exited the app a few seconds ago. Visual Studio builds again. Oh, and the "check for build before debug" option? It's turned off.
Mother Microsoft knows best my ass.
Software Zen: delete this;
|
|
|
|
|
Debugging, running Entity framework's Update-Database command, looking at it slightly sideways. It always goes through the whole build cycle.
What happened to the days of simply tracking project dependencies and file changes, and when youhit F5 it says "nothing I care about has changed. We're done"
cheers
Chris Maunder
|
|
|
|
|
Chris Maunder wrote: What happened to the days of simply tracking project dependencies and file changes, and when youhit F5 it says "nothing I care about has changed. We're done"
They ended in Visual Studio 2008, which we still use(*) for most of our development. Pilot projects moved to VS2015 and now VS2019 exhibit the problems you cite.
(*) I'm part of a software group working in a company where R&D and engineering managers are all mechanical engineers. Workflow and official documentation, even for software, therefore adheres to hardware methodologies. Changing Tools Is Bad, because then you have to do a complete product regression test, and nobody has time for that.
Software Zen: delete this;
|
|
|
|
|
I have had all kinds of fun with the Batch Build option. I think it is messed up to the point I filed a bug report and was told the issue is behavior by design. I replied that it was a very poor design.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
I've told them that about a lot of their crapware.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Message Closed
modified 15-May-23 19:07pm.
|
|
|
|
|
It must have improved since the last time I used Qt Creator. I had to do complete clean and build's because the dependency checking ignored resource changes.
Software Zen: delete this;
|
|
|
|
|
VS has not a single clue what/when to build or not, if you are not going and explicitly define the project dependencies...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
|
|
|
|
|
What annoys me is that if you leave the "properties" page open and close VS, next time you open the solution you get an error because VS is using the project file and can't open it twice ...
This is an annoyance when you release a new version, and then go to the assembly properties to set up the version number of the next debug edits ... which may be some weeks or months off.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
We have several solutions that contain several projects each. When you tell it to build, it has to check each one for changes to make sure it actually has to build it.
There's a line in the output window that tells me "n succeeded; n failed; n up to date"
The numbers represented there (in my case) always represent the correct compile status. Build is different from rebuild, as I'm sure you know.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Chris Maunder wrote: Is it just me or is Visual Studio a little lax in understanding when it doesn't need to build, and when it doesn't need to build.
Aren't these two the same...? Is VS the only one who's confused here...? 
|
|
|
|
|
Visual Studio has confused me so much I can't even form logical sentences.
cheers
Chris Maunder
|
|
|
|
|
I think this is exactly what's happening. VS manages to confuse itself.
|
|
|
|
|
Before there were BitCoins there were Arcade Tokens !
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
W∴ Balboos, GHB wrote: Before there were BitCoins there were Arcade Arcane Tokens!
FTFY
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
