I have to take my previous post back! - It does work.

Here are the dlls I had to include in my reference (the path on some dlls might be different):

<li>C:\Program Files (x86)\Microsoft SQL Server\100\SDK\Assemblies\Microsoft.SqlServer.ConnectionInfo.dll
<li>C:\Program Files (x86)\Microsoft SQL Server\100\SDK\Assemblies\Microsoft.SqlServer.Management.Sdk.Sfc.dll
<li>C:\Program Files (x86)\Microsoft SQL Server\100\SDK\Assemblies\Microsoft.SqlServer.Smo.dll
<li>C:\Program Files (x86)\Microsoft SQL Server\100\SDK\Assemblies\Microsoft.SqlServer.SmoExtended.dll
<li>C:\Windows\assembly\GAC_MSIL\Microsoft.SqlServer.SqlClrProvider\10.0.0.0__89845dcd8080cc91\Microsoft.SqlServer.SqlClrProvider.dll
<li>C:\Windows\assembly\GAC_MSIL\Microsoft.SqlServer.SqlEnum\10.0.0.0__89845dcd8080cc91\Microsoft.SqlServer.SqlEnum.dll

Now, in my case those were added to a secondary application which I added to the installshield setup (for the workstation installation section). This secondary app runs after the install of the main app (which includes this small app) and allows the user to select a previously setup sql server to be injected into the app.config which is then encrypted.

This portion works great now. I will check tomorrow if this will also work for my main install application, which currently runs directly from the CD. I might get a problem there as installshield does not install this master install routine.

I'll have to see.

Bonnie, thank you. (I wait with the stars untill tomorrow).



>>Hmmm, I thought i tried that - but I am propably wrong.
>>
>>I'll check it out a bit later today, that would be cool if that works.
>>
>>Thanks!
>
>You're welcome ... let us know if that works.
>
>~~Bonnie
>
>
>>
>>>
>>>I see no problem with that approach.
>>>
>>>But, rather than require the user to run the app on the existing server machine, here's another thing you can do rather than install SMO:
>>>
>>>- Change the "Copy Local" for the SMO references. IOW, in the references of your app, right-click on the Microsoft.SqlServer.Smo and choose Properties. Then change "Copy Local" to true (do this with the other Microsoft.SqlServer.* DLLs). The DLLs get included in your bin\debug folder. So, you're actually going to distribute the DLLs with your app. That's probably ok to do, I'm guessing.
>>>
>>>... and it seems to work ok, I just tested it. Although, to be honest, I didn't actually test it on a machine that doesn't already have SMO installed, so you may want to play with it a bit more.
>>>
>>>~~Bonnie