tea time with meowkins

How to Fake SPFarm.Local & SPFarm.Properties with Typemock

This was a little tricky to figure out, and finding info on typemock is kind of hard sometimes, so here it is.

1. Get a fake SPFarm object
   
   SPFarm fakeFarm = Isolate.Fake.Instance<SPFarm>(Members.ReturnRecursiveFakes);
   
2. Fake SPFarm.Local with the fake farm
   
   Isolate.WhenCalled(() => SPFarm.Local).WillReturn(fakeFarm);
   
3. Fake the fakeFarm.Properties with a Hashtable containing your fake properties
   
   Hashtable farmProps = new Hashtable();
   farmProps.Add("WindwardArrowLicense", testLicense);
   Isolate.WhenCalled(() => fakeFarm.Properties).WillReturn(farmProps);

Here's an example test method.

[Test, Isolated]

public void ReadLicense_RequestExistingLicenseFromLicenseHandler_LicenseReturned()

{

// setup the fake farm

SPFarm fakeFarm = Isolate.Fake.Instance<SPFarm>(Members.ReturnRecursiveFakes);

 

// fake the "SPFarm.Local"

Isolate.WhenCalled(() => SPFarm.Local).WillReturn(fakeFarm);

 

// fake properties

Hashtable farmProps = new Hashtable();

farmProps.Add("WindwardArrowLicense", testLicense);

Isolate.WhenCalled(() => fakeFarm.Properties).WillReturn(farmProps);

 

string readLicense = ArrowLicenseHandler.ReadLicense();

 

Assert.AreEqual(testLicense, readLicense);

 

Isolate.Verify.WasCalledWithAnyArguments(() => fakeFarm.Properties);

}

 

Happy mocking!

The Longing

I'm in the deep again

In the darkness

Drinking deeply of the despair

Warm slow burn

Come with me into the darkness

Breathing the sludge

Warmth and longing 

The longing

SharePoint List Field Type Mappings to SQL Data Types

I've been wondering how SharePoint list field types map to SQL data types. I did some web searches but didn't find what I was looking for, so here's a link to the documentation explaining this (WSS v3): http://msdn.microsoft.com/en-us/library/ms437580(v=office.12).aspx. And here's a table of mappings as documented for the Type attribute.

SharePoint Field Type	SQL Data Type
AllDayEvent	bit
Attachments	bit
Boolean	bit
Calculated	sql_variant
Choice	nvarchar
Computed
ContentTypeId	varbinary
Counter	int
CrossProjectLink	bit
Currency	float
DateTime	datetime
File	uniqueidentifier
GridChoice	ntext
Guid	uniqueidentifier
Integer	int
Lookup	int
LookupMulti
ModStat	int
MultiChioce	ntext
MultiColumn
Note	ntext
Number	float
PageSeparator
Recurrence	bit
Text	nvarchar
ThreadIndex	varbinary
Threading	varchar
URL	nvarchar
User	int
UserMulti
WorkflowEventType
WorkflowStatus	nvarchar

 

On the empty ones, I'm not sure what the type should be or if there is even supposed to be a type.

The Type in the left column is the value of the Type attribute in a list Field definition. These <Field> elements are returned when you retrieve a list schema from the Lists web service.

The Phenomenon of Attachment of the Ego to Art

Here's my theory about why people get upset when you tell them you don't like the music, or movies, or whatever, that they like. I believe that listening to music and watching movies is a very expressive thing for people. Their music is them. The movies they like are part of their ego. So when you strike those things, you're striking the people that like them as well.

Let's take a lesson from this observation and move away from anger when someone strikes the arts we enjoy. Maybe they are just trying to piss you off, but most times I think people are just not thinking about this.

I think this phenomenon is at the root of all "religious wars". I'm not talking about religion (although maybe that's the same), I'm talking about things like Windows vs Mac, iPhone vs Android, vi vs Emacs.

Another lesson we can take here is to be careful about when you express any kind of negativity. This is sort of a personal choice – sometimes we actually prefer people who just say what's on their mind all the time – but if you're talking to someone that you really don't want to offend, you should avoid negative expressions, because you might strike some part of them – maybe a trivial part, or maybe a sacred one.

But how can we avoid being drawn to anger ourselves? We must detach ourselves from things. "Seeing me before him, the enemy attacks, but by that time I am already standing safely behind him."

Windows 7 to Windows XP Logon Failure: The user has not been granted the requested logon type at this machine.

Ok, so I ran into this networking problem last week, and it took me a bit to figure it out, so I'll explain the problem and how I fixed it here.

SUMMARY

You are logged in as a user on machine A. You try to view shared folders on machine B. You get the logon failure. That's because the user is not allowed to log into or share files with machine B. Add the user to the remote users group on machine B. The machines have to be in the same workgroup or domain for you to do this.

DETAILS

I recently got a brand new Windows 7 desktop to work from home, but I also have this old Windows XP desktop at home that I've been using for personal stuff and remoting into work. I wanted to give my work computer access to my home computer so that I could just copy some of the files (The Longest Journey! :D) over as needed. My new win 7 desktop is MACHINE_A, and my home desktop is MACHINE_B.  

The problem I hit was that when I tried to browse to \\MACHINE_B, MACHINE_A would say the logon failed because the user had not been granted the requested logon type at the computer. The thing that really confused me was that when I first tried to explore \\MACHINE_B, it would prompt me for a u/p, and I would put in the one for MACHINE_B\admin, and it would churn for a moment, and then it would give that error. Here's what happened.  

MACHINE_B was on workgroup settings, and MACHINE_A was on the work domain. I was logged into MACHINE_A as DOMAIN\userOnA, a user that was unknown to MACHINE_B. MACHINE_B gave remote access only to administrators, which is why userOnA was blocked, even with the correct u/p. I had the right authentication, but not the right authorization. I tried to add userOnA somehow, but I couldn't. I probably could have opened MACHINE_B wide open so that anything could access it, but I didn't want to do that.  

Eventually, I figured out that I needed to put MACHINE_B on the work domain so that I could select user objects from it, and add them to the remote users. That would let me add userOnA to MACHINE_B's remote users, which means that if userOnA were authenticated, then he could also perform remote actions like sharing files from MACHINE_B. I joined MACHINE_B to the work domain, logged in as admin, added userOnA to the remote users, went over to MACHINE_A, explored \\MACHINE_B, and I was able to see the shared folders.  

Actually, to tell you the truth, I could be mistaken about how I explained some of these things, but based on what I did and what worked, these are the concepts that I drew. In any case, I hope this helps you out!

Happy Networking!