I think the merge modules (SQLSMOMergeModule.msm and StrataFrameMergeModule.msm) supplied in the latest beta, install SF DLLs which are an earlier version than the DLLs installed by the beta itself.
When I run my application against the DLLs installed by the merge modules I get "type not found" style errors which are not there when the application runs against the DLLs installed by the beta installation itself.
If this is the case, any chance of an update?
Thanks,
Aaron
When I first read this I tought that we probably forgot to update this. However, the same SMO MSM that we place in the distribution folder is the same that we use as part of our installation. So these should be up to date. The StrataFrame MSM appears to be updated as well, but I will look at this more closely. So I would imagine at this point that one of two things happened:
I will check again, but I am pretty confident that the correct files are being distributed.
Just some more info in case it helps...
I have uninstalled and re-installed the latest beta and checked that the Distribution folder was removed after the uninstall. After the SF beta installs, the SQLSMOMergeModule.msm file has a modified date of 27th January and StrataFrameMergeModule.msm is 16th February.
When I build and run my app in VS everything is okay. I then re-build my Installaware installation (after deleting and adding the merge modules in IA just to be safe). When I run the IA installation routine on my PC, the application doesn't run and throws "type not found" errors from the SF DLLs. This is also true if I try and run my application in VS. To fix it, I do a repair on the SF beta installation and I am back in operation again.
I don't think there is a permission problem as my PC starts with the correct DLLs from the SF beta install. It is only after the IA merge module install that it goes wrong. I have also tested it on a clean PC with the same outcome.
This is very literally the exact SQLSMO MSM that we use during our install of SF.
Thanks.
Thanks