StrataFrame Forum

SF and VS 2008

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

By Hugo R. Figueroa - 12/21/2007

When I try to set the BussinesObjectName for a textbox I get this error (I am using Visual Studio 2008)

==========================================================

Exception
  The ApplicationBasePage could not be located.  Please rebuild project.

Source     : MicroFour StrataFrame Extensibility

Stack Trace:
   at MicroFour.StrataFrame.Extensibility.BusinessObjectNameTypeEditor.EditValue(ITypeDescriptorContext context, IServiceProvider provider, Object value)
===========================================================

I downloaded and installed the .dlls according to http://forum.strataframe.net/Topic12892-22-1.aspx (did it twice) and still get the error.

What can I do to fix this?

Thanks.

By Hugo R. Figueroa - 12/21/2007

If I set the property writing directly on it, instead of clicking on the downarrow, the application compiles ok.
By Hugo R. Figueroa - 1/2/2008

still stuck
By Trent L. Taylor - 1/3/2008

Hugo,

I will set this up in 2008 and see if I can reproduce.  We have all just gotten back into the office and so we are working as quick as we can to catch up after the Christmas break.  Thanks for your patience.

By Hugo R. Figueroa - 1/3/2008

No problem Smile.

I just worried that my message was overlooked.

By the way, HAPPY NEW YEAR!!!

By StrataFrame Team - 1/4/2008

The problem is 2008... that type editor looks for the VS Design-Time Extensibility object in the running object table of the OS.  The name of the object changed for VS2008.  We have made the necessary changes to get the type editors working in VS2008, but they have not been released, yet.  We are re-working the installation utility to also check for VS2008.  When that is complete, we will release a new build that supports VS2008.
By Hugo R. Figueroa - 3/13/2008

I am getting the same error in VS2008 after upgrading from VS2005 (this is a web site)
By Trent L. Taylor - 3/13/2008

If you create a new web site or application (one not upgraded) does this same error occur? This may be an upgrade issue that was introduced through the VS upgrade wizard.