Hi guys,



For those of you using InstallAware they just released an update to add the .Net 4.0 Framework runtimes, here are the links:

Edhy Rijo

Hey Edhy.

A bit late, but thanks for posting this. I faced an issue with VS 2010 Service Pack 1 and SqlServer.SMO referencing .NET Framework 3.5, so as Keyth and Marcia have already done it, I had to recompile SF under CLR 3.5 and now I will have to make sure my installations test this pre-requisite on the clients machines. Since I own Installaware 7, I didn't have these CLRs ready for installation. Your post directed me to the right place!

Thank you.

Hi Ivan,



You are welcome, but just to be clear, I have not seen the issue that requires me to rebuild SF under CLR 3.5.  Here is my configuration:
VS2010 SP1
All my projects are using .Net 4.5 runtime.
SF source is as distributed by MicroFour, only the DevExpress solution is rebuild, but using 2.0.
InstallAware 9 R2.

I install the SQL SMO2008 with a custom IA script, I don't remember if I created it, or get it from somebody else couple of years ago, if you need it I can send it to you.

Edhy Rijo

Yeah, I would also be fine if I hadn't made some customizations to the SF source code (don't tell "anyone" I did it!).
But as I have done so, I do need to recompile it, and then I hit the error I mentioned before right in the DBEngine project, which uses SMO. This is because the SMO now makes reference to the CLR 3.5 System.Core ( http://connect.microsoft.com/VisualStudio/feedback/details/651546/microsoft-sqlserver-smo-could-not-be-resolved-because-it-has-an-indirect-dependency-on-the-framework-assembly-system-core-version-3-5-0-0 ), and then VS2010 SP1 will complain about it, since SF is compiled under CLR 2.0. That is where I got stuck and had to change the source code to compile under 3.5.

Ivan, thanks for the explanation, now I understand.

Edhy Rijo