GAC and Common Files was the first place I looked. Ended up I had a manually created custom field descriptor in a BO that didnt match the new constructor. So that is solved.

I had to add the SQL SDK reference at home as well to recompile the SF source for Strataframe DB Engine, odd but working fine. Thanks, have a good weekend and dont work too hard

Keith Chisarik

Sorry, didn't finish my thought...a lot going on around me.  My point was that the SQL management assembly shouldn't even be needed for any version of SF.  So I am unsure of where that is coming from.

Be sure to check your GAC and that your references in your project are looking at the new SF assemblies.

It sounds like you have some old assemblies hanging around.  Once you rebuild the BOs with the BO Mapper and then rebuild the projects, this error should go away.  As for the SQLServer error, that is strange.  I will be posting a build on Tuesday/Wednesday that will have full SQL Server 2008 support and also reduces the amount of SMO used within the framework (totally removed from the UI).

I read the post in "to upgrade or not to upgrade" and decided to update to 1.6.7 beta.

Two issues:

1) To rebuild the SF source I had to add a reference to Microsoft.SQLerver.Management.SDK.sfc. Why, and any issue there?

2) ...and this is the big one because I cant work now. I rebuilt all my BO partial classes via mapper. I still get the folowing errors when trying to compile that I cannot get past.

a) _ComponentType is not declared

b) Argument not specified for parameter 'propertyType' of Public Sub New(fieldname as String, propertyType as System.Type)

 

Keith Chisarik