The postings on this site are my own and do not represent my Employer's positions, advice or strategies.

LifeAsBob - Blog



No Ads ever, except search!
Sunday, June 16, 2024 Login

Blog posts for the month of December,2011.
Growing Pecan and persimmon trees in Missouri12/27/2011 2:18:58 PM

Well, we're about to find out how difficult it is to grow pecan trees in missouri, specifically Pleasant Hill, Missouri, Cass County.

I ordered several varieties from different nurseries, trying to see what will do best.

8 Pecan from (pencil size about 18 inches)
4 Pecan (Native Hardy Seedling) from (Thick as your thumb,2-3 foot)
4 Osage Pecan Tree (grafted) from (Thick as your thumb,2-3 foot)
4 American Persimmon from (Nice size, about 2-3 foot, thick as a pinky or ring finger)
1 Hazlenut from

I have a Northern James Pecan which just came from TyTy Nursery, I'll plant that tomorrow and update the map below.  Also from TyTy were some cherries and mulberries, I'll have to post an updated map of the orchard that is being planted.

For Spring planting I have ordered an extra large nut tree bundle from the Missouri Department of Conservation: nut tree bundle
species includes 5 each of :
Shellbark hickory (see species 331)
Pecan (see species 301)
Hazelnut (see species 422)
Black walnut (see species 300)
Butternut (Juglans cinerea)

I'm also wanting to plant some Paw Paw trees but they may have to wait until next year.


Mulberry, Pear, Paw Paw and Pecan12/30/2011 10:37:24 AM

Got some nice temperatures the past few days and managed to plan a few more trees I received from TyTy nursery (  These were probably the best bare root trees I received, and the cost reflected that:

1 6 foot Northern James Pecan

2 Super Mulberry

1 Gelato Red Mulberry

1 Paw Paw Tree

2 Keiffer Pear

1 Bing Cherry

1 Black Tartarian Cherry

Update Map (does not include Orchard area, i still have to map that).


Unhandled Exception12/13/2011 1:22:50 PM

This is nothing users dislike more than an Unhandled Exception, an I agree.

SQL Server Management Studio (SSMS) Express 2008 (patched with SP3), recently began giving this error to a user of mine, every time they clicked on the "New Query" button.  "Microsoft .NET Framework"  Unhandled Exception has occured in a component in your application.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
   at Microsoft.SqlServer.Management.UI.VSIntegration.ShellCodeWindowControl.CreateCWWindow()
   at Microsoft.SqlServer.Management.UI.VSIntegration.ShellCodeWindowControl.OnHandleCreated(EventArgs a)
   at System.Windows.Forms.Control.WmCreate(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at Microsoft.SqlServer.Management.UI.VSIntegration.ShellTextEditorControl.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************

The user recently received from patches for Visual Studio 2010 and then things stopped working.

Basically the user was using SSMS express.  I Unininstalled SSMS Express 2008 (and the SQLExpress instance) and installed SQL Server Developer Edition 2008.  In the process of installing developer edition, the installation was aborted due to missing Visual Studio 2008 SP1.  I applied Visual Studio 2008 sp1 and then restarted the installation of developer edition, the install was successful.  The user was able to open SSMS and launch a new query window without error.  I wonder if applying VS 2008 SP1 would have corrected the original error, but at the point I realized VS 2008 sp 1 was missing, I had already installed SSMS Express 2008.

I hope to never see this error again, but I've been trouble shooting many issues related to having Visual Studio 2005, 2008, 2010 and SQL Server 2005,2008, 2008r2.   I can't even imagine throwing sql 2012 into the mix, but I guess it's coming....prepare for more compatability issues.

Blog Home