Hi All,
I have deployed my .NET application in a web server. The clients has to download it using an URL provided in my website. The deployment is ok and the installation is working fine in client machines where users logged in as Administrators. I have problem with client machines where users are has limited access only. It is saying "Administrator permissions are required to install..."

My Application Information:

• WPF CAB Application
• Developed in .NET Framework 3.5
• SQL Server CE 3.5 is used as local database

The Client machine information:

• Windows XP Professional
• Windows Installer 3.1 is not installed
• .NET Framework 3.5 is not installed
• SQL Server CE 3.5 is not installed

The above error happens when the prerequisites are installing. It stops when the Windows Installer 3.1 is about the install.

1. Is there anyway that these prerequisites will install in Limited Access User login?
2. Is this same problem come when my application is about to install assuming all the prerequisites are installed?

1. No.

2. No.

They have to have admin privs to install the .Net Framework or the Windows Installer. If they are already installed, then the installation will just continue.

Now, for SQLCE, you can actually deploy the dll's locally rather than installing SQLCE itself. You can add the dll's to your project and set "copy local" to true and include them in the deployment. Then you can remove that as a prerequisite. Here are the dll's you need to add:

sqlceca30.dll

sqlcecompact30.dll

sqlceer30en.dll

sqlceme30.dll

sqlceoledb30.dll

sqlceqp30.dll

sqlcese30.dll

RobinS.

GoldMail.com

In my project I have under References only one entry for SQLCE: System.Data.SqlServerCe. The path for mine is: C:\Program Files\Microsoft SQL Server Compact Edition\v3.5\Desktop\System.Data.SqlServerCe.dll. CopyLocal is set to False for the reference.

Copy those dll's over to the same folder as your csproj file for your main project, and then add them to the project in the Solution Explorer in Visual Studio. They should be marked with a Build Action of Content, and Copy To Output Directory set to "copy always".

They will be included in the ClickOnce deployment, and on the client machine, your software will access them locally, and they won't need to be installed in Program Files *or* the GAC.

RobinS.

GoldMail.com

Hi,

The installation of the Windows Installer 3.1 v2 requires the administrative previleges to start the windows installer service.
Without this you cannot install the software. Even if the windows installer is installed the service wouldn't run properly.

Regards,

If only windows installer is available on the machine you would not face any problems.

1. No.

2. No.

They have to have admin privs to install the .Net Framework or the Windows Installer. If they are already installed, then the installation will just continue.

Now, for SQLCE, you can actually deploy the dll's locally rather than installing SQLCE itself. You can add the dll's to your project and set "copy local" to true and include them in the deployment. Then you can remove that as a prerequisite. Here are the dll's you need to add:

sqlceca30.dll

sqlcecompact30.dll

sqlceer30en.dll

sqlceme30.dll

sqlceoledb30.dll

sqlceqp30.dll

sqlcese30.dll

RobinS.

GoldMail.com

Yes Robin. You are right.

Dileep Kumar's suggestion won't work. I tried a very long back with the same scenario. But each prerequisite required Administrator Permissions. I convinced my client to install them in Admin Mode.

Coming to SQL CE, I have read this one in an article too. I would refer the SQL CE in my application from the Reference dialog which refers to the GAC assemblies. If I am coping all the above DLLs and local how it would work in the client machine? Should I have to reference SQL CE from the local DLLs??

In my project I have under References only one entry for SQLCE: System.Data.SqlServerCe. The path for mine is: C:\Program Files\Microsoft SQL Server Compact Edition\v3.5\Desktop\System.Data.SqlServerCe.dll. CopyLocal is set to False for the reference.

Copy those dll's over to the same folder as your csproj file for your main project, and then add them to the project in the Solution Explorer in Visual Studio. They should be marked with a Build Action of Content, and Copy To Output Directory set to "copy always".

They will be included in the ClickOnce deployment, and on the client machine, your software will access them locally, and they won't need to be installed in Program Files *or* the GAC.

RobinS.

GoldMail.com

Thank you Robin. I will try it...