eat off the street (food carts on twitter)

These are some of the twitter users that provide location and time-sensitive updates on where to grab their grub.

Creme Brulee Cart
Twitter: @cremebruleecart
Sugar-crusted treats in the Mission, usually at Dolores Park, torching the desserts to order.

Magic Curry Kart
Twitter: @magiccurrykart
Choice of chicken or tofu curry and lots of veggies (broccoli, string beans, and carrots), served with rice. Usually near the Creme Brulee Cart.

Amuse Bouche Cart
Twitter: @AmuseBoucheSF
Muffins and chai for a dollar. The self-proclaimed "home of the original recession buster breakfast."

Mobile Pho Truck
Twitter: @whatthepho
Fresh noodles and broth all over the Bay Area, including Millbrae, outside AT&T Park, and the piers.

Urban Nectar
Twitter: @urbanectar
URL: urbanectar.com
A juice cart selling fresh-squeezed lemonade, watermelon juice, and strawberry juice, where a portion of earnings go to a local charity.

Spencer on the Go
Twitter: @chezspencergo
URL: spenceronthego.com/home.html
Fine French cuisine (grilled sweetbread with sherry, ratatouille, truffle boeuf bourguignon) sold from a converted taco truck.

Roli Roti
Twitter: @RoliRoti
URL: roliroti.com
Sustainably-farmed meats grilled rotisserie style, served with organic produce.

CookieWagSF
Twitter: @cookiewagsf
A cookie/ice cream sandwich cart.

The Tamale Lady
Twitter: @tamalelady
Her Twitter feed is blank right now, but surely the Tamale Lady will get around to updating (after making her pork with red sauce).

Left Coast Smoke
Twitter: @leftcoastsmoke
A barbecue outfit rotating among several Mission District bars.

Sam's Chowder Van
Twitter: @samschowdervan
URL: Starting this summer, a truck selling East Coast lobster rolls and chowder to the Bay Area.

I Love Street Food
Twitter: @streetfoodsf
Tracks national street food news, but specifically the San Francisco scene.

list compiled by serious eats http://www.seriouseats.com/2009/05/a-list-of-street-food-vendors-trucks-carts-using-twitter.html

Why call it a toy?

The visual studio 2008 command here powertoy, redux for windows 2008 32 bit, installation of visual studio on the c: drive. I know that someone will want this exact thing rather than pecking through the INF file themselves.

Download Install Here. Right click on the INF file and select Install.

ref:

• Scott Hanselman and http://accidentaltechnologist.com/programming/visual-studio-2008-command-prompt-here-on-vista-64/

p.s. the uninstall is botched; it leaves its registry folders in place for some reason. If someone fixes this, great, in the mean time just don't uninstall it

Following Robert Shelton's well documented series on creating MOSS 2007 workflows in Visual Studio 2008, I ran across a bit of a snafu. Basically, his recommended dev machine setup stipulates WSS3, VS2008, etc. However the Visual Studio 2008 wizards/templates for Sequential Workflow expect MOSS, not WSS. The workaround should get me positioned to develop, debug, package and deploy workflows in VS2008.

I found the most complete workaround write-up on this issue on the Visual Studio SharePoint Tools Blog by Roger Best. Here is his writeup in full (in case the link stops working one day..)

"Getting Visual Studio 2008 SharePoint 2007 Sequential / State Machine Workflow projects working with Windows SharePoint Services 3.0

Published 19 August 08 02:18 PM

I wanted to create a SharePoint workflow using VS 2008 on WSS 3.0. The documentation is set that only Microsoft Office SharePoint Server 2007 can be used but I figured I would lay out the modifications needed to allow a project to function on WSS 3.0. The four steps are:

1.) Since WSS 3.0 doesn't have a docs site and the wizard is particular about specific "sites" we need to change http://machinename/docs to http://machinename.

If not you will get the message:

"SharePoint site location entered is not valid. The SharePoint site at http:///Docs could not be found. Verify that you have typed the URL correctly. If the URL should be serving existing content, the system administrator may need to add a new request URL mapping to the intended application."

Go ahead and finish wizard with what you need. Once the project has been created

