StrataFrame Forum

Visual Studio crashing when mousing over BO in object tray

http://forum.strataframe.net/Topic17267.aspx

By Govinda Berrio - 6/23/2008

I just tried this on a fresh VS 2008 project. I start a project using the Stataframe Windows Application (no security) template. Add a Strataframe Standard form. Add a Stataframe BO. I start the BO Mapper and point it at the database (SQL Server 2005 Express), just one table dbo.Lookups. Build the partial. Close BO Mapper. ReBuild the project, everything compiles fine. I can add the BO to the new form by dragging it from the toolbox. But... when I *mouse* over the the BO in the object tray I get a Visual Studio error without much information to glean anything from. (But I can send to Microsoft for their information.)



I've attached the table that I'm getting this with. Any help would be great.



Govinda
By Trent L. Taylor - 6/23/2008

Wow...that makes absolutely no sense whatsoever Crazy

Mousing over a BO within a designer doesn't do anything, so this is really strange.  In fact, since a BO isn't a UI component and inherits from a Component within the component model, there are no UI events!  So even if we wanted to do something in the mouse over within the designer or run-time...we couldn't!

You are welcome to post the solution and I will see if the same results happen on this side...but I have a feeling that there is something going in within your VS environment in regards to any Component or MarshalByRefComponent class.

By Govinda Berrio - 6/24/2008

Thanks Trent,



here's the VS solution....



Also, this doesn't happen with any other BOs that I'm working with. And if I don't mouse over the BO everything else is working fine. So, lets say there is a problem with the Component or MarshalByRefComponent class, what's the fix for that? Try reinstalling VS?



Govinda
By Trent L. Taylor - 6/24/2008

OK, I am not sure exactly why this was making VS die, but it failed on my side as well.  However, to fix the problem, all I had to do was go into the BO Mapper, map the BO, build the partial class, and then rebuild the solution.  Once I did this, all was well.
By Govinda Berrio - 6/24/2008

I've done that several time at this point and it hasn't fixed the problem here.



I'm running SF version 1.6.5.1. Is there another version I can try?
By Edhy Rijo - 6/24/2008

Hi Govinda,

Yes there is a new beta version released yesterday at http://forum.strataframe.net/FindPost17255.aspx

By Trent L. Taylor - 6/24/2008

Govinda,

I am not sure that you had as I did not see any strong-typed properties in the sample that you sent me.  I saw that you had everything structured, etc.  But I just mapped to the Customers table in the StrataFrameSample database and all was well.  One thing that I did not think if you did map, is what you mapped to.  Does your structure use any reserved words, have spaces, or anything funny like that?

By Govinda Berrio - 6/24/2008

OK! I figured something out. (Thanks to Trent Wink)



I just started renaming columns one-by-one and found that VS just doesn't like it when you name a column "Locked". As far as I know it's not a keyword in SQL Server 2005, maybe it's stepping on a BO class member, since the column name becomes a property of the BO. But why did rebuilding the partial fix it on your machine, Trent? (rhetorical)



Anyway, I hope this thread helps someone else someday.



Govinda
By Trent L. Taylor - 6/24/2008

If you place the column name in brackets it may have resolved your problem:

Public Property [Locked] As String
   ...
End Property

This is an escape for reserved words (including intrinsic ones).  You might try that to see if the problem goes away.  Just an idea Smile