« first day (784 days earlier)      last day (1620 days later) » 

06:37
@Derpy your action over five years ago took effect just now....
in Shadow's Den on Meta Stack Exchange Chat, 2 mins ago, by FOX 9000
@ShadowWizardWearingMask WSP (?)
You remember this?
Guess not, so...
BTW these days the Den is really a different place than what it used to be when you decided to leave it. No trace to the people who were active back then, so you can play WAG again if you like, FOX is lonely. ;)
 
12 hours later…
19:00
@ShadowWizardWearingMask A WSP package is a package for SharePoint. Therefore, it is basically a functionality update for a virus.
I thought you liked sharepoint
@AndrasDeak .... what gave you that idea??
I have to work with SharePoint. And it is a mess
(also, kinda unrelated....
in Tavern on the Meta on Meta Stack Exchange Chat, 5 mins ago, by Νеvеrꭑoꭇе
Am I going crazy or Facebook has decided to self-terminate by requiring login to access any profile page (including those of companies that advertise thru the site)?
19:32
@Derpy I knew you worked with it (any tech thing I've seen you remark on was SP) and I kind of assumed you didn't hate it. Working with tech you hate sucks.
I only have very limited clicky-clicky experience with it, so I can't even imagine what using it seriously (and programming it) can be like
19:49
@AndrasDeak Over the course of some years, I kinda managed to just be indifferent to it. It is bad due to the way it was implemented, but I don't let it ruin my day.
In a way, it is even funny.
Seeing the horrible workarounds you have to make at times can be intriguing.
that's Stockholm syndrome at best :)
@AndrasDeak nope, more of a explorer/archeologist thing.
Decoding SharePoint docs is kinda similar to deciphering hieroglyphs
ah, explains that username...
also, ugh :(
20:04
I think I mentioned that before somewhere.
Once I found a pdf book hidden on a MSDN page that documented the schema for the CAML spec.
@Derpy probabky, but I don't stalk you :P
Short version, it is an XML like language you have to use to describe some things in a declarative way when working with solutions, features ect
Not familiar with CAML
Just to give you a vague idea of "How BAD" it is...
@Derpy you had me at XML-like
But go on :D
20:08
some properties must have boolean value, some had to have GUID values.
Well...
A "normal/sane minded" language would probably accept the strings "true", "True", "TRUE" etc... without making any casing distinction.
Everything unexpected should give a warning/error
Sharepoint... nope.
Every true/false value has different rules
Some are considered "true" only if you write exactly "True", false otherwise (so "TRUE" is considered false in this case)
Haha, nice
Tell me that invalid values are silently ignored
Some ignore casing but unexpected values are considered false. Some do the same but consider errors as true
Oh, it's false. Even better!
In some cases, you can either write "True" or "TRUE" but "true" gives an error
Is that incompetence or malice?
20:13
In some cases, EVERY value is considered true, even the string "false"
to specify a false value, you must not set the property altogether.
:|
Sounds like malice :P
I was able to find the doc again
As you can see, it gets even better with Guids.
Sometime you have to include curly braces, sometime it will error out if you do...
But the "true/false" thing is the worst.
> Intellectual Property Rights Notice for Open Specifications Documentation
Aha! So it is malice!
"Newbies" often lose hours because they think they have set a property to true in a feature but the package "seems to ignore my setting"
I like how "UniqueIdentifierWithOrWithoutBracesWithOrWithoutDashes" is a "common simple type"
20:20
and then discover that they wrote prop="true" in a case where only "True" is accepted and everything else is ignored
@AndrasDeak Sadly, I have to go now, but if you want to see how weird it can get, read this old post of mine
11
Q: Purpose of the <MAPPINGS> CAML element in a custom Choice Field definition

BlueSoulI have yet to find a clear answer to this topic, so I'm writing this question in hope that someone can explain me the correct way to achieve my goal. I must also add that all my test was done on SharePoint 2007, but as far as I know the behavior should be the same when using the 2010 version. Edi...

It's about a functionality/setting that apparently has no purpose
Thanks, I'll take a look :) I'm half elsewhere anyway
Night
Up to now, no one I know has managed to find a way to make it work.
I think it is just an elaborate form of feng-shui
Morbidly fascinating

« first day (784 days earlier)      last day (1620 days later) »