2.) Remove the reference to Microsoft.Office.Workflow.Tasks

Now depending if you are coding in VB or C# you should

3a.) C# open workflow1.cs code editor and remove "using Microsoft.Office.Workflow.Utility;"

or

3b.) VB remove import of Microsoft.Office.Workflow.utility.

4.) Now we have to remove some xml from the feature.xml file specifically

- ReceiverAssembly="Microsoft.Office.Workflow.Feature, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"

- ReceiverClass="Microsoft.Office.Workflow.Feature.WorkflowFeatureReceiver"

Now you should be able to debug the project .

Roger Best"

refs:

• http://blogs.msdn.com/vssharepointtoolsblog/archive/2008/08/19/getting-visual-studio-2008-sharepoint-2007-sequential-state-machine-workflow-projects-working-with-windows-sharepoint-services-3-0.aspx
• http://www.sheltonblog.com/archive/2007/10/05/sharepoint-document-workflow-with-visual-studio-workshop-documents-download.aspx
  

another day, another lesson.

After arm wrestling the 64 bit version of MOSS 2007 + Windows 2008 x64 + Visual Studio 2008 x64 (and Visual Studio 2010 Beta 1 x64) , and LOSING - I was cornered into SharePoint Designer for development of workflows.

Now, I know the inefficiency I'm invoking by doing this - instance creation versus template creation! But deadlines beg, you know. So how pleased am I that when I eventually get my x86 (ow, what year is it? I think I've been writing for x86 platforms for something like 20+years, yikes) VM dev instance in HyperV up and running, I'll be able to reuse/import the SPD built workflow logic into Visual Studio.

Warning, there is excessive winking in this blog entry:

http://blogs.msdn.com/sharepointdesigner/archive/2007/07/06/porting-sharepoint-designer-workflows-to-visual-studio.aspx

The other nugget of the day is that I think I'll write up my findings of first release of Google Chrome for Mac OSX and the SharePoint experience. Chrome is built on webkit rendering, similar to Safari, so I imagine its pretty much a similar look & feel - but Chrome is supposedly faster. Maybe Microsoft will give even test for Chrome in Office 14 / SharePoint 10 and bestow the official "level 2" browser support.

This is Yet Another Blog on how to properly install & configure a SharePoint 2007 development client installation. I've read many different blogs and noticed pretty substantial inconsistencies and invariably most come to the conclusion that Your Mileage May Vary. Case and point, in my dev environment, I'm optimized for the current bleeding edge, and there is a whole lot of blood. Dev setup:

OSes

• Windows 2008 Server 64 bit for the Dev Server
• One configuration that didn't work for the Dev Client - Windows 7 RC1 (Build 7100) 64 bit (HP Compaq workstation, 2gb ram); the reason that I need to have a client/server is due to a limitation of Visual Studio 2008 and VS 2010 Beta 1's SharePoint Workflow Project creation running on a 64 bit OS - http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=325668
• Dev Client - Windows XP SP3, dual core E2220 CPU at 2.4 GHz, 2GB RAM

Configuration

to be continued...

How to install MOSS 2007 SP2 on Windows 7 RC (build 7100)

Although this is not a supported scenario, there is a way to install MOSS 2007 onto Windows 7 Release Candidate (build 7100). Here are the steps:

1. Get the Installation Helper, created by Bamboo Nation.
   
2. Get the MOSS 2007 installation media and extract it to a temporary folder on your hard drive
   
3. Get the MOSS 2007 SP2 service pack: http://www.microsoft.com/downloads/details.aspx?FamilyId=B7816D90-5FC6-4347-89B0-A80DEB27A082&displaylang=en
   
4. Get the WSS 3.0 SP2 service pack: http://www.microsoft.com/downloads/details.aspx?FamilyId=79BADA82-C13F-44C1-BDC1-D0447337051B&displaylang=en
   
