referencing Microsoft.sqlserver.Management.smo in for .Net 3.5

Where can I find the dll needed to reference for the namespace Microsoft.sqlserver.Management.smo that is compatible with .Net 3.5

When I locate the needed assemblies :


from the dll(s) in the folder C:\Program Files\Microsoft SQL Server\110\SDK\Assemblies\ I get a message that these dll(s) needs newer version of .net FW to use.

I using .Net 3.5
SQL server 2012
and VS 2010

Please help
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

You need to install the SQL Server 2005 Feature pack and reference those versions. I don't think you need to have SQL 2005 installed.

32bit -

64bit -
fmichailAuthor Commented:

Thanks for the quick response. If I install both 32 and 64 versions of the Feature pack on the same box?
Umm.... I'm sure you can. But i'm not sure how that will work when it comes to deployment? I don't know what you think about this... Perhaps target x86 so that you have compatibility across all architectures?
Exploring SharePoint 2016

Explore SharePoint 2016, the web-based, collaborative platform that integrates with Microsoft Office to provide intranets, secure document management, and collaboration so you can develop your online and offline capabilities.

fmichailAuthor Commented:
I need to use these components ONLY in my Installation Application to programatically create SQL agent job for my clients to backup the database nightly (As a part of installing my application), and my application targets SQL server 2012, so I do not think I will have an issue in running this (Kind of Setup.exe) on the client site even If I have to create 2 versions of the installation (Setup) application (Like the same concept of the 32 bit/64 bit that you are helping me to resolve now).

I know it must be a different question, but I am trying to use these namespaces only to create the sql agent job and schedule it to run nightly. Is there another alternative to do this action using the normal SQLClient namespace. Thanks
Why don't you just use SQL scripts to create the jobs? Then you don't need to worry about SQL DMO versions and making two setup files?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
fmichailAuthor Commented:
What I am doing now is to make the Setup application create the SQL script for the job to create 7 rolling daily backups, and Indicate to the DBA to create this SQL agent job and schedule it to run daily, however, I wanted to take it a step further to automate even this step. But you are absolutely right, and I think it is an extra un-required step. I appreciate your help and it was really fun to discuss and learn from you. Thanks MIandaT.
Glad to have helped :)

Look around at Custom Actions as well. They allow you to add custom actions :) to your installers and stuff:
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic.NET

From novice to tech pro — start learning today.