5. Now you need to slipstream the installation packages (if you try to run the installer without SP2 slipstreamed, you will be blocked (KB 962935)
   http://blogs.msdn.com/opal/archive/2009/05/08/install-moss-2007-wss-3-0-on-windows-server-2008-r2-you-will-need-sp2-slipstream.aspx
   
6. To create the slipstream package, follow the steps in http://technet.microsoft.com/en-us/library/cc261890.aspx. Basically, you need to open a command prompt and execute the following commands:
7. wssv3sp2-kb953338-x64-fullfile-en-us.exe /extract:C:\TEMP\MOSS2007×64\Updates
   
8. officeserver2007sp2-kb953334-x64-fullfile-en-us.exe /extract:C:\TEMP\MOSS2007×64\Updates
   
9. Delete Wsssetup.dll because it may conflict with Svrsetup.dll. Having both Wsssetup.dll and Svrsetup.dll in the updates folder for a slipstreamed installation source is not supported.
   
10. Run the SetupLauncher.exe from C:\Program Files (x86)\WssOnVista\Setup)
    
11. Locate the MOSS 2007 setup.exe in your installation folder.

source: http://blogs.msdn.com/weslbo/archive/2009/05/08/how-to-install-moss-2007-sp2-on-windows-7-rc-build-7100.aspx

After installing VS2008 pro on the sharepoint 2007 64 bit win2k8 server, I create a new SharePoint Sequential Workflow project and get the dreaded "Object reference not set to an instance of an object" dialog.

A similar project creation failure occurs using Visual Studio 2010 Beta 1 on the 64 bit MOSS 2007 server too. In the case of the newer IDE however, there is no dialog box, rather the status bar on the bottom says

Creating project 'SharePointWorkflow1'... project creation failed.

So it seems like the "plan" as indicated by the Program Manager is currently half implemented. The VS2010 Beta 1 actually shows these project templates to the user on a 64 bit environment (not according to plan), however the project creation fails (seemingly by design).

>"The plan for Visual Studio 2010 is to still not support SharePoint 2007 Workflow projects on a 64bit workstation. VS 2010 will avoid the problem of throwing exceptions by hiding the Project Templates for those two project types: SharePoint 2007 Sequential Workflow or SharePoint 2007 State Machine Workflow. However Visual Studio 2010 will support 64bit development of the future version of SharePoint." - Christin Boyd, Program Manager, Visual Studio.

Is Microsoft really taking SharePoint ECM development seriously? e.g. at TechEd (a couple weeks ago), the keynote reinforced the 64-bit-everywhere mantra for MOSS, but this frustrating issue doesn't make that feel very near term.

i.e. this issue is 'closed' from Microsoft's standpoint *YIKES* https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=325668

http://blogs.msdn.com/nikhil/archive/2008/01/15/sharepoint-workflow-feature-in-vs-2008.aspx

There is one workaround that seems promising - the Workflow templates in WSPbuilder from CodePlex are supposed to work. I'll going to give that a shot next.

Once upon a time, a Sharepoint site quota snuck up on you. Users complained, Admins panicked, and no one could upload or make changes to their sites. After a couple of frustrated attempts to adjust a Quota Template (seemingly obvious answer), the admin realizes this path is in vain. Recycling the app pool, or even worse, the server does nothing to appease the angered users. Fear not, there is hope: these are the steps to change the effective site quota for a site in flight:

1. Open Central Admin
2. Open Application Management
3. Under SharePoint site management go to site collection quotas and locks - the breadcrumb trail should now read:
   Central Administration > Application Management > Site Collection Quotas and Locks
4. Select a Site Collection (if you are editing a subsite, click the dropdown and select the Site Collection, even if it is already on the target site collection you are having a problem with)
5. (if you are editing a subsite quota) find the subsite URL or user’s personal site, and select it
6. (if you are editing a subsite) the Site Collection box should read e.g. http://my/personal/username
7. Under Site Quota Information at the bottom of the page, click the Current Quota Template dropdown to the right and select Individual Quota.
8. Adjust the effective quota to the desired limit and warning values. The changes take effect immediately. Verify effective quota by viewing the site's Site Settings > Storage Space Allocation e.g. http://my/personal/username/_layouts/storman.aspx

Applies to Sharepoint 2007.

Adapted from user gmagerr http://www.sharepointblogs.com/forums/t/13739.aspx